Issue metadata
Sign in to add a comment
|
Security: Leak REFERER
Reported by
jackwill...@gmail.com,
Dec 26 2017
|
||||||||||||||||||||
Issue descriptionVERSION Chrome Version: [x.x.x.x] + [stable, beta, or dev] Operating System: [Please indicate OS, version, and service pack level] REPRODUCTION CASE 1. Go to https://www.google.com/url?q=https://mallory.csrf.jp/referer_stealer.php&sa=D&ust=1514244644828000&usg=AFQjCNFkMfByI7kYEb0ccbHmGXpKlGAgwQ 2. Click on https://mallory.csrf.jp/referer_stealer.php 3. Obwserve [Danger] Leak REFERER: https://www.google.com/url?q=https://mallory.csrf.jp/referer_stealer.php&sa=D&ust=1514244644828000&usg=AFQjCNFkMfByI7kYEb0ccbHmGXpKlGAgwQ
,
Dec 27 2017
By default, browsers send the Referer header for each navigation, except in HTTPS->HTTP navigations (to avoid leaking HTTPS-protected data over HTTP). Individual sites can specify a Referrer Policy [1] to override this default. The redirection page in this report does not do so and thus the default behavior is followed. [1] https://www.w3.org/TR/referrer-policy/
,
Apr 5 2018
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by elawrence@chromium.org
, Dec 26 2017Labels: Needs-Feedback