Search Results (42 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2019-19635 1 Saitoha 1 Libsixel 2026-04-24 9.8 Critical
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer overflow in the function sixel_decode_raw_impl at fromsixel.c.
CVE-2019-19777 2 Nothings, Saitoha 2 Stb Image.h, Libsixel 2026-04-24 8.8 High
stb_image.h (aka the stb image loader) 2.23, as used in libsixel and other products, has a heap-based buffer over-read in stbi__load_main.
CVE-2019-19637 1 Saitoha 1 Libsixel 2026-04-24 9.8 Critical
An issue was discovered in libsixel 1.8.2. There is an integer overflow in the function sixel_decode_raw_impl at fromsixel.c.
CVE-2019-19638 1 Saitoha 1 Libsixel 2026-04-24 9.8 Critical
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer overflow in the function load_pnm at frompnm.c, due to an integer overflow.
CVE-2019-20024 1 Saitoha 1 Libsixel 2026-04-24 6.5 Medium
A heap-based buffer overflow was discovered in image_buffer_resize in fromsixel.c in libsixel before 1.8.4.
CVE-2019-20140 1 Saitoha 1 Libsixel 2026-04-24 8.8 High
An issue was discovered in libsixel 1.8.4. There is a heap-based buffer overflow in the function gif_out_code at fromgif.c.
CVE-2019-20205 1 Saitoha 1 Libsixel 2026-04-24 8.8 High
libsixel 1.8.4 has an integer overflow in sixel_frame_resize in frame.c.
CVE-2020-19668 1 Saitoha 1 Libsixel 2026-04-24 6.5 Medium
Unverified indexs into the array lead to out of bound access in the gif_out_code function in fromgif.c in libsixel 1.8.6.
CVE-2022-29977 1 Saitoha 1 Libsixel 2026-04-24 6.5 Medium
There is an assertion failure error in stbi__jpeg_huff_decode, stb_image.h:1894 in libsixel img2sixel 1.8.6. Remote attackers could leverage this vulnerability to cause a denial-of-service via a crafted JPEG file.
CVE-2022-27044 1 Saitoha 1 Libsixel 2026-04-24 8.8 High
libsixel 1.8.6 is affected by Buffer Overflow in libsixel/src/quant.c:876.
CVE-2018-19761 1 Saitoha 1 Libsixel 2026-04-24 N/A
There is an illegal address access at fromsixel.c (function: sixel_decode_raw_impl) in libsixel 1.8.2 that will cause a denial of service.
CVE-2019-19778 1 Saitoha 1 Libsixel 2026-04-24 8.8 High
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer over-read in the function load_sixel at loader.c.
CVE-2019-20022 1 Saitoha 1 Libsixel 2026-04-24 6.5 Medium
An invalid memory address dereference was discovered in load_pnm in frompnm.c in libsixel before 1.8.3.
CVE-2019-20023 1 Saitoha 1 Libsixel 2026-04-24 6.5 Medium
A memory leak was discovered in image_buffer_resize in fromsixel.c in libsixel 1.8.4.
CVE-2019-3573 1 Saitoha 1 Libsixel 2026-04-24 N/A
In libsixel v1.8.2, there is an infinite loop in the function sixel_decode_raw_impl() in the file fromsixel.c, as demonstrated by sixel2png.
CVE-2018-14073 1 Saitoha 1 Libsixel 2026-04-24 N/A
libsixel 1.8.1 has a memory leak in sixel_allocator_new in allocator.c.
CVE-2025-61146 1 Saitoha 1 Libsixel 2026-04-23 4 Medium
saitoha libsixel until v1.8.7 was discovered to contain a memory leak via the component malloc_stub.c.
CVE-2026-33018 1 Saitoha 1 Libsixel 2026-04-23 7 High
libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. Versions 1.8.7 and prior contain a Use-After-Free vulnerability via the load_gif() function in fromgif.c, where a single sixel_frame_t object is reused across all frames of an animated GIF and gif_init_frame() unconditionally frees and reallocates frame->pixels between frames without consulting the object's reference count. Because the public API explicitly provides sixel_frame_ref() to retain a frame and sixel_frame_get_pixels() to access the raw pixel buffer, a callback following this documented usage pattern will hold a dangling pointer after the second frame is decoded, resulting in a heap use-after-free confirmed by ASAN. Any application using sixel_helper_load_image_file() with a multi-frame callback to process user-supplied animated GIFs is affected, with a reliable crash as the minimum impact and potential for code execution. This issue has been fixed in version 1.8.7-r1.
CVE-2026-33019 1 Saitoha 1 Libsixel 2026-04-23 7.1 High
libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. Versions 1.8.7 and prior contain an integer overflow leading to an out-of-bounds heap read in the --crop option handling of img2sixel, where positive coordinates up to INT_MAX are accepted without overflow-safe bounds checking. In sixel_encoder_do_clip(), the expression clip_w + clip_x overflows to a large negative value when clip_x is INT_MAX, causing the bounds guard to be skipped entirely, and the unclamped coordinate is passed through sixel_frame_clip() to clip(), which computes a source pointer far beyond the image buffer and passes it to memmove(). An attacker supplying a specially crafted crop argument with any valid image can trigger an out-of-bounds read in the heap, resulting in a reliable crash and potential information disclosure. This issue has been fixed in version 1.8.7-r1.
CVE-2026-33020 1 Saitoha 1 Libsixel 2026-04-23 7.1 High
libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. Versions 1.8.7 and prior contain an integer overflow which leads to a heap buffer overflow via sixel_frame_convert_to_rgb888() in frame.c, where allocation size and pointer offset computations for palettised images (PAL1, PAL2, PAL4) are performed using int arithmetic before casting to size_t. For images whose pixel count exceeds INT_MAX / 4, the overflow produces an undersized heap allocation for the conversion buffer and a negative pointer offset for the normalization sub-buffer, after which sixel_helper_normalize_pixelformat() writes the full image data starting from the invalid pointer, causing massive heap corruption confirmed by ASAN. An attacker providing a specially crafted large palettised PNG can corrupt the heap of the victim process, resulting in a reliable crash and potential arbitrary code execution. This issue has been fixed in version 1.8.7-r1.