Converter crash via out-of-bounds DCT read
Published Jul 21, 2021 · Updated Aug 4, 2024
Out-of-bounds read in DCTStream::decodeImage in PDF2JSON 0.70 allows local users to crash the converter with a crafted PDF file. The JPEG decoder reads four-byte values past the end of a heap allocation while processing malformed DCT stream data. Execution requires the converter to process the file; the demonstrated result is an abort that interrupts the conversion process.
Summary
What happened
Out-of-bounds read in DCTStream::decodeImage in PDF2JSON 0.70 allows local users to crash the converter with a crafted PDF file. The JPEG decoder reads four-byte values past the end of a heap allocation while processing malformed DCT stream data. Execution requires the converter to process the file; the demonstrated result is an abort that interrupts the conversion process.
The record
- CVE
- CVE-2020-19471
- Published
- Jul 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- PoC_aborted_DCTStream::decodeImageproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo