Application crash via null Huffman decoder dereference
Published Aug 18, 2022 · Updated Aug 3, 2024
Memory corruption in libjpeg commit 281daa9 allows attackers to crash applications that decode a crafted JPEG file. LosslessScan::ParseMCU invokes HuffmanDecoder::Get through a null decoder pointer while reconstructing the malformed stream. An application must process the attacker-supplied image; the demonstrated result is a segmentation fault and process crash.
Summary
What happened
Memory corruption in libjpeg commit 281daa9 allows attackers to crash applications that decode a crafted JPEG file. LosslessScan::ParseMCU invokes HuffmanDecoder::Get through a null decoder pointer while reconstructing the malformed stream. An application must process the attacker-supplied image; the demonstrated result is a segmentation fault and process crash.
The record
- CVE
- CVE-2022-37769
- Published
- Aug 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 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.
Weakness, pattern, technique
Public exploit references
- HuffmanDecoder::Get crash reproducerproof 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