Issue metadata
Sign in to add a comment
|
Heap-buffer-overflow in angle::LoadToNative<signed |
||||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4899784885010432 Fuzzer: webDEViL_webgl Job Type: windows_asan_chrome_with_gpu Platform Id: windows Crash Type: Heap-buffer-overflow READ {*} Crash Address: 0x12f10b731b84 Crash State: angle::LoadToNative<signed rx::Image11::loadData rx::TextureD3D::initializeContents Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=550440:550450 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4899784885010432 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Apr 19 2018
,
Apr 19 2018
Not fixed, c#3,#4 were flake.
,
Apr 19 2018
Yet another regression from https://chromium.googlesource.com/angle/angle/+/56c8577b4dbf2239780e38090dadbeb06f4b8563
,
Apr 20 2018
ClusterFuzz has detected this issue as fixed in range 552146:552148. Detailed report: https://clusterfuzz.com/testcase?key=4899784885010432 Fuzzer: webDEViL_webgl Job Type: windows_asan_chrome_with_gpu Platform Id: windows Crash Type: Heap-buffer-overflow READ {*} Crash Address: 0x12f10b731b84 Crash State: angle::LoadToNative<signed rx::Image11::loadData rx::TextureD3D::initializeContents Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=550440:550450 Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=552146:552148 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4899784885010432 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Apr 20 2018
,
Apr 20 2018
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
,
Apr 20 2018
,
Apr 21 2018
,
Apr 24 2018
,
Apr 24 2018
ClusterFuzz has detected this issue as fixed in range 552581:552589. Detailed report: https://clusterfuzz.com/testcase?key=4899784885010432 Fuzzer: webDEViL_webgl Job Type: windows_asan_chrome_with_gpu Platform Id: windows Crash Type: Heap-buffer-overflow READ {*} Crash Address: 0x12f10b731b84 Crash State: angle::LoadToNative<signed rx::Image11::loadData rx::TextureD3D::initializeContents Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=550440:550450 Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=552581:552589 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4899784885010432 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Apr 25 2018
,
Aug 1
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 aarya@google.com
, Apr 19 2018Components: Internals>GPU>Internals
Owner: kbr@chromium.org
Status: Assigned (was: Untriaged)