Issue metadata
Sign in to add a comment
|
Security: Security: UXSS via dispatchEvent on iframes
Reported by
chromium...@gmail.com,
Nov 10 2016
|
||||||||||||||||||
Issue descriptionVERSION Chrome Version: 56.0.2915.0 Operating System: Windows 7 REPRODUCTION CASE 1. Set up a local webserver to host child.html and parent.html as: - parent.html is at http://localhost/parent.html - child.html is at http://localhost/child.html 2. Navigate http://localhost/parent.html 3. Note that the CHILD_SECRET cookie should be inaccessible from the parent page.
,
Nov 10 2016
(I'm unsure if this is a security bug.)
,
Nov 10 2016
Hi, can you please give some more details about what the bug is here (did you upload the correct files?)
When I navigate to parent.html, nothing happens. Clicking results in this error:
Uncaught TypeError: Cannot read property 'tagName' of null
at MyEvtHandler.utility (VM155 parent.html:3)
at MyEvtHandler.handler (VM155 parent.html:6)
MyEvtHandler.utility @ VM155 parent.html:3
MyEvtHandler.handler @ VM155 parent.html:6
In order for this to be UXSS, you'd need the ability to read secret data from a different origin.
,
Nov 10 2016
Er sorry, I meant to say "you'd need the ability to run script in the context of a different origin"
,
Nov 10 2016
Oops! sorry I didn't upload the correct files.
,
Nov 10 2016
To test this, I ran a separate server on localhost:8001 and accessed parent.html via http://localhost:8001/parent.html. When I tested it that way, I get the following error: Uncaught DOMException: Failed to execute 'dispatchEvent' on 'EventTarget': Blocked a frame with origin "http://localhost:8001" from accessing a cross-origin frame. at http://localhost:8001/parent.html:34:30 So this doesn't appear to work cross-origin.
,
Nov 10 2016
I can repro this easily without any error as on the video. Could you please try with this new files inside UXSS.rar
,
Nov 10 2016
Hi, I am able to get the alert if I access both child.html and parent.html under the same origin, but if I try to demonstrate cross site scripting by placing them on different origins, that access seems to be blocked.
,
Nov 11 2016
Hmm... understood :) thank you for the feedback.
,
Nov 11 2016
All right, will close as wontfix for now, but keep the reports coming!
,
Feb 17 2017
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 Deleted