This one also looks very similar to 666892. Should check after that is fixed.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

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

Assigning to npm@ to take a look after 666892 is fixed.

The following revision refers to this bug:
  https://pdfium.googlesource.com/pdfium/+/9bdbc16e3c8f30e32a1f399543d04ac5b1e9c97c

commit 9bdbc16e3c8f30e32a1f399543d04ac5b1e9c97c
Author: Nicolas Pena <npm@chromium.org>
Date: Fri May 05 20:39:51 2017

Fix undefined shift in opj_bio_read

Bug:  chromium:666683 
Change-Id: I1c633d82e9ef75dd99ef032b4fc46fe8d3651cd1
Reviewed-on: https://pdfium-review.googlesource.com/5050
Commit-Queue: Nicolás Peña <npm@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>

[add] https://crrev.com/9bdbc16e3c8f30e32a1f399543d04ac5b1e9c97c/third_party/libopenjpeg20/0031-undefined-shift-opj_bio_read.patch
[modify] https://crrev.com/9bdbc16e3c8f30e32a1f399543d04ac5b1e9c97c/third_party/libopenjpeg20/README.pdfium
[modify] https://crrev.com/9bdbc16e3c8f30e32a1f399543d04ac5b1e9c97c/third_party/libopenjpeg20/bio.c

ClusterFuzz has detected this issue as fixed in range 469836:469843.

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

Fuzzer: libfuzzer_pdf_jpx_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  opj_bio_read
  opj_t2_read_packet_header
  opj_t2_decode_packet
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=395640:395746
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=469836:469843

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


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.

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

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