Issue metadata
Sign in to add a comment
|
Heap-buffer-overflow in getAddress |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6313397730410496 Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Heap-buffer-overflow READ 8 Crash Address: 0x62d00004e400 Crash State: getAddress sw::Array<sw::Float4, 1>::operator Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=521502:521564 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6313397730410496 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Feb 24 2018
,
Feb 24 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
,
Feb 24 2018
,
Feb 24 2018
+awhalley@, could you ptal and assign to appropriate dev pls? Thank you.
,
Feb 25 2018
M65 Stable promotion is coming VERY soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. Merge has to happen latest by 1:00 PM PT Tuesday (02/27/18) in order to make it to last M65 beta release next week. Thank you.
,
Feb 26 2018
,
Feb 26 2018
,
Mar 7 2018
,
Mar 12 2018
sugoi: Uh oh! This issue still open and hasn't been updated in the last 14 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers? If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one? If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 27 2018
sugoi: Uh oh! This issue still open and hasn't been updated in the last 29 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers? If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one? If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 13 2018
The following revision refers to this bug: https://swiftshader.googlesource.com/SwiftShader.git/+/329747ca1c0fc80010ac55f2fa41c22d3c56c1a0 commit 329747ca1c0fc80010ac55f2fa41c22d3c56c1a0 Author: Alexis Hetu <sugoi@google.com> Date: Fri Apr 13 12:07:22 2018 Added check for temporary register overflow Currently, when overflowing the number of temporary registers allowed, SwiftShader will crash somewhere in the generated code. This cl adds an early check to prevent the crash and instead output an error message to the user. Bug chromium:814987 Change-Id: Idadda21ee14298662763d986ee1283a5114c1c01 Reviewed-on: https://swiftshader-review.googlesource.com/18388 Tested-by: Alexis Hétu <sugoi@google.com> Reviewed-by: Nicolas Capens <nicolascapens@google.com> [modify] https://crrev.com/329747ca1c0fc80010ac55f2fa41c22d3c56c1a0/src/Main/Config.hpp [modify] https://crrev.com/329747ca1c0fc80010ac55f2fa41c22d3c56c1a0/src/OpenGL/compiler/OutputASM.cpp [modify] https://crrev.com/329747ca1c0fc80010ac55f2fa41c22d3c56c1a0/src/Shader/PixelProgram.hpp [modify] https://crrev.com/329747ca1c0fc80010ac55f2fa41c22d3c56c1a0/src/Shader/VertexProgram.hpp
,
Apr 18 2018
,
Apr 20 2018
ClusterFuzz has detected this issue as fixed in range 552045:552055. Detailed report: https://clusterfuzz.com/testcase?key=6313397730410496 Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Heap-buffer-overflow READ 8 Crash Address: 0x62d00004e400 Crash State: getAddress sw::Array<sw::Float4, 1>::operator Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=521502:521564 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=552045:552055 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6313397730410496 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 20 2018
ClusterFuzz testcase 6313397730410496 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Apr 20 2018
,
May 29 2018
,
Jul 23
,
Jul 27
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
, Feb 23 2018Labels: Test-Predator-Auto-Components