VulnerabilityPublished 8 May 2024Updated 4 Nov 2025

CVE-2024-27282: ruby · Out-of-bounds Read

Affects rubySource CVE Database V5

Not known to be exploited · CVSS 6.6 Medium · fixed in 3.3.1 : update ruby when convenient.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

6.6Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.3.1, 3.2.4, 3.1.5 +1

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade ruby to 3.3.1, 3.2.4, 3.1.5 or 3.0.7.

Affected software

Product	Affected	Fixed in
RubyGemsruby`pkg:gem/ruby`Other threats	Affected <3.0.7 >=3.0.7 <3.1.5 >=3.1.5 <3.2.4 >=3.2.4 <3.3.1	Fixed in 3.0.7 3.1.5 3.2.4 3.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade Ruby installations to the fixed versions: 3.0.7, 3.1.5, 3.2.4, or 3.3.1, depending on their current version. Where immediate patching is not feasible, restrict access to systems running vulnerable Ruby versions to trusted users only and monitor for unusual regex compilation activities or anomalous user input patterns. Implement input validation and sanitization to limit attacker-controlled data reaching the regex compiler. Employ runtime application self-protection (RASP) or memory protection tools to detect and prevent out-of-bounds memory reads. Conduct code reviews and security testing focused on regex usage in applications. Additionally, audit logs for suspicious user interactions that could indicate exploitation attempts. For critical systems, consider isolating Ruby processes or running them with minimal privileges to reduce the attack surface. Finally, maintain an up-to-date inventory of Ruby versions in use across the organization to ensure comprehensive remediation.

Description

An issue was discovered in Ruby 3.x through 3.3.0. 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. The fixed versions are 3.0.7, 3.1.5, 3.2.4, and 3.3.1.

Impact

For European organizations, the primary impact of CVE-2024-27282 is the potential leakage of sensitive information from heap memory, which could include cryptographic keys, authentication tokens, or other confidential data processed or stored in memory during regex operations. This can lead to confidentiality breaches, undermining data protection obligations under regulations such as GDPR. Organizations running Ruby-based web applications, middleware, or automation tools that accept user input for regex processing are at risk. Although the attack requires local access and user interaction, insider threats or compromised user accounts could exploit this vulnerability to escalate data exposure. The limited impact on integrity and availability reduces the risk of service disruption but does not diminish the importance of protecting sensitive data. The vulnerability could also facilitate further attacks if leaked pointers or strings enable attackers to craft more sophisticated exploits. Given the widespread use of Ruby in European software development and production environments, especially in sectors like finance, healthcare, and government, the risk of data leakage is significant if unpatched.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 17:05 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats