Memory exhaustion via unreleased jfif_decode allocations
Published Aug 16, 2022 · Updated Aug 3, 2024
Memory leaks in ffjpeg before 2021-12-16 allow context-dependent attackers to exhaust memory by decoding a crafted JPEG file. jfif_decode allocates two 256-byte buffers at line 404 and three one-byte buffers at lines 443-445, then leaves them unreleased on the reproduced decode path. Exploitation requires a user or consuming application to decode the crafted file; repeated decoding progressively consumes memory and interrupts service.
Summary
What happened
Memory leaks in ffjpeg before 2021-12-16 allow context-dependent attackers to exhaust memory by decoding a crafted JPEG file. jfif_decode allocates two 256-byte buffers at line 404 and three one-byte buffers at lines 443-445, then leaves them unreleased on the reproduced decode path. Exploitation requires a user or consuming application to decode the crafted file; repeated decoding progressively consumes memory and interrupts service.
The record
- CVE
- CVE-2022-35433
- Published
- Aug 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- 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
- Upstream sample-file memory-leak 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