Libarchive vulnerabilitiesNone on the known-exploited list.

Vendor
The short answer

Libarchive has 70 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 Libarchive, with 70. If you run Libarchive software, patch the exploited flaws first.

See the exploited flaws

We keep watching the known-exploited list.

Products

Which Libarchive products have the most vulnerabilities?

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

  1. Libarchive70
Published vulnerabilities
Known exploited

Which Libarchive vulnerabilities are being exploited?

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

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

Exploit likelihood

Which Libarchive 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. 88%

    Libarchive Remote Code Execution Vulnerability

    CVSS7.8Published9 Apr 2024
  2. 12%

    The ae_strtofflags function in archive_entry.c in libarchive before 3.2.0 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted mtree file.

    CVSS7.5Published20 Sep 2016
  3. 10%

    Heap-based buffer overflow in the zip_read_mac_metadata function in archive_read_support_format_zip.c in libarchive before 3.2.0 allows remote attackers to execute arbitrary code via crafted entry-size values in a...

    CVSS8.8Published7 May 2016
  4. 6.3%

    Integer overflow in the ISO9660 writer in libarchive before 3.2.1 allows remote attackers to cause a denial of service (application crash) or execute arbitrary code via vectors related to verifying filename lengths...

    CVSS8.6Published21 Sep 2016
  5. 5.4%

    The archive_read_format_tar_read_header function in archive_read_support_format_tar.c in libarchive before 3.2.0 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted tar file.

    CVSS5.5Published20 Sep 2016
  6. 5.3%

    Stack-based buffer overflow in the safe_fprintf function in tar/util.c in libarchive 3.2.1 allows remote attackers to cause a denial of service via a crafted non-printable multibyte character in a filename.

    CVSS7.5Published15 Feb 2017
  7. 4.9%

    Integer overflow in the read_SubStreamsInfo function in archive_read_support_format_7zip.c in libarchive before 3.2.1 allows remote attackers to execute arbitrary code via a 7zip file with a large number of...

    CVSS7.8Published21 Sep 2016
  8. 4.9%

    Absolute path traversal vulnerability in bsdcpio in libarchive 3.1.2 and earlier allows remote attackers to write to arbitrary files via a full pathname in an archive.

    CVSS6.4Published15 Mar 2015
  9. 4.8%

    The archive_read_format_cpio_read_header function in archive_read_support_format_cpio.c in libarchive before 3.2.1 allows remote attackers to cause a denial of service (application crash) via a CPIO archive with a...

    CVSS7.5Published21 Sep 2016
  10. 4.8%

    Heap-based buffer overflow in the parse_codes function in archive_read_support_format_rar.c in libarchive before 3.2.1 allows remote attackers to execute arbitrary code via a RAR file with a zero-sized dictionary.

    CVSS7.8Published21 Sep 2016
Every product

All Libarchive 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 Libarchive? 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 70 published vulnerabilities across 1 product and 51 versions from Libarchive.

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

Libarchive, with 70 published vulnerabilities. Its own page lists the ones known to be exploited.

Create a Precursor Intelligence account and track the Libarchive 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.