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://pdfium.googlesource.com/pdfium/+/0f567261d33a70860bb3ec3db4cf1185df1a9a54 (Make PDF_DataDecode()'s buffer out parameter a std::unique_ptr.).

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.

ClusterFuzz has detected this issue as fixed in range 599500:599501.

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

Fuzzer: libFuzzer_pdfium_xfa_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Heap-use-after-free READ 1
Crash Address: 0x602000004770
Crash State:
  fxcrt::UnownedPtr<unsigned char const>::ProbeForLowSeverityLifetimeIssue
  fxcrt::UnownedPtr<unsigned char const>::~UnownedPtr
  pdfium::span<unsigned char const>::~span
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=599296:599305
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=599500:599501

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

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