Process crash via unchecked GIF LZW code size
Published Sep 14, 2021 · Updated Aug 4, 2024
Stack buffer overflow in Libsixel before 1.8.3 allows context-dependent attackers to crash GIF-consuming processes via a crafted GIF. The gif_process_raster function accepts an LZW minimum code size above 12, derives indices from it, and writes outside its fixed 4,096-entry codes table. Processing attacker-supplied GIF content is required, and successful exploitation interrupts the consuming process by causing a crash.
Summary
What happened
Stack buffer overflow in Libsixel before 1.8.3 allows context-dependent attackers to crash GIF-consuming processes via a crafted GIF. The gif_process_raster function accepts an LZW minimum code size above 12, derives indices from it, and writes outside its fixed 4,096-entry codes table. Processing attacker-supplied GIF content is required, and successful exploitation interrupts the consuming process by causing a crash.
The record
- CVE
- CVE-2020-21050
- Published
- Sep 14, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 14, 2021CVE 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
- so_fromgif.c:310_1.gif crashing inputproof of concept · demonstrated
- so_fromgif.c:310_2.gif crashing inputproof 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