How severe is CVE-2012-5370?

No CVSS score has been assigned to CVE-2012-5370 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2012-5370?

CVE-2012-5370 affects the following packages: org.jruby:jruby-parent (Maven). Ecosystems affected: Maven.

How do I fix CVE-2012-5370?

Update org.jruby:jruby-parent to 1.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-5370 is resolved across your whole dependency graph.

How do I detect CVE-2012-5370 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jruby:jruby-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2012-5370 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2012-5370 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-5370 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2012-5370?

CVE-2012-5370 has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 83th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2012-5370?

CVE-2012-5370 is classified as CWE-310 (CWE-310). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2012-5370 published, and has it been updated?

CVE-2012-5370 was published on November 28, 2012 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2012-5370: jruby-parent DoS

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.jruby:jruby-parent

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jruby:jruby-parent`	all versions	1.7.1`org.jruby:jruby-parent:1.7.1`

Affected Products

1 product · 1 configurations

Application

jrubyjruby

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jruby:jruby-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jruby:jruby-parent to 1.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-5370 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

RHSA-2012:1604Fuse ESB Enterprise 7.1.0 RHSA-2013:0533Red Hat JBoss SOA Platform 5.3

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2012-5370 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2012-5370 — jruby-parent