New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 675237 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Use-after-poison in blink::HTMLFormElement::reset

Project Member Reported by ClusterFuzz, Dec 16 2016

Issue description

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5636720206020608

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: Use-after-poison READ 8
Crash Address: 0x7eed3c9a4488
Crash State:
  blink::HTMLFormElement::reset
  blink::ResetInputType::handleDOMActivateEvent
  blink::HTMLInputElement::defaultEventHandler
  
Recommended Security Severity: High

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=437123:437180

Minimized Testcase (0.32 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv95U7VaodAB31U6zQAjptKZ-50IqE38zYjzdHL-ge5j0_Q9z6QKp3IDkXlA8vShxS-vVd76VDyFPCZ2j9r4qpnbX4QoPA3-4oEUOGbMuIy--N9cT6W2n5lmjKXaiCZAHfxc96CaDPe-yPOn-2pYS2Vaenyon2g?testcase_id=5636720206020608
<script>
function jsfuzzer() {
 if(htmlvar00020) htmlvar00020.appendChild(htmlvar00004); 
 htmlvar00005.click(); 
}
function eventhandler3() {
}
</script>
<body onload=jsfuzzer()>
<details id="htmlvar00004">
<input id="htmlvar00005" type="reset">
</details>
<form>
<output>
<param id="htmlvar00020" valuetype="ref"</output>


Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Dec 17 2016

Labels: M-57
Project Member

Comment 2 by sheriffbot@chromium.org, Dec 17 2016

Labels: ReleaseBlock-Beta
This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 3 by sheriffbot@chromium.org, Dec 17 2016

Labels: Pri-1
 Issue 675181  has been merged into this issue.
Issue 675110 has been merged into this issue.

Comment 6 by aarya@google.com, Dec 20 2016

Owner: tkent@chromium.org
Status: Assigned (was: Untriaged)
The result is a list of CLs that change the crashed files. 

Author: tkent
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/f5775c2f04c255de2fe9f68ff8444d3f987901a4
Time: Thu Dec 08 04:12:13 2016
Lines 469 of file HTMLFormElement.cpp which potentially caused crash are changed in this cl (frame #1, "blink::HTMLFormElement::reset").
Minimum distance from crash line to modified line: 0. (file: HTMLFormElement.cpp, crashed on: 468, modified: 468).

Comment 7 by tkent@chromium.org, Dec 20 2016

Components: Blink>Forms

Comment 8 by tkent@chromium.org, Dec 20 2016

Status: Started (was: Assigned)

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

Cc: kochi@chromium.org

Comment 11 by tkent@chromium.org, Dec 21 2016

Status: Fixed (was: Started)
Project Member

Comment 12 by ClusterFuzz, Dec 21 2016

ClusterFuzz has detected this issue as fixed in range 439820:440026.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5636720206020608

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: Use-after-poison READ 8
Crash Address: 0x7eed3c9a4488
Crash State:
  blink::HTMLFormElement::reset
  blink::ResetInputType::handleDOMActivateEvent
  blink::HTMLInputElement::defaultEventHandler
  
Recommended Security Severity: High

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=437123:437180
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=439820:440026

Minimized Testcase (0.32 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv95U7VaodAB31U6zQAjptKZ-50IqE38zYjzdHL-ge5j0_Q9z6QKp3IDkXlA8vShxS-vVd76VDyFPCZ2j9r4qpnbX4QoPA3-4oEUOGbMuIy--N9cT6W2n5lmjKXaiCZAHfxc96CaDPe-yPOn-2pYS2Vaenyon2g?testcase_id=5636720206020608
<script>
function jsfuzzer() {
 if(htmlvar00020) htmlvar00020.appendChild(htmlvar00004); 
 htmlvar00005.click(); 
}
function eventhandler3() {
}
</script>
<body onload=jsfuzzer()>
<details id="htmlvar00004">
<input id="htmlvar00005" type="reset">
</details>
<form>
<output>
<param id="htmlvar00020" valuetype="ref"</output>


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

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

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

Comment 15 by sheriffbot@chromium.org, Mar 29 2017

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

Sign in to add a comment