Application crash via gfseek out-of-bounds write
Published Sep 30, 2022 · Updated May 20, 2025
Out-of-bounds write in Xpdf 4.04 allows context-dependent attackers to crash the application by opening a crafted PDF file. The failure occurs in gfseek in goo/gfile.cc, but public material does not disclose which PDF field drives the invalid write or which bounds check is absent. Successful exploitation requires user interaction with the crafted file and interrupts only the affected Xpdf process.
Summary
What happened
Out-of-bounds write in Xpdf 4.04 allows context-dependent attackers to crash the application by opening a crafted PDF file. The failure occurs in gfseek in goo/gfile.cc, but public material does not disclose which PDF field drives the invalid write or which bounds check is absent. Successful exploitation requires user interaction with the crafted file and interrupts only the affected Xpdf process.
The record
- CVE
- CVE-2022-41842
- Published
- Sep 30, 2022
- Updated
- May 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 30, 2022CVE publishedPublication date reported by the CVE source.
- May 20, 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.
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
- Xpdf forum gfseek 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