Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2015-8923

libarchive: Unclear crashes in ZIP parser

Overview

Published
20 Sep 2016
Modified
6 May 2026
Medium CVE
0 Registry packages
5 OS packages
5 Linux distributions
Yes Fix available

Description

The process_extra function in libarchive before 3.2.0 uses the size field and a signed number in an offset, which allows remote attackers to cause a denial of service (crash) via a crafted zip file.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Weakness: CWE-20

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 9 fixes

Oracle Linux 1 release · 1 package

fixed 1
bsdcpio
Oracle Linux fixes for CVE-2015-8923
ReleasePackageFixed in
7 bsdcpio +3 3.1.2-10.el7_2

Red Hat 1 release · 1 package

fixed 1
bsdcpio
Red Hat fixes for CVE-2015-8923
ReleasePackageFixed inAdvisory
7 bsdcpio +3 0:3.1.2-10.el7_2 RHSA-2016:1844

debian 4 releases · 1 package

fixed 4
libarchive
debian fixes for CVE-2015-8923
ReleasePackageFixed in
11 libarchive 3.2.0-2
12 libarchive 3.2.0-2
13 libarchive 3.2.0-2
14 libarchive 3.2.0-2

echo 1 release · 1 package

fixed 1
libarchive
echo fixes for CVE-2015-8923
ReleasePackageFixed in
libarchive 3.2.0-2

root.io debian 2 releases · 1 package

fixed 2
rootio-libarchive
root.io debian fixes for CVE-2015-8923
ReleasePackageFixed in
11 rootio-libarchive 3.2.0-2
12 rootio-libarchive 3.2.0-2

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.