Issue metadata
Sign in to add a comment
|
Crash in base::UncheckedMalloc |
||||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=4722880040665088 Fuzzer: miaubiz_svg_fuzzer Job Type: windows_syzyasan_chrome Platform Id: windows Crash Type: UNKNOWN Crash Address: 0x002ce607 Crash State: base::UncheckedMalloc base::UncheckedCalloc sk_calloc Recommended Security Severity: Medium Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_syzyasan_chrome&range=411158:411207 Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97UbZL7Bftlb5uTJpumkRgO9LEcU7BaC_PC5FpwWbP5_yHB_jPNrCkommESqTiXgBkrOJpNdyT1BRNxSlz3dRXt-5tTOtzMM4yR5cqSYe1hzperBC-oz1MgusqxgpYzGEPWvMZbkD24RIpHWqox5NQM8m0XB6F_QsGHUGo-VS0TAgcyUM8?testcase_id=4722880040665088 Issue manually filed by: mmoroz See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Aug 16 2016
,
Aug 16 2016
This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 16 2016
,
Aug 16 2016
,
Aug 30 2016
reed: 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
,
Sep 1 2016
,
Sep 6 2016
Friendly ping, this is currently a Beta-blocker and needs to get fixed and merged as soon as feasible, as M54 is going to beta this Thursday 9/8
,
Sep 7 2016
Moving to ReleaseBlock-Stable to keep track of this for M54
,
Sep 13 2016
reed: Uh oh! This issue still open and hasn't been updated in the last 28 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
,
Sep 28 2016
Friendly ping, this a stable blocker for M54, please try to have a fix in by the first week of October so it can be fixed in time for the release.
,
Oct 7 2016
Hi reed@ - anybody else who could take a look if you're not going to get to this soon? Cheers!
,
Oct 10 2016
,
Oct 11 2016
,
Oct 11 2016
Per #13 moving to M55, Sheriffbot will always add RBS back to medium/high severity issues with Security_Impact-Beta
,
Oct 12 2016
CF Unable to reproduce, closing.
,
Oct 13 2016
,
Jan 19 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 mmoroz@chromium.org
, Aug 16 2016Labels: Pri-2
Owner: reed@chromium.org