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

Issue 704467 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Crash in blink::Range::checkExtractPrecondition

Project Member Reported by ClusterFuzz, Mar 23 2017

Issue description

Cc: msrchandra@chromium.org
Components: Blink>DOM
Labels: Test-Predator-Wrong M-59
Owner: pilgrim@chromium.org
Status: Assigned (was: Untriaged)
Assigning to the concern owner from CL --
https://chromium.googlesource.com/chromium/src/+log/994db999829331ea3b982d9c9ec469fde22de21d..1855b444e1246227907fdae45be098f2a1543982?pretty=fuller

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/e5fbce5b84544a61512d2eaf6e2e743dc22b164b

@pilgrim -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.
Cc: yoshi@chromium.org yuzus@chromium.org
+yoshi, +yuzus FYI. Noticed the repro cause uses <menu> but not sure if it is important.
Project Member

Comment 3 by ClusterFuzz, May 27 2017

ClusterFuzz has detected this issue as fixed in range 474922:474938.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::Range::CheckExtractPrecondition
  blink::Range::extractContents
  blink::V8Range::extractContentsMethodCallback
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=434769:434830
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=474922:474938

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


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 4 by ClusterFuzz, May 27 2017

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

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Cc: -yoshi@chromium.org

Sign in to add a comment