Skip to content

Product

debian/lrzip vulnerabilities

31 published CVES affecting debian/lrzip, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
31
Critical
2
High
2
Medium
23
Low
0
Unscored
4
CISA KEV
0

Latest debian/lrzip CVEs

Newest publication first · page 1 of 2

  1. MediumCVSS 4.8 EPSS 0.19%

    A security vulnerability has been detected in ckolivas lrzip up to 0.651. This vulnerability affects the function ucompthread of the file stream.c. Such manipulation leads to null pointer dereference. The attack can only be performed from a local environment. The exploit has been...

  2. MediumCVSS 4.8 EPSS 0.23%

    A vulnerability was found in ckolivas lrzip up to 0.651. This impacts the function lzma_decompress_buf of the file stream.c. Performing a manipulation results in use after free. Attacking locally is a requirement. The exploit has been made public and could be used. The project wa...

  3. MediumCVSS 5.5 EPSS 0.70%

    Lrzip v0.651 was discovered to contain multiple invalid arithmetic shifts via the functions get_magic in lrzip.c and Predictor::init in libzpaq/libzpaq.cpp. These vulnerabilities allow attackers to cause a Denial of Service via unspecified vectors.

  4. MediumCVSS 5.5 EPSS 0.87%

    lrzip v0.641 was discovered to contain a multiple concurrency use-after-free between the functions zpaq_decompress_buf() and clear_rulist(). This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted Irz file.

  5. MediumCVSS 5.5 EPSS 1.2%

    The lzo1x_decompress function in liblzo2.so.2 in LZO 2.10, as used in Long Range Zip (aka lrzip) 0.631, allows remote attackers to cause a denial of service (invalid memory read and application crash) via a crafted archive, a different vulnerability than CVE-2017-8845.

  6. CriticalCVSS 9.8 EPSS 2.4%

    In Long Range Zip (aka lrzip) 0.631, there is a use-after-free in the lzma_decompress_buf function of stream.c, which allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact.

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.