Issue metadata
Sign in to add a comment
|
Incorrect-function-pointer-type in _hb_blob_destroy_user_data |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5975138029010944 Fuzzer: libFuzzer_renderer_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Incorrect-function-pointer-type Crash Address: Crash State: _hb_blob_destroy_user_data hb_blob_destroy hb_face_t::get_upem Sanitizer: undefined (UBSAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=496738:496798 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5975138029010944 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Aug 24 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
,
Aug 24 2017
,
Aug 24 2017
The repro case is 1 byte, which seems implausible. There don't seem to be any changes to fonts within the regression range?
,
Aug 25 2017
I can reproduce this on Goobuntu. msw@, would you be the right person to fix this?
,
Aug 25 2017
No, my text rendering work has been for chrome browser ui, not the blink renderer (they're completely separate harfbuzz clients). Hopefully drott@ or eae@ can triage.
,
Sep 4 2017
,
Sep 4 2017
Behdad, are these more instances of https://github.com/behdad/harfbuzz/issues/474 ?
,
Sep 5 2017
Yes.
,
Sep 5 2017
Downgrading this to same severity as issue 696729 and removing ReleaseBlock-Stable.
,
Sep 5 2017
,
Sep 5 2017
,
Sep 6 2017
,
Oct 1 2017
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
,
Oct 18 2017
,
Oct 24 2017
For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md. The link referenced in the description is no longer valid.
,
Oct 31 2017
Issue 761694 has been merged into this issue.
,
Nov 3 2017
ClusterFuzz has detected this issue as fixed in range 513517:513548. Detailed report: https://clusterfuzz.com/testcase?key=5975138029010944 Fuzzer: libFuzzer_renderer_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Incorrect-function-pointer-type Crash Address: Crash State: _hb_blob_destroy_user_data hb_blob_destroy hb_face_t::get_upem Sanitizer: undefined (UBSAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=496738:496798 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=513517:513548 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5975138029010944 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.
,
Nov 3 2017
ClusterFuzz testcase 6020511204376576 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Nov 3 2017
,
Nov 7 2017
,
Dec 4 2017
,
Feb 9 2018
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 sheriffbot@chromium.org
, Aug 24 2017