ghsa-fmmq-j7pq-f85c
Vulnerability from github
Published
2022-05-17 04:17
Modified
2023-08-29 20:33
Summary
JRuby denial of service via Hash Collision
Details
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": [ { "package": { "ecosystem": "Maven", "name": "org.jruby:jruby-parent" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "1.7.1" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2012-5370" ], "database_specific": { "cwe_ids": [ "CWE-400" ], "github_reviewed": true, "github_reviewed_at": "2023-08-29T20:33:46Z", "nvd_published_at": "2012-11-28T13:03:00Z", "severity": "MODERATE" }, "details": "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.", "id": "GHSA-fmmq-j7pq-f85c", "modified": "2023-08-29T20:33:46Z", "published": "2022-05-17T04:17:07Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2012-5370" }, { "type": "WEB", "url": "https://github.com/jruby/jruby/commit/5e4aab28b26fd127112b76fabfac9a33b64caf77" }, { "type": "WEB", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=880671" }, { "type": "WEB", "url": "http://jruby.org/2012/12/03/jruby-1-7-1" }, { "type": "WEB", "url": "http://rhn.redhat.com/errata/RHSA-2013-0533.html" } ], "schema_version": "1.4.0", "severity": [], "summary": "JRuby denial of service via Hash Collision" }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.