Process crash in AcroForm handling
Published Aug 30, 2022 · Updated Aug 3, 2024
A segmentation fault in Xpdf 4.04 allows context-dependent attackers to crash an Xpdf utility by supplying a crafted PDF file. Processing reaches AcroForm.cc line 538, where the public record identifies the fault but does not disclose the invalid operation. A user or automated workflow must process the file with an affected utility; the supported consequence is process termination and service interruption.
Summary
What happened
A segmentation fault in Xpdf 4.04 allows context-dependent attackers to crash an Xpdf utility by supplying a crafted PDF file. Processing reaches AcroForm.cc line 538, where the public record identifies the fault but does not disclose the invalid operation. A user or automated workflow must process the file with an affected utility; the supported consequence is process termination and service interruption.
The record
- CVE
- CVE-2022-36561
- Published
- Aug 30, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 30, 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.
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
- Xpdf forum crash reproducerproof of concept · unverified
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