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

Issue 791253 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Dec 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Security



Sign in to add a comment

Heap-use-after-free in ui::AXSystemCaretWin::~AXSystemCaretWin

Project Member Reported by ClusterFuzz, Dec 2 2017

Issue description

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_syzyasan_chrome
Platform Id: windows

Crash Type: Heap-use-after-free READ 4
Crash Address: 0x34c76a9f
Crash State:
  ui::AXSystemCaretWin::~AXSystemCaretWin
  views::HWNDMessageHandler::DestroyAXSystemCaret
  views::HWNDMessageHandler::OnSysCommand
  
Memory Tool: SYZYASAN

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_chrome&range=521102:521174

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

Additional requirements: Requires Gestures

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Dec 2 2017

Components: Internals>Views
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Dec 2 2017

Labels: Test-Predator-Auto-Owner
Owner: nek...@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/ca6969eeeb517401b6483960a244777c77634682 (Enables AccessibleObjectFromEvent to retrieve the system caret).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
Project Member

Comment 3 by sheriffbot@chromium.org, Dec 2 2017

Labels: M-64
Project Member

Comment 4 by sheriffbot@chromium.org, Dec 2 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 5 by sheriffbot@chromium.org, Dec 2 2017

Labels: Pri-1
Project Member

Comment 6 by ClusterFuzz, Dec 5 2017

Labels: -M-64 ReleaseBlock-Beta ClusterFuzz-Top-Crash M-65
Testcase 5092642764619776 is a top crash on ClusterFuzz for windows platform. Please prioritize fixing this crash.

Marking this crash as a Beta release blocker.

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

Comment 7 by ClusterFuzz, Dec 8 2017

ClusterFuzz has detected this issue as fixed in range 522485:522510.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Heap-use-after-free READ 4
Crash Address: 0x34c76a9f
Crash State:
  ui::AXSystemCaretWin::~AXSystemCaretWin
  views::HWNDMessageHandler::DestroyAXSystemCaret
  views::HWNDMessageHandler::OnSysCommand
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=521102:521174
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=522485:522510

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

Additional requirements: Requires Gestures

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, Dec 8 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5092642764619776 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, Dec 8 2017

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

Comment 12 by sheriffbot@chromium.org, Mar 16 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 13 by sheriffbot@chromium.org, Mar 27 2018

Labels: -Security_Impact-Head Security_Impact-Stable

Sign in to add a comment