Re:Firefox 59 to strip path information from referrer values...
by rovek on Friday February 02, 2018 @06:22AM
(#16289758)
You're right about subdomains but they are stripping both query and path, so 123.a.b.tld/foo would become 123.a.b.tld. It's fair to assume most misplaced sensitive data will be in the path or query, rather than the subdomain.
Re:Firefox 59 to strip path information from referrer values...
by alkonaut on Friday February 02, 2018 @06:37AM
(#16289813)
I didn't even think about the subdomain until I saw the image that is in the article here - which literally looks like it added an arbitrary number in the subdomain, duplicating the parameter number! When I saw the image I thought the article was actually about blocking some shady way of leaking that doubleclick had invented.
Re:Firefox 59 to strip path information from referrer values...
by rocqua on Friday February 02, 2018 @06:22AM
(#16289754)
To answer #1, the referrer could probably be used to make a link refer to a login page on another domain, and to then let the host redirect to the correct page after login.
There are of course ways to do this by following your suggestion #2, but I suspect this might be why we originally had the referrer header.
Re:Firefox 59 to strip path information from referrer values...
by alkonaut on Friday February 02, 2018 @06:40AM
(#16289823)
Third party logins are definitely a use case. But you'd think that they would aim to do it with logins.somewhereelse.com/?u=source instead of relying on the referrer field as the source to go back to! I wonder how common actual use of referrer is?
#2 Won't this be possible to bypass simply by encoding more in the domain part of the url than in parameters? So you switch from a.b.tld/foo?p=123 to 123.a.b.tld/foo ?