Libmspack Project vulnerabilitiesNone on the known-exploited list.

Vendor
The short answer

Libmspack Project has 11 published vulnerabilities across 1 product in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Libmspack, with 11. If you run Libmspack Project software, patch the exploited flaws first.

See the exploited flaws

We keep watching the known-exploited list.

Products

Which Libmspack Project products have the most vulnerabilities?

Libmspack leads with 11 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.

  1. Libmspack11
Published vulnerabilities
Known exploited

Which Libmspack Project vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Libmspack Project's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Libmspack Project flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 7.1%

    The cabd_extract function in cabd.c in libmspack before 0.5 does not properly maintain decompression callbacks in certain cases where an invalid file follows a valid file, which allows remote attackers to cause a...

    CVSS4.3Published11 Jun 2015
  2. 3.1%

    In mspack/cab.h in libmspack before 0.8alpha and cabextract before 1.8, the CAB block input buffer is one byte too small for the maximal Quantum block, leading to an out-of-bounds write.

    CVSS6.5Published23 Oct 2018
  3. 2.8%

    Integer overflow in the qtmd_decompress function in libmspack 0.4 allows remote attackers to cause a denial of service (hang) via a crafted CAB file, which triggers an infinite loop.

    CVSS5.0Published3 Feb 2015
  4. 2.3%

    Off-by-one error in the lzxd_decompress function in lzxd.c in libmspack before 0.5 allows remote attackers to cause a denial of service (buffer under-read and application crash) via a crafted CAB archive.

    CVSS4.3Published11 Jun 2015
  5. 2.1%

    The cabd_read_string function in mspack/cabd.c in libmspack 0.5alpha, as used in ClamAV 0.99.2 and other products, allows remote attackers to cause a denial of service (stack-based buffer over-read and application...

    CVSS5.5Published18 Jul 2017
  6. 2.0%

    mspack/lzxd.c in libmspack 0.5alpha, as used in ClamAV 0.99.2, allows remote attackers to cause a denial of service (heap-based buffer overflow and application crash) or possibly have unspecified other impact via a...

    CVSS7.8Published7 Aug 2017
  7. 1.6%

    Off-by-one error in the READ_ENCINT macro in chmd.c in libmspack before 0.5 allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted CHM file.

    CVSS6.8Published11 Jun 2015
  8. 1.4%

    The chmd_init_decomp function in chmd.c in libmspack before 0.5 does not properly validate the reset interval, which allows remote attackers to cause a denial of service (divide-by-zero error and application crash)...

    CVSS4.3Published11 Jun 2015
  9. 1.4%

    The chmd_read_headers function in chmd.c in libmspack before 0.5 does not validate name lengths, which allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted CHM file.

    CVSS4.3Published11 Jun 2015
  10. 1.4%

    Multiple integer overflows in the search_chunk function in chmd.c in libmspack before 0.5 allow remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted CHM file.

    CVSS4.3Published11 Jun 2015
Every product

All Libmspack Project products we track.

1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.

Precursor Intelligence

Running Libmspack Project? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

Our catalogue lists 11 published vulnerabilities across 1 product and 7 versions from Libmspack Project.

None of Libmspack Project's vulnerabilities is on the list of flaws known to be exploited today.

Libmspack, with 11 published vulnerabilities. Its own page lists the ones known to be exploited.

Create a Precursor Intelligence account and track the Libmspack Project products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.