Application crash via freed JBIG2 stream access
Published Aug 15, 2022 · Updated Aug 3, 2024
Use-after-free in JBIG2Stream::close() in Xpdf 4.04 allows attackers to crash a PDF-processing application with a crafted PDF file. While closing a JBIG2 stream, the function accesses an object after its storage has been freed; public sources do not identify the specific stale reference. A user or automated workflow must open or process the file, and the reliably documented consequence is an application crash; other impact is unspecified.
Summary
What happened
Use-after-free in JBIG2Stream::close() in Xpdf 4.04 allows attackers to crash a PDF-processing application with a crafted PDF file. While closing a JBIG2 stream, the function accesses an object after its storage has been freed; public sources do not identify the specific stale reference. A user or automated workflow must open or process the file, and the reliably documented consequence is an application crash; other impact is unspecified.
The record
- CVE
- CVE-2022-38222
- Published
- Aug 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 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
- Crafted PDF trigger for JBIG2Stream::close()proof 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