New issue
Advanced search Search tips

Issue 766039 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Security
Team-Accessibility



Sign in to add a comment

Heap-use-after-free in test_runner::AccessibilityController::FocusedElement

Project Member Reported by ClusterFuzz, Sep 18 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5089443945119744

Fuzzer: inferno_twister
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x61700004f000
Crash State:
  test_runner::AccessibilityController::FocusedElement
  gin::internal::Dispatcher<v8::Local<v8::Object>
  v8::internal::FunctionCallbackArguments::Call
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=499930:499947

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5089443945119744

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Sep 18 2017

Labels: M-63
Project Member

Comment 2 by sheriffbot@chromium.org, Sep 18 2017

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

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

Comment 3 by sheriffbot@chromium.org, Sep 18 2017

Labels: Pri-1

Comment 4 by palmer@chromium.org, Sep 19 2017

Cc: lukasza@chromium.org
Components: Internals>Accessibility
Owner: dmazz...@chromium.org
Status: Assigned (was: Untriaged)
Any thoughts on whether this is a bug in the test runner or in a11y code itself?
Project Member

Comment 5 by ClusterFuzz, Oct 1 2017

Components: Blink>Bindings
Labels: Test-Predator-AutoComponents
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 6 by sheriffbot@chromium.org, Oct 2 2017

dmazzoni: Uh oh! This issue still open and hasn't been updated in the last 14 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers?

If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one?

If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

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

Comment 7 by ClusterFuzz, Oct 13 2017

ClusterFuzz has detected this issue as fixed in range 508470:508529.

Detailed report: https://clusterfuzz.com/testcase?key=5089443945119744

Fuzzer: inferno_twister
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x61700004f000
Crash State:
  test_runner::AccessibilityController::FocusedElement
  gin::internal::Dispatcher<v8::Local<v8::Object>
  v8::internal::FunctionCallbackArguments::Call
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=499930:499947
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=508470:508529

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5089443945119744

See https://github.com/google/clusterfuzz-tools 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 8 by ClusterFuzz, Oct 13 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5089443945119744 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Project Member

Comment 9 by sheriffbot@chromium.org, Oct 13 2017

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Both regressed and fixed in M63, removing ReleaseBlock-Stable
Labels: -ReleaseBlock-Stable
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components
Project Member

Comment 13 by sheriffbot@chromium.org, Jan 19 2018

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
Project Member

Comment 14 by sheriffbot@chromium.org, Mar 27 2018

Labels: -Security_Impact-Head -M-63 M-65 Security_Impact-Stable

Sign in to add a comment