Issue metadata
Sign in to add a comment
|
Heap-buffer-overflow in ft_glyphslot_alloc_bitmap |
||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=4900387710042112 Fuzzer: attekett_surku_fuzzer Job Type: linux_lsan_chrome_mp Platform Id: linux Crash Type: Heap-buffer-overflow READ 4 Crash Address: 0x603000e63c99 Crash State: ft_glyphslot_alloc_bitmap Load_SBit_Image tt_face_load_sbit_image Recommended Security Severity: Low Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=383126:383194 Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv952OJF_R20n1UteVCTjA1o5Nlsi6vyx5DuTT3MiZui0N9n9PuIuIUwF1sfmkgxw4ukNfF1bMx_nE0gv_gzffp7dv3HB7UWxhnCf1zqf3FeIjymSVvL7V7FkFslk4Mw1wqxnXqCjqx8TQcrTH00I-N4Ze9PPOw Additional requirements: Requires Gestures Filer: mmoroz See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Apr 1 2016
,
Apr 4 2016
,
Apr 4 2016
,
Apr 5 2016
,
Apr 21 2016
bungeman: Uh oh! This issue still open and hasn't been updated in the last 19 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
,
May 6 2016
bungeman: Uh oh! This issue still open and hasn't been updated in the last 34 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
,
May 24 2016
This isn't in Skia, and the code doesn't ship. The code in question is what ships on Ubuntu Precise, so if one thinks it should be fixed for users the appropriate fix would be to track down the fix for this issue in FreeType and open a bug in launchpad against Canonical requesting the patch be ported to affected versions of FreeType (in particular Ubuntu Precise). If it's accepted it will eventually be patched into the Chromium branch of FreeType which mirrors the code in Precise. I have plans to keep Chrome as close as possible to tip of tree FreeType, allowing builders of Chromium to use whichever FreeType they wish (much like the HarfBuzz situation). However, getting this set up will take some time.
,
May 24 2016
Well, we discussed freetype in several places (all are blocked on bug 594972 ). My understanding is that we have to keep those bugs open until update/remove of freetype. Am I wrong and may be we should WontFix them and ignore in the future?
,
May 26 2016
,
May 27 2016
,
May 27 2016
Discussed this offline. I'm going to mark this as stable impacting even though it depends on system freetype. ExternalDependency is more appropriate on its own.
,
Jul 21 2016
,
Sep 1 2016
,
Oct 10 2016
,
Oct 13 2016
,
Dec 2 2016
,
Jan 1 2017
ClusterFuzz testcase 4900387710042112 is flaky and no longer reproduces, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Apr 10 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
, Apr 1 2016Cc: mmoroz@chromium.org
Owner: bunge...@chromium.org