There's a flaw in lz4. An attacker who submits a crafted file to an application linked with lz4 may be able to trigger an integer overflow, leading to calling of memmove() on a negative size argument, causing an out-of-bounds write and/or a crash. The greatest impact of this flaw...
Product
debian/lz4 vulnerabilities
6 published CVES affecting debian/lz4, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 1
- High
- 1
- Medium
- 2
- Low
- 0
- Unscored
- 2
- CISA KEV
- 0
Latest debian/lz4 CVEs
Newest publication first
-
CriticalCVSS 9.8 EPSS 3.4%
-
DSA-4919-1 lz4 - security update
PublishedUnknown -
DLA-2657-1 lz4 - security update
PublishedUnknown -
HighCVSS 8.1 EPSS 10.5%
LZ4 before 1.9.2 has a heap-based buffer overflow in LZ4_write32 (related to LZ4_compress_destSize), affecting applications that call LZ4_compress_fast with a large input. (This issue can also lead to data corruption.) NOTE: the vendor states "only a few specific / uncommon usage...
-
MediumCVSS 5.0 EPSS 2.8%
Yann Collet LZ4 before r119, when used on certain 32-bit platforms that allocate memory beyond 0x80000000, does not properly detect integer overflows, which allows context-dependent attackers to cause a denial of service (memory corruption) or possibly have unspecified other impa...
-
MediumCVSS 5.0 EPSS 8.9%
Integer overflow in the LZ4 algorithm implementation, as used in Yann Collet LZ4 before r118 and in the lz4_uncompress function in lib/lz4/lz4_decompress.c in the Linux kernel before 3.15.2, on 32-bit platforms might allow context-dependent attackers to cause a denial of service...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.