Excessive memory consumption via ignored limit
Published Jun 15, 2020 · Updated Aug 4, 2024
Uncontrolled resource consumption in IJG JPEG before 9d allows attackers to exceed a configured memory limit via JPEG processing. In jmemnobs.c, jpeg_mem_available() returns max_bytes_needed instead of subtracting allocated memory from max_memory_to_use, so djpeg ignores the configured cap. The gate is an application that processes a memory-intensive JPEG with the no-backing-store manager; the consequence is memory use beyond that cap, not data modification.
Summary
What happened
Uncontrolled resource consumption in IJG JPEG before 9d allows attackers to exceed a configured memory limit via JPEG processing. In jmemnobs.c, jpeg_mem_available() returns max_bytes_needed instead of subtracting allocated memory from max_memory_to_use, so djpeg ignores the configured cap. The gate is an application that processes a memory-intensive JPEG with the no-backing-store manager; the consequence is memory use beyond that cap, not data modification.
The record
- CVE
- CVE-2020-14152
- Published
- Jun 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
No public exploit references are available in this record.
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