Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Fixed in HB master.  Dominik, can you do a roll?  Multiple CFF fuzzer-found issues have been fixed in this week.

Oh, Ben already did: https://chromium-review.googlesource.com/c/chromium/src/+/1365803

ClusterFuzz has detected this issue as fixed in range 614426:614571.

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

Fuzzer: libFuzzer_harfbuzz_fuzzer
Fuzz target binary: harfbuzz_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  CFF::DictOpSet::parse_bcd
  CFF::DictOpSet::process_op
  CFF::CFF1TopDictOpSet::process_op
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=613961:613964
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=614426:614571

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

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.

ClusterFuzz testcase 5012913062150144 is verified as fixed, so closing issue as verified.

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