CVE-2026-33019
Description
A flaw was found in libsixel. An attacker can trigger an integer overflow in the image processing component, img2sixel, by supplying a specially crafted crop argument. This vulnerability leads to an out-of-bounds memory read, which can cause the application to crash, resulting in a Denial of Service, and potentially expose sensitive information.
Statement
Important: A flaw in libsixel allows an attacker to trigger an integer overflow in the img2sixel component by providing a specially crafted crop argument. This can lead to an out-of-bounds memory read, causing a Denial of Service and potential information disclosure. Red Hat products utilizing libsixel for image processing, particularly with the img2sixel utility and its crop functionality, may be affected if processing untrusted input.
Mitigation
The vulnerability in `libsixel`'s `img2sixel` utility is triggered by processing untrusted input via the `--crop` option. To mitigate this, avoid using `img2sixel` with untrusted or unvalidated input. Restrict execution of `img2sixel` to trusted users and environments where input can be controlled.
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (Memory); DoS: Instability
This weakness can generally lead to undefined behavior and therefore crashes. When the calculated result is used for resource allocation, this weakness can cause too many (or too few) resources to be allocated, possibly enabling crashes if the product requests more resources than can be provided.
Integrity
Technical Impact: Modify Memory
If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the overflow/wraparound results in other conditions such as buffer overflows, further memory corruption may occur.
Confidentiality,Availability,Access Control
Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism
This weakness can sometimes trigger buffer overflows, which can be used to execute arbitrary code. This is usually outside the scope of the product's implicit security policy.
Availability,Other
Technical Impact: Alter Execution Logic; DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU)
If the overflow/wraparound occurs in a loop index variable, this could cause the loop to terminate at the wrong time - too early, too late, or not at all (i.e., infinite loops). With too many iterations, some loops could consume too many resources such as memory, file handles, etc., possibly leading to a crash or other DoS.
Access Control
Technical Impact: Bypass Protection Mechanism
If integer values are used in security-critical decisions, such as calculating quotas or allocation limits, integer overflows can be used to cause an incorrect security decision.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
