CVE-2019-20162

An issue was discovered in GPAC version 0.8.0 and 0.9.0-development-20191109. There is heap-based buffer overflow in the function gfisomboxparseex in isomedia/boxfuncs.c...

CVE-2019-20140

An issue was discovered in libsixel 1.8.4. There is a heap-based buffer overflow in the function gifoutcode at fromgif.c...

CVE-2019-20140

CVE-2019-20140 affects libsixel 1.8.4, with a heap-based buffer overflow in the function gif_out_code in fromgif.c. This is corroborated by Red Hat’s advisory and multiple CVE aggregators. The available documents do not specify a patched version or workaround. References point to Libsixel issue #...

CVE-2019-20088

GoPro GPMF-parser 1.2.3 has a heap-based buffer over-read in GetPayload in GPMFmp4reader.c...

CVE-2019-20089

GoPro GPMF-parser 1.2.3 has an heap-based buffer over-read in GPMFSeekToSamples in GPMFparse.c for the size calculation...

Heap overflow

GoPro GPMF-parser 1.2.3 has a heap-based buffer over-read in GetPayload in GPMFmp4reader.c...

Heap overflow

GoPro GPMF-parser 1.2.3 has a heap-based buffer over-read in GPMFNext in GPMFparser.c...

CVE-2019-20086

GoPro GPMF-parser 1.2.3 has a heap-based buffer over-read in GPMFNext in GPMFparser.c...

CVE-2019-20087

GoPro GPMF-parser 1.2.3 is affected by a heap-based buffer over-read in GPMF_seekToSamples (GPMF-parse.c) related to the "matching tags" feature. The issue is reported across multiple sources (NVD, Red Hat, OSV, CVE lists) and is tied to CVE-2019-20087. The vulnerability description consistently ...

CVE-2019-20089

GoPro GPMF-parser 1.2.3 has an heap-based buffer over-read in GPMFSeekToSamples in GPMFparse.c for the size calculation...

CVE-2019-20089

Affected software: GoPro GPMF-parser 1.2.3. Issue: a heap-based buffer over-read in GPMF_SeekToSamples within GPMF_parse.c used for size calculation. Root cause per description: reading beyond allocated memory boundaries, enabling an out-of-bounds read. Impact described in the sources as a heap/b...

CVE-2019-15903

In libexpat before 2.2.8, crafted XML input could fool the parser into changing from DTD parsing to document parsing too early; a consecutive call to XMLGetCurrentLineNumber or XMLGetCurrentColumnNumber then resulted in a heap-based buffer over-read. Mitigation Mitigation for this issue is either...

CVE-2019-20024

A heap-based buffer overflow was discovered in imagebufferresize in fromsixel.c in libsixel before 1.8.4...

CVE-2019-20011

An issue was discovered in GNU LibreDWG 0.92. There is a heap-based buffer over-read in decodeR13R2000 in decode.c...

CVE-2019-20011

An issue was discovered in GNU LibreDWG 0.92. There is a heap-based buffer over-read in decodeR13R2000 in decode.c...

Heap overflow

An issue was discovered in GNU LibreDWG 0.92. There is a heap-based buffer over-read in decodeR13R2000 in decode.c...

CVE-2019-20021

CVE-2019-20021 affects UPX, where UPX 3.95 contains a heap-based buffer over-read in canUnpack() within p_mach.cpp when processing crafted Mach-O files. OpenSUSE/Fedora advisories indicate the fix is in UPX 3.96, which patches this vulnerability (and related CVEs) by updating to 3.96. Practical i...

CVE-2019-20024

CVE-2019-20024 impacts libsixel: a heap-based buffer overflow in image_buffer_resize (fromsixel.c) occurs in all versions before 1.8.4. The Red Hat entry reproduces this, and multiple PTSecurity notes discuss related libsixel issues. Public references indicate the vulnerability exists in the ment...

CVE-2019-20011

CVE-2019-20011 is a heap-based buffer over-read in GNU LibreDWG up to version 0.9.3 (decode_R13_R2000 in decode.c). OpenSUSE/SUSE advisories indicate this was addressed by releasing LibreDWG 0.9.3 with overflow checks and related fixes, and other documents corroborate the same vulnerability class...

CVE-2019-20005

An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxmldecode, while parsing a crafted XML file, performs incorrect memory handling, leading to a heap-based buffer over-read while running strchr starting with a pointer after a '\0' character where the processing of a string was...