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/+/105ea1c0f896a4a2718f1356cae0dce8c01859cc (Avoid repeated calculations in CFX_BitStream::GetBits().).

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 561622:561640.

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

Fuzzer: afl_pdf_hint_table_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: Heap-buffer-overflow READ 1
Crash Address: 0x60e0000031dc
Crash State:
  CFX_BitStream::GetBits
  CPDF_HintTables::ReadSharedObjHintTable
  HintTableForFuzzing::Fuzz
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=561408:561422
Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=561622:561640

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

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