New issue
Advanced search Search tips

Issue 761245 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Security



Sign in to add a comment

Incorrect-function-pointer-type in _hb_blob_destroy_user_data

Project Member Reported by ClusterFuzz, Sep 1 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=6327734241591296

Fuzzer: libFuzzer_harfbuzz_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Incorrect-function-pointer-type
Crash Address: 
Crash State:
  _hb_blob_destroy_user_data
  _try_writable
  hb_blob_get_data_writable
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=424217:424275

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6327734241591296

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 
Cc: e...@chromium.org
Components: Blink>Fonts
Labels: Pri-1
Owner: drott@chromium.org
Status: Assigned (was: Untriaged)
drott: this looks similar to  Issue 758478 . Do you mind taking a look please?
Project Member

Comment 2 by sheriffbot@chromium.org, Sep 1 2017

Labels: M-62
Project Member

Comment 3 by sheriffbot@chromium.org, Sep 1 2017

Labels: ReleaseBlock-Stable
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

Comment 4 by drott@chromium.org, Sep 4 2017

Cc: behdad@chromium.org

Comment 5 by drott@chromium.org, Sep 4 2017

Behdad, are these more instances of https://github.com/behdad/harfbuzz/issues/474 ?
Yes, looks like it.  I'll try to fix those soon.

Comment 7 by drott@chromium.org, Sep 5 2017

Labels: -Security_Severity-Medium -ReleaseBlock-Stable Security_Severity-Low
Downgrading this to same severity as  issue 696729  and removing ReleaseBlock-Stable.
Project Member

Comment 8 by sheriffbot@chromium.org, Sep 5 2017

Labels: -Pri-1 Pri-2
Project Member

Comment 9 by sheriffbot@chromium.org, Sep 6 2017

Labels: -Security_Impact-Head Security_Impact-Beta
Project Member

Comment 10 by ClusterFuzz, Oct 1 2017

Labels: Test-Predator-AutoComponents
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 11 by sheriffbot@chromium.org, Oct 18 2017

Labels: -Security_Impact-Beta Security_Impact-Stable
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.
Project Member

Comment 13 by ClusterFuzz, Nov 3 2017

ClusterFuzz has detected this issue as fixed in range 513517:513548.

Detailed report: https://clusterfuzz.com/testcase?key=6327734241591296

Fuzzer: libFuzzer_harfbuzz_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Incorrect-function-pointer-type
Crash Address: 
Crash State:
  _hb_blob_destroy_user_data
  _try_writable
  hb_blob_get_data_writable
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=424217:424275
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=513517:513548

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6327734241591296

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.
Project Member

Comment 14 by ClusterFuzz, Nov 3 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 6327734241591296 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Project Member

Comment 15 by sheriffbot@chromium.org, Nov 3 2017

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components
Labels: -M-62 M-64
Labels: Release-0-M64
Project Member

Comment 19 by sheriffbot@chromium.org, Feb 9 2018

Labels: -Restrict-View-SecurityNotify allpublic
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