Memory corruption via out-of-bounds grayscale pixel write
Published Aug 16, 2022 · Updated Aug 3, 2024
Global buffer overflow in JPEGDEC commit be4843c allows context-dependent attackers to corrupt memory via a crafted JPEG image. JPEGPutMCU8BitGray writes a decoded grayscale byte 1,120 bytes past the 16,384-byte ucDitherBuffer in src/jpeg.inl. An application must decode the malicious file; the published reproducer triggers an AddressSanitizer abort, while code execution is not demonstrated.
Summary
What happened
Global buffer overflow in JPEGDEC commit be4843c allows context-dependent attackers to corrupt memory via a crafted JPEG image. JPEGPutMCU8BitGray writes a decoded grayscale byte 1,120 bytes past the 16,384-byte ucDitherBuffer in src/jpeg.inl. An application must decode the malicious file; the published reproducer triggers an AddressSanitizer abort, while code execution is not demonstrated.
The record
- CVE
- CVE-2022-35003
- Published
- Aug 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 16, 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
- JPEGDEC global-buffer-overflow crash sampleproof 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