Skip to content
Fencer Intel
medium 5.0

CVE-2012-5370 json

JRuby denial of service via Hash Collision

published 2012-11-28 13 y ago modified 2026-09-10 1 mo ago also GHSA-fmmq-j7pq-f85c , EUVD-2022-3805

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

JRuby 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 the MurmurHash2 algorithm, a different vulnerability than CVE-2011-4838.

Patch / fix

  • maven org.jruby:jruby-parent 1.7.1
  • jruby Debian 14, Debian 13, Debian 12 1.5.6-5

debian advisories DEBIAN-CVE-2012-5370

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-5370 updated cvss 5.0

jruby: Murmur hash function collisions (oCERT-2012-001)

  • Red Hat JBoss SOA Platform 5 jruby jruby
    affected: no fix available
  • Red Hat Fuse ESB Enterprise 7.1.0
    fixed: vendor fix RHSA-2012:1604
  • Red Hat JBoss SOA Platform 5.3
    fixed: vendor fix RHSA-2013:0533

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.25% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Affected packages

ecosystem package affected fixed in
maven org.jruby:jruby-parent
<1.7.1
1.7.1

Classification

Weakness
  • CWE-310 Cryptographic Issues
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.