Null-dereference READ in blink::ThreadState::Current |
||||||
Issue descriptionDetailed 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.
,
Aug 10 2017
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.
,
Aug 10 2017
This is not related to my CL. Keishi, can you have a look or reassign?
,
Aug 10 2017
,
Oct 1 2017
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
,
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)
,
Nov 7 2017
,
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.
,
Apr 1 2018
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 |
||||||
Comment 1 by msrchandra@chromium.org
, Aug 10 2017Labels: Test-Predator-Wrong-CLs M-62
Owner: mlippautz@chromium.org
Status: Assigned (was: Untriaged)