CVE-2015-0292

Description

An integer underflow flaw, leading to a buffer overflow, was found in the way OpenSSL decoded malformed Base64-encoded inputs. An attacker able to make an application using OpenSSL decode a specially crafted Base64-encoded input (such as a PEM file) could use this flaw to cause the application to crash. Note: this flaw is not exploitable via the TLS/SSL protocol because the data being transferred is not Base64-encoded.

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).

CVSS v2 Score Breakdown

Red HatNVDcve.org
Base Score5.17.5N/A
Attack VectorNetworkNetworkN/A
Access ComplexityHighLowN/A
AuthenticationNoneNoneN/A
Confidentiality ImpactPartialPartialN/A
Integrity ImpactPartialPartialN/A
Availability ImpactPartialPartialN/A

Vector

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

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

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Instability

This weakness will generally lead to undefined behavior and therefore crashes. In the case of overflows involving loop index variables, the likelihood of infinite loops is also high.

Integrity

Technical Impact: Modify Memory

If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the wrap around results in other conditions such as buffer overflows, further memory corruption may occur.

Confidentiality,Availability,Access Control

Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism

This weakness can sometimes trigger buffer overflows which can be used to execute arbitrary code. This is usually outside the scope of a program's implicit security policy.

Acknowledgements

Red Hat would like to thank OpenSSL project for reporting this issue. Upstream acknowledges David Ramos and Robert Dugal as the original reporters.

Frequently Asked Questions

Want to get errata notifications? Sign up here.