pdfunite crash via unchecked embedded-file stream
Published Aug 22, 2023 · Updated Nov 3, 2025
Reachable assertion in Poppler 22.07.0 allows context-dependent attackers to crash pdfunite through a crafted PDF file. The pdfunite main function treats an embedded-file object as a stream and saves it without first checking the object type, triggering an assertion when the object is malformed. A user must process the crafted PDF with pdfunite; exploitation terminates that process without reading or altering data.
Summary
What happened
Reachable assertion in Poppler 22.07.0 allows context-dependent attackers to crash pdfunite through a crafted PDF file. The pdfunite main function treats an embedded-file object as a stream and saves it without first checking the object type, triggering an assertion when the object is malformed. A user must process the crafted PDF with pdfunite; exploitation terminates that process without reading or altering data.
The record
- CVE
- CVE-2022-37051
- Published
- Aug 22, 2023
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-617, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2023CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- SIGABRT at poppler/Object.h:435 (pdfunite)proof 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