CVE-2015-8915

Public on

Last Modified: UTC

Description

The CVE Program describes this issue as:

bsdcpio in libarchive before 3.2.0 allows remote attackers to cause a denial of service (invalid read and crash) via crafted cpio file.

Additional information

  • Bugzilla 1216891: libarchive: crash via malformed cpio archive
  • CWE-125: Out-of-bounds Read
  • FAQ: Frequently asked questions about CVE-2015-8915

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v2 Score Breakdown
Red HatNVD

CVSS v2 Base Score

1.9

4.3

Attack Vector

Local

Network

Access Complexity

Medium

Medium

Authentication

None

None

Confidentiality Impact

None

None

Integrity Impact

None

None

Availability Impact

Partial

Partial

CVSS v2 Vector

Red Hat: AV:L/AC:M/Au:N/C:N/I:N/A:P

NVD: AV:N/AC:M/Au:N/C:N/I:N/A:P

Understanding the Weakness (CWE)

CWE-125

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?

What can I do if my product is listed as "Will not fix"?

What can I do if my product is listed as "Fix deferred"?

What is a mitigation?

I have a Red Hat product but it is not in the above list, is it affected?

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

Want to get errata notifications? Sign up here.