Service interruption via optimized-away font bounds check
Published Apr 24, 2024 · Updated Aug 1, 2024
Out-of-bounds array write in Xpdf before 4.05 allows local users to interrupt PDF processing via an invalid Type 1 font. The character-code bounds check used while processing the font is optimized away by modern compilers, allowing an invalid code to index beyond the array. Triggering the write requires an affected binary to process a PDF containing the invalid font code, and the documented consequence is service interruption rather than data disclosure or modification.
Summary
What happened
Out-of-bounds array write in Xpdf before 4.05 allows local users to interrupt PDF processing via an invalid Type 1 font. The character-code bounds check used while processing the font is optimized away by modern compilers, allowing an invalid code to index beyond the array. Triggering the write requires an affected binary to process a PDF containing the invalid font code, and the documented consequence is service interruption rather than data disclosure or modification.
The record
- CVE
- CVE-2024-4141
- Published
- Apr 24, 2024
- Updated
- Aug 1, 2024
- Vendor
- Glyph & Cog, LLC
- Product
- Xpdf
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.05
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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