LiveActive security incident?Get immediate response
CVE Record

CVE-2012-5371: Ruby (aka CRuby) 1.9 before 1.9.3-p327 and 2.0 before r37575 computes hash values without properly restrict...

Ruby (aka CRuby) 1.9 before 1.9.3-p327 and 2.0 before r37575 computes hash values without properly restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table, as demonstrated by a universal multicollision attack against a variant of the MurmurHash2 algorithm, a different vulnerability than CVE-2011-4815.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a denial-of-service issue in old CRuby runtimes. Specially crafted input can make Ruby spend excessive CPU time handling hash tables, potentially slowing or stopping affected applications. It matters mainly for legacy systems still running Ruby 1.9 before 1.9.3-p327 or Ruby 2.0 before r37575. Exposure is most likely in legacy Ruby applications that accept attacker-controlled input and process it into Ruby hash tables. The source bundle identifies Ruby 1.9 before 1.9.3-p327 and Ruby 2.0 before r37575. Prioritize if any business-critical or internet-facing service still runs the affected Ruby versions. For modern supported Ruby stacks, urgency is lower, but legacy inventory should be verified because exploitation causes availability impact rather than data theft. Mitigation focus: Upgrade CRuby 1.9 to 1.9.3-p327 or later vendor-supported packages.; For Ruby 2.0 development builds, verify inclusion of r37575 or later fixes.; Apply distribution security updates from vendors such as Ubuntu or Red Hat where applicable..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2012-5371 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.