Issue metadata
Sign in to add a comment
|
Heap-buffer-overflow in getIConst |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6319256064229376 Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Heap-buffer-overflow READ 4 Crash Address: 0x62500007c900 Crash State: getIConst TIntermConstantUnion::fold TIntermediate::addBinaryMath Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=512583:512623 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6319256064229376 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Nov 15 2017
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
,
Nov 15 2017
,
Nov 15 2017
cwallez: Would you mind taking a look at this? Also, could you let us know if earlier versions are affected since it seems like we started hitting this after a fuzzer change? We'll want to update the impact/milestone/releaseblock labels if so.
,
Nov 15 2017
Assigning to capn@. The issue certainly predates the fuzzer.
,
Nov 27 2017
This is an issue in the constant folding of the GLSL compiler, which is old code. It only affects the GPU process, so its security implications are minimal. We'll look into this and related bugs when revamping the compiler.
,
Dec 5 2017
ClusterFuzz has detected this issue as fixed in range 521502:521564. Detailed report: https://clusterfuzz.com/testcase?key=6319256064229376 Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Heap-buffer-overflow READ 4 Crash Address: 0x62500007c900 Crash State: getIConst TIntermConstantUnion::fold TIntermediate::addBinaryMath Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=512583:512623 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=521502:521564 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6319256064229376 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.
,
Dec 5 2017
ClusterFuzz testcase 6319256064229376 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Dec 5 2017
,
Mar 13 2018
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
,
Mar 27 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sheriffbot@chromium.org
, Nov 15 2017