Process crash via oversized high-color buffer copy
Published Aug 10, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in Libsixel 1.8.4 allows attackers to crash img2sixel by converting a crafted PNG image to SIXEL. In sixel_encoder_output_without_macro at encoder.c line 814, memcpy reads roughly 1.5 GB beyond the end of a roughly 36 MB heap allocation during high-color encoding. Execution requires the crafted image to reach an application that invokes Libsixel's high-color encoder; the demonstrated consequence is process termination.
Summary
What happened
Heap-based buffer overflow in Libsixel 1.8.4 allows attackers to crash img2sixel by converting a crafted PNG image to SIXEL. In sixel_encoder_output_without_macro at encoder.c line 814, memcpy reads roughly 1.5 GB beyond the end of a roughly 36 MB heap allocation during high-color encoding. Execution requires the crafted image to reach an application that invokes Libsixel's high-color encoder; the demonstrated consequence is process termination.
The record
- CVE
- CVE-2020-21677
- Published
- Aug 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 10, 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
- Crafted-image high-color conversion 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