CVE-2019-8906

Description

A vulnerability has been identified in the File Project, specifically in the do_core_note function within readelf.c of libmagic.a where, an out-of-bounds read, can be exploited by a local attacker using a specially crafted file which could result in a denial of service or leakage of sensitive information.

Statement

This vulnerability was rated as LOW severity because its exploitation requires a local attacker to use a specially crafted file and it results in temporary application crashes or exposure of limited information, it does not allow remote code execution or system compromise.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert: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 v3 Score Breakdown

Red HatNVDcve.org
Base Score4.44.4N/A
Attack VectorLocalLocalN/A
Attack ComplexityLowLowN/A
Privileges RequiredLowLowN/A
User InteractionNoneNoneN/A
ScopeUnchangedUnchangedN/A
ConfidentialityLowLowN/A
Integrity ImpactNoneNoneN/A
Availability ImpactLowLowN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

Red Hat CVSS v3 Score Explanation

This buffer over-read vulnerability can not be exploited for arbitrary code execution, only to cause a transient crash (A:L) or disclosure of non-sensitive memory content (C:L). No Integrity impact is possible (I:N). The file utility is not normally bound to the network, and if executed by a network service a crash will not impact that service. Local access is required (AV:L/PR:L).

Understanding the Weakness (CWE)

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

Want to get errata notifications? Sign up here.