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.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/e2e9d0b71ded5408aaa0b469791fc1df4fcf1648 (Signed Exchange: Switch to b1 envelope format).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

This should be fixed by http://crrev.com/564428.

ClusterFuzz has detected this issue as fixed in range 564422:564430.

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

Fuzzer: libFuzzer_signed_exchange_envelope_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Heap-buffer-overflow READ 8
Crash Address: 0x603000008513
Crash State:
  content::SignedExchangePrologue::Parse
  signed_exchange_envelope_fuzzer.cc
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=563561:563577
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=564422:564430

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

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.

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