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

Issue 754120 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in blink::ThreadState::Current

Project Member Reported by ClusterFuzz, Aug 10 2017

Issue description

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

Fuzzer: libFuzzer_content_security_policy_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::ThreadState::Current
  unsigned char* blink::ThreadHeap::Allocate<blink::ContentSecurityPolicy>
  blink::ContentSecurityPolicy::Create
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=493100:493156

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 
Cc: msrchandra@chromium.org
Labels: Test-Predator-Wrong-CLs M-62
Owner: mlippautz@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using Code Search for the file, "ThreadState.h" assigning to the concern owner.

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

@mlippautz
Predator and CL could not provide any possible suspects.
Using Code Search for the file, "ThreadState.h" assigning to the concern owner.

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

@mlippautz -- Could you please look into the issue, kindly re-assign if it is not related to your changes.
Thank You.
Components: Blink>MemoryAllocator>GarbageCollection
Owner: keishi@chromium.org
This is not related to my CL. Keishi, can you have a look or reassign?
Cc: mlippautz@chromium.org
Project Member

Comment 5 by ClusterFuzz, Oct 1 2017

Components: Blink>Internals
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.

Comment 6 by mmoroz@chromium.org, Oct 24 2017

For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md.

The link referenced in the description is no longer valid.

(bulk edit)
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components
Project Member

Comment 8 by ClusterFuzz, Apr 1 2018

ClusterFuzz has detected this issue as fixed in range 547202:547312.

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

Fuzzer: libFuzzer_content_security_policy_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::ThreadState::Current
  unsigned char* blink::ThreadHeap::Allocate<blink::ContentSecurityPolicy>
  blink::ContentSecurityPolicy::Create
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=493100:493156
Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=547202:547312

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 9 by ClusterFuzz, Apr 1 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 4625189676777472 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