Process crash via xref stream buffer over-read
Published Jul 22, 2022 · Updated Aug 3, 2024
Heap buffer over-read in QPDF 8.4.2 allows context-dependent attackers to crash the process via a crafted PDF file. QPDF::processXRefStream continues after decoded cross-reference data exceeds its computed size, then advances field reads beyond the heap buffer. Exploitation requires the file to be processed; the demonstrated consequence is an availability-only process abort.
Summary
What happened
Heap buffer over-read in QPDF 8.4.2 allows context-dependent attackers to crash the process via a crafted PDF file. QPDF::processXRefStream continues after decoded cross-reference data exceeds its computed size, then advances field reads beyond the heap buffer. Exploitation requires the file to be processed; the demonstrated consequence is an availability-only process abort.
The record
- CVE
- CVE-2022-34503
- Published
- Jul 22, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 22, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- HeapBOF-processXRefStream.zip reproducerproof 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