Skip to content
Fencer Intel
medium 5.5

CVE-2015-8929 json

Memory leak in the __archive_read_get_extract function in archive_read_extract2.c in libarchive before 3.2.0 allows remote attackers to cau…

published 2016-09-20 10 y ago modified 2026-06-17 4 mo ago also EUVD-2015-8785

cvss
5.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

Summary

Memory leak in the __archive_read_get_extract function in archive_read_extract2.c in libarchive before 3.2.0 allows remote attackers to cause a denial of service via a tar file.

Patch / fix

  • libarchive Debian 14, Debian 13, Debian 12 3.2.0-2

debian advisories DEBIAN-CVE-2015-8929

  • bsdtar Studio Onsite 1.3, SLES for SAP 11 SP4, SLES 11 SP4 +8 more 2.5.5-9.1
  • libarchive SLES for SAP 12 SP1, SLES 12 SP1, SLED 12 SP1 +1 more 3.1.2-22.1

suse advisories SUSE-SU-2016:1939-1SUSE-SU-2016:1909-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-8929 updated cvss 3.5

libarchive: Memory leak in TAR parser

  • Red Hat Enterprise Linux 6 libarchive Red Hat Enterprise Linux 7 bsdtar, bsdcpio, libarchive
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.54% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/libarchive/libarchive/issues/517 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.