Process crash via eSYCC conversion buffer overflow
Published Feb 20, 2020 · Updated Aug 5, 2024
Heap-buffer overflow in color_esycc_to_rgb in OpenJPEG before 2.1.1 allows attackers to crash an image-decoding process via a crafted JPEG 2000 file. The conversion loop reads four bytes beyond an allocated component buffer, corrupting heap state that later fails during deallocation. Exploitation requires a user or application to decode attacker-controlled image content; the demonstrated consequence is process termination, not code execution.
Summary
What happened
Heap-buffer overflow in color_esycc_to_rgb in OpenJPEG before 2.1.1 allows attackers to crash an image-decoding process via a crafted JPEG 2000 file. The conversion loop reads four bytes beyond an allocated component buffer, corrupting heap state that later fails during deallocation. Exploitation requires a user or application to decode attacker-controlled image content; the demonstrated consequence is process termination, not code execution.
The record
- CVE
- CVE-2016-3182
- Published
- Feb 20, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1499.004, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
Weakness, pattern, technique
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