Apache Geronimo 2.2.1 and earlier are vulnerable to a denial-of-service attack due to predictable hash collisions in the computation of hash values for form parameters. An attacker can send a large number of specially crafted HTTP POST parameters that result in hash collisions, causing excessive CPU consumption during parameter parsing. This vulnerability is a variant of the algorithmic complexity attack described in 2003 and affects multiple web application platforms.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit auxiliary module: 'modules/auxiliary/dos/http/hashcollision_dos.rb'. The module implements a denial-of-service (DoS) attack that targets web servers written in PHP or Java by exploiting hash table collision vulnerabilities (CVE-2011-5034, CVE-2011-5035, CVE-2011-4885, CVE-2011-4858). The exploit generates a large HTTP POST request with many parameters whose names are crafted to produce identical hash values, causing the server's hash table implementation to consume excessive CPU resources while parsing the request. This can render the web service unresponsive. The module allows the user to select the target type (PHP or Java), customize the request URI, and adjust payload parameters. The code is written in Ruby and is designed to be run within the Metasploit Framework. No hardcoded IP addresses or domains are present; the attack is directed at a user-specified HTTP endpoint (default '/'). The repository is operational and provides a working DoS exploit for the described vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.