Service interruption via colliding HTTP parameter keys
Published Feb 24, 2020 · Updated Aug 6, 2024
Hash-collision denial of service in Jenkins before 1.447 and LTS before 1.424.2 allows remote attackers to interrupt service via crafted HTTP data. Winstone processes attacker-controlled request keys in hash tables whose predictable collisions force excessive CPU work when parameter counts are not sufficiently limited. Unauthenticated network access to a Winstone-backed instance is sufficient; the resulting CPU exhaustion denies legitimate requests without disclosing data.
Summary
What happened
Hash-collision denial of service in Jenkins before 1.447 and LTS before 1.424.2 allows remote attackers to interrupt service via crafted HTTP data. Winstone processes attacker-controlled request keys in hash tables whose predictable collisions force excessive CPU work when parameter counts are not sufficiently limited. Unauthenticated network access to a Winstone-backed instance is sufficient; the resulting CPU exhaustion denies legitimate requests without disclosing data.
The record
- CVE
- CVE-2012-0785
- Published
- Feb 24, 2020
- Updated
- Aug 6, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 24, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before 1.424.2
- Affected versionversion=before 1.447
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo