OSV-2017-22
Heap-buffer-overflow in opj_tcd_mct_decode
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3331
Crash type: Heap-buffer-overflow READ 4
Crash state:
opj_tcd_mct_decode
opj_tcd_decode_tile
opj_j2k_decode_tile
What each source reports
OSV No score
Heap-buffer-overflow in opj_tcd_mct_decode
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3331
Crash type: Heap-buffer-overflow READ 4
Crash state:
opj_tcd_mct_decode
opj_tcd_decode_tile
opj_j2k_decode_tile
- Record
OSV-2017-22- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
openjpegOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2017-22 is a vulnerability with no CVSS score yet in openjpeg, published January 13, 2021. No source lists public exploit code. A source reports a fix.