Memory corruption via unchecked error-diffusion index
Published Apr 8, 2022 · Updated Aug 4, 2024
Heap buffer overflow in libsixel before 1.10 allows remote attackers to corrupt memory by inducing processing of a crafted image. For a one-pixel-wide image, the Stucki path passes a negative pixel position to error_diffuse, which accesses memory before the allocated pixel buffer. Processing the crafted image with Stucki diffusion is required, and the published proof of concept aborts after corrupting the heap.
Summary
What happened
Heap buffer overflow in libsixel before 1.10 allows remote attackers to corrupt memory by inducing processing of a crafted image. For a one-pixel-wide image, the Stucki path passes a negative pixel position to error_diffuse, which accesses memory before the allocated pixel buffer. Processing the crafted image with Stucki diffusion is required, and the published proof of concept aborts after corrupting the heap.
The record
- CVE
- CVE-2021-40656
- Published
- Apr 8, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2022CVE 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
- Crafted one-pixel-wide image proof of conceptproof 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