CVE-2024-27282

Description

A flaw was found in Ruby. If attacker-supplied data is provided to the Ruby regex compiler, it is possible to extract arbitrary heap data relative to the start of the text, including pointers and sensitive strings.

Statement

The CVE-2024-27282 vulnerability in Ruby is classified as a Moderate severity issue due to its potential to expose arbitrary heap data relative to the start of the text through the Ruby regex compiler. While the vulnerability allows the extraction of pointers and sensitive strings from memory, its exploitation requires attacker-supplied data to be provided to the regex compiler. This means that an attacker would need to craft specific input to exploit the issue, limiting the ease of exploitation compared to vulnerabilities that might be remotely exploitable without user interaction.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

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

Red HatNVDcve.org
Base Score6.6N/A6.6
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionRequiredN/ARequired
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactLowN/ALow
Availability ImpactLowN/ALow

Vector

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

cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L

Red Hat CVSS v3 Score Explanation

Confidentiality[High]: This vulnerability allows attackers to extract arbitrary heap data, including potentially sensitive strings. Therefore, it directly impacts the confidentiality of the system, as sensitive information could be exposed to unauthorized parties.

Integrity[Low]: Since attackers can extract arbitrary heap data, including pointers, there's a risk of data manipulation and corruption. This affects the integrity of the system, as the data could be altered in unauthorized ways.

Availability[Low]: While this vulnerability doesn't directly affect the availability of the system, if exploited, it could potentially lead to denial of service (DoS) attacks or other disruptions, especially if the attacker can manipulate data.

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.