New issue
Advanced search Search tips

Issue 647267 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Sep 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

Crash in blink::TopDocumentRootScrollerController::globalRootScroller

Project Member Reported by ClusterFuzz, Sep 15 2016

Issue description

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

Fuzzer: meacer_chromebot_extensions
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x5f9e211c
Crash State:
  blink::TopDocumentRootScrollerController::globalRootScroller
  blink::PaintLayerCompositor::updateClippingOnCompositorLayers
  blink::PaintLayerCompositor::updateIfNeeded
  
Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_v8_arm&range=418622:418712

Minimized Testcase (15.55 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94df1BQ_RvVY-CLRPnsTjFPpaijH43c9BG1Gxdc0t3vzt9GQHGJT9TmmKiMCbpx6sNKSvyuJHZSCUEjiEpB6REi-iVOdnHLga5vtTj7Yy9F_Z7KoW5BuE2xQL8TC2uFBjGmSsc-kKMziK9IPWFJjGzka5bRfQ?testcase_id=6716160005636096

Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Components: Blink>Compositing
Labels: Pri-2
Owner: bokan@chromium.org
Status: Assigned (was: Untriaged)
https://chromium.googlesource.com/chromium/src/+/469bcf04ced0868049864010a367b0d56a73ffa7

Hi David,

Assigning 2 security bugs to you, related to TopDocumentRootScrollerController.
Project Member

Comment 2 by sheriffbot@chromium.org, Sep 16 2016

Labels: M-55
Project Member

Comment 3 by sheriffbot@chromium.org, Sep 16 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 4 by sheriffbot@chromium.org, Sep 16 2016

Labels: -Pri-2 Pri-1

Comment 5 by bokan@chromium.org, Sep 16 2016

Status: Started (was: Assigned)

Comment 6 by bokan@chromium.org, Sep 16 2016

FYI, I've already landed a followup patch that I suspect should fix this. I'll confirm shortly or fix by EOD.

Comment 7 by bokan@chromium.org, Sep 16 2016

Manually ran the clusterfuzz testcase and confirmed its fixed in my ToT build. Will leave this open until the clusterfuzz bot cycles over a more recent revision and confirms the fix.

Comment 8 by bokan@chromium.org, Sep 16 2016

Status: Fixed (was: Started)
Clusterfuzz has now marked the issue as fixed. This is fixed by https://chromium.googlesource.com/chromium/src/+/23cd9757ba798fa41b4d8dd80eb8457da6a9fa9e. 
Project Member

Comment 9 by sheriffbot@chromium.org, Sep 17 2016

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Labels: Hotlist-Input-Dev
Labels: -ReleaseBlock-Beta
Project Member

Comment 12 by sheriffbot@chromium.org, Dec 24 2016

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 ClusterFuzz, Nov 27 2017

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

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

Sign in to add a comment