This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Fixing Component based on file path of  third_party/pdfium/core/fxcodec/codec/fx_codec_fax.cpp

thestig@ could you please look into this and assign an appropriate owner if needed? 

This issue appears very similar to  issue 648935 . It looks like we just turned on fuzzing for this area (via https://chromium.googlesource.com/chromium/src/+/a6dc4f682f6db2b4792963ef5a26929d8a728f2a)

Now that the fax fuzzer is finding bugs... any interest in taking them?

ClusterFuzz has detected this issue as fixed in range 420640:420782.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6334813751738368

Fuzzer: libfuzzer_pdf_codec_fax_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x7f27e8074f74
Crash State:
  FindBit
  FaxG4FindB1B2
  FaxG4GetRow
  
Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=419790:419892
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=420640:420782

Minimized Testcase (3.48 Kb): https://cluster-fuzz.appspot.com/download/AMIfv969GOJ2xme-fJgcH7UBq1cFyYnxcJFyWNuLF1NA5l5sQn7PdP06kQ4tYjqkq5VbXEduDnFN69vDTBqqUHhTxWWCVmx7mNUlP5Q1ifX3BOmOKrmMAqxvw8XoGBenWOzqvMtezNUTa3FzyeP9qsYPQ1oo84Nd1A?testcase_id=6334813751738368

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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