Issue metadata
Sign in to add a comment
|
Security: Form name="referrer" changes document.referrer
Reported by
evan.gil...@velocityapp.com,
Dec 16 2016
|
||||||||||||||||||||||
Issue descriptionDear Google, I was building an AngularJS application that needed to collect the referrer name and I had a form with the name attribute referrer and my document.referrer changed to the form DOM element. Document.referrer should not be manipulated, it's a read-only attribute. This is both a security issue for manipulating the dom, CORS, etc and more importantly a functionality issue as document.referrer is used in many sdks,such as mixpanel (I reported this bug to them as well as it breaks their sdk). REPRODUCTION CASE See this gist and jsbin: https://gist.github.com/evanjmg/4ab1fc961b53bdd67f275231a73365fa, https://jsbin.com/quyede Chrome Version 55.0.2883.95 (64-bit) Operating System: Macbook Pro - MacBookPro11,4 - OS X El Capitan - Mid 2015, 15inch Please follow up with me and let me know if you have any questions. Hope you'll get this patched up soon. Best, Evan Gillogley Web Developer at Velocity evan.gillogley@velocityapp.com +447481235882 github: @evanjmg
,
Dec 19 2016
Not sure who the best person to take a look at this is. Adding a few ccs that might potentially be interested.
,
Dec 19 2016
,
Nov 10 2017
,
Nov 14 2017
according to https://heycam.github.io/webidl/#idl-named-properties named properties (such as the value of an iframe's name) take precedence of other properties, so this is expected behavior note that the referrer only gets shadowed for javascript, the actual referrer used for network communication is not affected
,
Nov 14 2017
Issue 784733 has been merged into this issue.
,
Feb 20 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 16 2016