Crash in blink::FontCache::CrashWithFontInfo |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4905298644172800 Fuzzer: inferno_twister Job Type: windows_asan_chrome_no_sandbox Platform Id: windows Crash Type: UNKNOWN READ Crash Address: 0x833f3200 Crash State: blink::FontCache::CrashWithFontInfo blink::FontFallbackIterator::Next blink::FontFallbackIterator::Next Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=480259:480271 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4905298644172800 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jun 19 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 19 2017
,
Jun 19 2017
kojii, PTAL?
,
Jun 19 2017
CHECK failure is not a security bug, we fixed the parsing logic on clusterfuzz side, sorry for noise.
,
Jun 26 2017
Removing RBS because of #5 and because this is non-reproducible. I'll see it a while more if this can reproduce. This is an intentional crash to track down issue 561873.
,
Jul 11 2017
,
Jul 17 2017
WontFix since we could not reproduce it after a while. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by sheriffbot@chromium.org
, Jun 19 2017