Issue metadata
Sign in to add a comment
|
Crash in v8_wasm_compile_fuzzer |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5167270645727232 Fuzzer: afl_v8_wasm_compile_fuzzer Job Type: afl_chrome_asan Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x62d001b4dc10 Crash State: v8_wasm_compile_fuzzer v8::internal::Invoke v8::internal::CallInternal Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=571775:571776 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5167270645727232 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Jul 1
,
Jul 1
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
,
Jul 1
,
Jul 2
,
Jul 5
ClusterFuzz has detected this issue as fixed in range 572648:572652. Detailed report: https://clusterfuzz.com/testcase?key=5167270645727232 Fuzzer: afl_v8_wasm_compile_fuzzer Job Type: afl_chrome_asan Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x62d001b4dc10 Crash State: v8_wasm_compile_fuzzer v8::internal::Invoke v8::internal::CallInternal Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=571775:571776 Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=572648:572652 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5167270645727232 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.
,
Jul 5
ClusterFuzz testcase 5167270645727232 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jul 6
,
Aug 15
,
Oct 12
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 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ClusterFuzz
, Jun 30 2018Labels: Test-Predator-Auto-Components