How severe is CVE-2011-5034?

No CVSS score has been assigned to CVE-2011-5034 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2011-5034?

CVE-2011-5034 affects the following packages: org.apache.geronimo:geronimo (Maven). Ecosystems affected: Maven.

How do I fix CVE-2011-5034?

Update org.apache.geronimo:geronimo to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-5034 is resolved across your whole dependency graph.

How do I detect CVE-2011-5034 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.geronimo:geronimo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2011-5034 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2011-5034 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2011-5034, including 1 documented proof-of-concept exploit on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2011-5034?

CVE-2011-5034 has an EPSS (Exploit Prediction Scoring System) score of 80.6%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2011-5034?

CVE-2011-5034 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2011-5034 published, and has it been updated?

CVE-2011-5034 was published on May 13, 2022 and was last updated on December 7, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2011-5034 — geronimo

CVE-2011-5034 is a Improper Input Validation vulnerability in org.apache.geronimo:geronimo. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.geronimo:geronimo — see the affected versions and patch details below.

Apache Geronimo Hash Collisions Cause DoS

Published

May 13, 2022

Updated

Dec 7, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

80.6%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.apache.geronimo:geronimo

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Apache Geronimo 2.2.1 and earlier computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters. NOTE: this might overlap CVE-2011-4461.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.geronimo:geronimo`	all versions	2.2.1`org.apache.geronimo:geronimo:2.2.1`

Affected Products

1 product · 17 configurations

Application

geronimoapache

≤ 2.2.1

16 versions

1.01.11.1.11.22.0.12.0.22.12.1.12.1.22.1.32.1.42.1.5

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-2012webappsphp✓ Verified

MyBulletinBoard (MyBB) 1.1.5 - 'CLIENT-IP' SQL Injection

by rgod · Jul 15, 2006

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.geronimo:geronimo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.geronimo:geronimo to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-5034 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2011-5034 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works