Skip to content
Fencer Intel
high 7.5

CVE-2012-0785 json

Hash collision attack vulnerability in Jenkins

published 2020-02-24 6 y ago modified 2026-06-16 4 mo ago also GHSA-pchp-c5w8-47gc , EUVD-2022-1797

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

Summary

Hash collision attack vulnerability in Jenkins before 1.447, Jenkins LTS before 1.424.2, and Jenkins Enterprise by CloudBees 1.424.x before 1.424.2.1 and 1.400.x before 1.400.0.11 could allow remote attackers to cause a considerable CPU load, aka "the Hash DoS attack."

Patch / fix

  • maven org.jenkins-ci.main:jenkins-core 1.424.2, 1.447
  • cloudbees jenkins 1.400.0.11, 1.424.2.1
  • jenkins jenkins 1.424.2, 1.447

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-0785 updated cvss 7.5

jenkins: hash collision allow remote attackers to cause a considerable CPU load resulting in Hash DoS

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

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.35% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 7.8 AV:N/AC:L/Au:N/C:N/I:N/A:C
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.main:jenkins-core
>=1.425, <1.447
<1.424.2
1.447
1.424.2

Affected products

  • Jenkins project Jenkins
  • Jenkins project Jenkins LTS
  • Jenkins project Jenkins Enterprise by CloudBees

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption
Technology feeds

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.