Process crash via out-of-bounds DCT reset write
Published Jul 21, 2021 · Updated Aug 4, 2024
Out-of-bounds write in DCTStream::reset in PDF2JSON 0.70 allows attackers to crash the converter via a crafted PDF file. While processing the malformed DCT stream, DCTStream::reset writes eight bytes immediately past a 4,584-byte allocation. Opening or converting the attacker-supplied file is required; the resulting memory corruption terminates the process with SIGSEGV, without reported confidentiality or integrity impact.
Summary
What happened
Out-of-bounds write in DCTStream::reset in PDF2JSON 0.70 allows attackers to crash the converter via a crafted PDF file. While processing the malformed DCT stream, DCTStream::reset writes eight bytes immediately past a 4,584-byte allocation. Opening or converting the attacker-supplied file is required; the resulting memory corruption terminates the process with SIGSEGV, without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2020-19469
- Published
- Jul 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002, T1499.004
- 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.
Weakness, pattern, technique
Public exploit references
- PoC_segv_DCTStream::resetproof 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