CVE-2015-8919: The lha_read_file_extended_header function in archive_read_support_format_lha.c in libarchive before 3.2.0 allows remote attackers to cause…
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.5% (FIRST EPSS); higher than 91.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: libarchive (Debian:12) 3.2.0-2; libarchive (Debian:7) 3.0.4-3+wheezy2; libarchive (Debian:8) 3.1.2-11+deb8u2.
Low priority for now. Upgrade to libarchive (Debian:12) 3.2.0-2; libarchive (Debian:7) 3.0.4-3+wheezy2; libarchive (Debian:8) 3.1.2-11+deb8u2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The lha_read_file_extended_header function in archive_read_support_format_lha.c in libarchive before 3.2.0 allows remote attackers to cause a denial of service (out-of-bounds heap) via a crafted (1) lzh or (2) lha file.
- Published
- Sep 20, 2016
- Updated
- Jun 16, 2026
- EPSS
- 4.5% · 91th percentile
- CWE
- CWE-119
Report tools
Action score
31
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| libarchive | libarchive | cpe:2.3:a:libarchive:libarchive |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| novell | suse linux enterprise software development kit | cpe:2.3:a:novell:suse_linux_enterprise_software_development_kit |
| novell | suse linux enterprise desktop | cpe:2.3:o:novell:suse_linux_enterprise_desktop |
| novell | suse linux enterprise server | cpe:2.3:o:novell:suse_linux_enterprise_server |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux12.04
- canonical ubuntu linux14.04
- canonical ubuntu linux15.10
- canonical ubuntu linux16.04
- libarchive libarchiveup to 3.1.901a inclusive
- novell suse linux enterprise desktop12.0
- novell suse linux enterprise server12.0
- novell suse linux enterprise software development kit12.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libarchive | before 3.2.0-2 | 3.2.0-2 |
| Debian:7 | libarchive | before 3.0.4-3+wheezy2 | 3.0.4-3+wheezy2 |
| Debian:8 | libarchive | before 3.1.2-11+deb8u2 | 3.1.2-11+deb8u2 |
| Red Hat:enterprise_linux:7::client | bsdcpio | before 0:3.1.2-10.el7_2 | 0:3.1.2-10.el7_2 |
| Red Hat:enterprise_linux:7::client | bsdtar | before 0:3.1.2-10.el7_2 | 0:3.1.2-10.el7_2 |
| Red Hat:enterprise_linux:7::client | libarchive | before 0:3.1.2-10.el7_2 | 0:3.1.2-10.el7_2 |
| Red Hat:enterprise_linux:7::client | libarchive-debuginfo | before 0:3.1.2-10.el7_2 | 0:3.1.2-10.el7_2 |
| Red Hat:enterprise_linux:7::client | libarchive-devel | before 0:3.1.2-10.el7_2 | 0:3.1.2-10.el7_2 |
| SUSE:Linux Enterprise Desktop 12 SP1 | libarchive | before 3.1.2-22.1 | 3.1.2-22.1 |
Same product
libarchive: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-26256Libarchive Remote Code Execution Vulnerability57Plan
- CVE-2022-36227In libarchive before 3.6.2, the software does not check for an error after calling calloc function that can return with a NULL pointer if…40Plan
- CVE-2016-1541Heap-based buffer overflow in the zip_read_mac_metadata function in archive_read_support_format_zip.c in libarchive before 3.2.0 allows…38Monitor
Published before and after this one in the same product
- ← EarlierCVE-2015-8917Sep 20, 2016 · bsdtar in libarchive before 3.2.0 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via an invalid…31Monitor
- ← EarlierCVE-2015-8918Sep 20, 2016 · The archive_string_append function in archive_string.c in libarchive before 3.2.0 allows remote attackers to cause a denial of service…31Monitor
- Later →CVE-2015-8920Sep 20, 2016 · The _ar_read_header function in archive_read_support_format_ar.c in libarchive before 3.2.0 allows remote attackers to cause a denial of…23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libarchive | 3.2.0-2 · Debian:12 | Package registry (OSV) |
| red hat:bsdcpio | 0:3.1.2-10.el7_2 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:bsdtar | 0:3.1.2-10.el7_2 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libarchive | 0:3.1.2-10.el7_2 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libarchive-debuginfo | 0:3.1.2-10.el7_2 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libarchive-devel | 0:3.1.2-10.el7_2 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| suse:libarchive | 3.1.2-22.1 · SUSE:Linux Enterprise Desktop 12 SP1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- rhn.redhat.com/errata/RHSA-2016-1844.html
- www.debian.org/security/2016/dsa-3657
- www.openwall.com/lists/oss-security/2016/06/17/2
- www.openwall.com/lists/oss-security/2016/06/17/5
- www.oracle.com/technetwork/topics/security/linuxbulletinjul2016-3090544.html
- www.securityfocus.com/bid/91302
- www.ubuntu.com/usn/USN-3033-1
- blog.fuzzing-project.org/47-Many-invalid-memory-access-issues-in-libarchive.html
- github.com/libarchive/libarchive/issues/510
- security.gentoo.org/glsa/201701-03
Vendor advisories and official records. Exploit/PoC links are deliberately left out.