Cabextract vulnerabilitiesRanked by how likely they are to be used.

Product16 versions
The short answer

Cabextract is made by Cabextract Project. We track 9 published vulnerabilities in it, across 16 versions. None of them is on the list of flaws known to be exploited today. If you run Cabextract, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Cabextract vulnerabilities are being exploited?

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

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

Exploit likelihood

Which Cabextract 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. 4.0%

    Integer signedness error in the Quantum decompressor in cabextract before 1.3, when archive test mode is used, allows user-assisted remote attackers to cause a denial of service (application crash) or possibly...

    CVSS5.1Published9 Aug 2010
  2. 3.8%

    An issue was discovered in mspack/chmd.c in libmspack before 0.7alpha.

    CVSS8.8Published28 Jul 2018
  3. 3.8%

    An issue was discovered in kwajd_read_headers in mspack/kwajd.c in libmspack before 0.7alpha.

    CVSS8.8Published28 Jul 2018
  4. 3.7%

    An issue was discovered in mspack/chmd.c in libmspack before 0.7alpha.

    CVSS6.5Published28 Jul 2018
  5. 3.6%

    Directory traversal vulnerability in cabextract before 1.1 allows remote attackers to overwrite arbitrary files via a cabinet file containing ..

    CVSS5.0Published27 Jan 2005
  6. 3.3%

    An issue was discovered in mspack/chmd.c in libmspack before 0.7alpha.

    CVSS6.5Published28 Jul 2018
  7. 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
  8. 2.3%

    cabextract before 1.6 does not properly check for leading slashes when extracting files, which allows remote attackers to conduct absolute directory traversal attacks via a malformed UTF-8 character that is changed...

    CVSS5.3Published29 Nov 2019
  9. 2.3%

    The MS-ZIP decompressor in cabextract before 1.3 allows remote attackers to cause a denial of service (infinite loop) via a malformed MSZIP archive in a .cab file during a (1) test or (2) extract action, related to...

    CVSS4.3Published9 Aug 2010
Precursor Intelligence

Running Cabextract? 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 →

We track 9 published vulnerabilities listed under the name Cabextract, across 16 versions.

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

Create a Precursor Intelligence account and track Cabextract. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.