CVE-2009-5146

Description

[REJECTED CVE] A memory leak flaw was fix in the hostname TLS extension. This flaw was introduced with the backport of the TLS extension code first introduced in version 0.9.8k of openssl.

Statement

This issue did not affect any versions of OpenSSL as shipped with Red Hat Enterprise Linux 5, 6, and 7.

Also, this CVE has been rejected, because investigation showed that it was not a security issue.

Red Hat has evaluated this issue and determined that it does not meet the criteria to be classified as a security vulnerability. This assessment is based on the issue not posing a significant security risk, being a result of misconfiguration or usage error, or falling outside the scope of security considerations.

As such, this CVE has been marked as "Rejected" in alignment with Red Hat's vulnerability management policies.

If you have additional information or concerns regarding this determination, please contact Red Hat Product Security for further clarification.

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 v2 Score Breakdown

Red HatNVDcve.org
Base Score5N/AN/A
Attack VectorNetworkN/AN/A
Access ComplexityLowN/AN/A
AuthenticationNoneN/AN/A
Confidentiality ImpactNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactPartialN/AN/A

Vector

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

Understanding the Weakness (CWE)

Availability

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

Most memory leaks result in general product reliability problems, but if an attacker can intentionally trigger a memory leak, the attacker might be able to launch a denial of service attack (by crashing or hanging the program) or take advantage of other unexpected program behavior resulting from a low memory condition.

Other

Technical Impact: Reduce Performance

Frequently Asked Questions

Want to get errata notifications? Sign up here.