Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user
Status: Fixed
Closed: Dec 2012
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug-Security

  • Only users with EditIssue permission may comment.

Sign in to add a comment
Security: Frame sniffing is not fixed
Reported by, Mar 16 2012 Back to list
Javascript allows to know if a frame scroll to a given fragment (#id) by reading the frame position. This can be abused by attacker to steal data. 


- Paul original idea: 

- My follow-up: (page 18) 

- The Firfox bug on it that I repoted in 2010

- Latest blog post on the subject (New blog post 03/16/12)


Tom / Adam ?
Comment 2 by, Mar 16 2012
Labels: -Pri-0 -Area-Undefined Pri-2 SecSeverity-Low Mstone-19 OS-All SecImpacts-Stable SecImpacts-Beta
Comment 3 by, Mar 16 2012
"Not fixed" would seemingly imply a previous bug, no? .  But I couldn't find one either here or in WK.
Problem is that scrollLeft and scrollTop properties of the frame are readable cross-origin.  Fix is to add an origin check.

Comment 4 by, Mar 16 2012
Actually, more subtle than just the origin check.  Create two nested iframes, the outer in the same domain as the main page, the inner one pointing at the victim page.  Scroll offest propogates from the inner frame out to the outer frame, which can then be read by scrollTop of the outer frame.
Comment 5 by, Mar 16 2012
Attached internals of demo.
12.6 KB View Download
Comment 7 by, Mar 19 2012
Comment 8 by, Mar 19 2012
Found the upstream bug: as implied by "Is still not fixed."
Comment 9 by, Mar 19 2012
Status: Available
Comment 10 by, Mar 27 2012
Labels: -Mstone-19 Mstone-20 MovedFrom-19
Labels: -MovedFrom-19 -Mstone-20 Mstone-19
Reverting the mass move. It does not apply to security bugs.
Status: Started
Tom has a patch up.
Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify Merge-Approved
Status: FixUnreleased
Committed r113503: <>
Confirmed that the linkedin POC no longer functions against Chromium 20.0.1097.0 

Labels: -Mstone-19 -Merge-Approved Mstone-20
And follow-on compat fix:
Committed r114406: <>

Given that this has compat considerations and that it's very late in the M19 game, let's just roll into M20.
Labels: CVE-2012-2815
Project Member Comment 17 by, Oct 13 2012
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Status: Fixed
Project Member Comment 19 by, Mar 10 2013
Labels: -Type-Security -SecSeverity-Low -SecImpacts-Stable -SecImpacts-Beta -Mstone-20 M-20 Security-Severity-Low Security-Impact-Stable Security-Impact-Beta Type-Bug-Security
Project Member Comment 20 by, Mar 13 2013
Labels: Restrict-View-EditIssue
Project Member Comment 21 by, Mar 14 2013
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Labels: -Restrict-View-SecurityNotify -Restrict-View-EditIssue
Project Member Comment 23 by, Mar 21 2013
Labels: -Security-Severity-Low Security_Severity-Low
Project Member Comment 24 by, Mar 21 2013
Labels: -Security-Impact-Stable Security_Impact-Stable
Project Member Comment 25 by, Mar 21 2013
Labels: -Security-Impact-Beta Security_Impact-Beta
Project Member Comment 26 by, Jun 14 2016
Labels: -security_impact-beta
Project Member Comment 27 by, Oct 1 2016
This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit - Your friendly Sheriffbot
Project Member Comment 28 by, Oct 2 2016
This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit - Your friendly Sheriffbot
Labels: allpublic
Sign in to add a comment