Image-conversion crash via oversized resize dimensions
Published Jan 1, 2020 · Updated Aug 5, 2024
Integer overflow in sixel_frame_resize in libsixel 1.8.4 allows attackers to crash image conversion through oversized dimensions. The function accepts user-controlled width and height values, and very large values produce an overflowing allocation request in frame.c. Triggering the failure requires processing attacker-influenced dimensions; the published proof demonstrates an allocation abort, not code execution.
Summary
What happened
Integer overflow in sixel_frame_resize in libsixel 1.8.4 allows attackers to crash image conversion through oversized dimensions. The function accepts user-controlled width and height values, and very large values produce an overflowing allocation request in frame.c. Triggering the failure requires processing attacker-influenced dimensions; the published proof demonstrates an allocation abort, not code execution.
The record
- CVE
- CVE-2019-20205
- Published
- Jan 1, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 1, 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
- Oversized resize-dimensions 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