Issue metadata
Sign in to add a comment
|
Heap-buffer-overflow in (unknown) |
||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5826328342560768 Fuzzer: inferno_twister Job Type: windows_syzyasan_content_shell Platform Id: windows Crash Type: Heap-buffer-overflow READ 16 Crash Address: 0x2F3D1C4F Crash State: (unknown) (unknown) SHStrDupA+256 Memory Tool: SYZYASAN Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=479947:479966 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5826328342560768 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jun 17 2017
,
Jun 17 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
,
Jun 17 2017
,
Jun 19 2017
Looks like we're hitting this a lot in CF (250k+ crashes/day). I haven't looked closely, but given the frequency I would expect this to be a tool issue. sebmarchand: Any idea what's going on here? Looks like this started up on the 16th.
,
Jun 19 2017
Ha, it's probably because of an issue that we're having right now with SyzyAsan, I'm working on fixing it.
,
Jun 20 2017
,
Jun 21 2017
Issue 734014 has been merged into this issue.
,
Jun 21 2017
Any updates on this ?
,
Jun 21 2017
The problem has been fixed on the Syzygy side, I'm rolling Syzygy deps in https://codereview.chromium.org/2947213002/
,
Jun 21 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/38734eca6b4e3d9cd60606e7150723402494b710 commit 38734eca6b4e3d9cd60606e7150723402494b710 Author: sebmarchand <sebmarchand@chromium.org> Date: Wed Jun 21 21:43:41 2017 Roll Syzygy deps to v0.8.31.0 Changelog: [e2fe0d0e41] Fail if we can't intercept a CRT function and add support for Win10 SDK versions 10.0.10586.0 and 10.0.15063.0. BUG= 734109 Review-Url: https://codereview.chromium.org/2947213002 Cr-Commit-Position: refs/heads/master@{#481314} [modify] https://crrev.com/38734eca6b4e3d9cd60606e7150723402494b710/DEPS
,
Jun 22 2017
ClusterFuzz has detected this issue as fixed in range 481254:481399. Detailed report: https://clusterfuzz.com/testcase?key=5826328342560768 Fuzzer: inferno_twister Job Type: windows_syzyasan_content_shell Platform Id: windows Crash Type: Heap-buffer-overflow READ 16 Crash Address: 0x2F3D1C4F Crash State: (unknown) (unknown) SHStrDupA+256 Memory Tool: SYZYASAN Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=479947:479966 Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=481254:481399 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5826328342560768 See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jun 22 2017
ClusterFuzz testcase 5566189958070272 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jun 22 2017
,
Jul 26 2017
,
Sep 28 2017
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 est...@chromium.org
, Jun 16 2017