Skip to content
Fencer Intel
medium 5.0

CVE-2012-2739 json

Oracle Java SE before 7 Update 6, and OpenJDK 7 before 7u6 build 12 and 8 before build 39, computes hash values without restricting the abi…

published 2012-11-28 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-2719

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

Summary

Oracle Java SE before 7 Update 6, and OpenJDK 7 before 7u6 build 12 and 8 before build 39, computes hash values without 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.

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-2739 updated cvss 5.0

java: hash table collisions CPU usage DoS (oCERT-2011-003)

  • Red Hat Enterprise Linux 4 java-1.5.0-ibm, java-1.6.0-ibm, java-1.6.0-sun, java-1.6.0-sun-src, java-1.6.0-sun-demo, java-1.6.0-sun-jdbc, +2 more Red Hat Enterprise Linux 5 java-1.5.0-ibm, java-1.6.0-ibm, java-1.6.0-sun, java-1.6.0-openjdk, java-1.6.0-sun-src, java-1.6.0-sun-demo, +3 more Red Hat Enterprise Linux 6 java-1.5.0-ibm, java-1.6.0-ibm, java-1.6.0-sun, java-1.5.0-ibm-src, java-1.6.0-ibm-src, java-1.6.0-openjdk, +15 more
    affected: no fix planned “Will not fix”

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

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

Exploits and checks

  • armoredbarista.blogspot.de http://armoredbarista.blogspot.de/2012/02/investigating-hashdos-issue.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness

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.