Issue metadata
Sign in to add a comment
|
Heap-buffer-overflow in spvtools::val::Function::AddFunctionCallTarget |
||||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6510743655284736 Fuzzer: afl_spvtools_val_fuzzer Job Type: afl_chrome_asan Platform Id: linux Crash Type: Heap-buffer-overflow READ 8 Crash Address: 0x61b0000000f0 Crash State: spvtools::val::Function::AddFunctionCallTarget spvtools::val::ValidationState_t::AddFunctionCallTarget spvtools::val::ProcessInstruction Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=579912:579914 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6510743655284736 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Aug 2
,
Aug 2
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
,
Aug 2
,
Aug 2
ehsann@, andreyt@, could you please take a look. Your validation related changes are in the regression range. Assigning to dsinclair@ since ehsann@ and andreyt@ don't seem to have @chromium.org accounts. Please re-route if you know their @chromium.org handles.
,
Aug 2
The SPIRV-Tools aren't used in Chromium yet, we're getting the fuzzers running before anything uses them. Removing ReleaseBlock-Stable.
,
Aug 2
Possibly a dupe of crbug.com/870156
,
Aug 2
,
Aug 3
ClusterFuzz has detected this issue as fixed in range 580360:580362. Detailed report: https://clusterfuzz.com/testcase?key=6510743655284736 Fuzzer: afl_spvtools_val_fuzzer Job Type: afl_chrome_asan Platform Id: linux Crash Type: Heap-buffer-overflow READ 8 Crash Address: 0x61b0000000f0 Crash State: spvtools::val::Function::AddFunctionCallTarget spvtools::val::ValidationState_t::AddFunctionCallTarget spvtools::val::ProcessInstruction Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=579912:579914 Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=580360:580362 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6510743655284736 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.
,
Nov 9
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
, Aug 2Labels: Test-Predator-Auto-Components