High Geronimo CVEs
3 CVEs, 1 protected by Waratek
Overview 3 matches · 1 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 1 EPSS ≥ 0.5
Protected by Waratek
1
33.3%
Rule in development
0
0.0%
Mitigation candidate
1
33.3%
No exploit published
1
33.3%
blocked by ARMR today
1
33.3%
partly blocked
0
0.0%
not blocked
2
66.7%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
2
66.7%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
1
33.3%
split by
peak 1 / quarter
Q2 091
Protected by Waratek1
High1
blocked by ARMR today1
Working exploit published1
Q3 090
Q4 090
Q1 100
Q2 100
Q3 100
Q4 100
Q1 110
Q2 110
Q3 110
Q4 111
Mitigation candidate1
High1
not blocked1
Working exploit published1
Q1 120
Q2 120
Q3 120
Q4 120
Q1 130
Q2 130
Q3 131
No exploit published1
High1
not blocked1
No public exploit1
Q3 09Q1 10Q3 10Q1 11Q3 11Q1 12Q3 12Q1 13Q3 13
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2013-1777 | High | 2013-07-11 | No exploit published | No public exploit | The JMX Remoting functionality in Apache Geronimo 3.x before 3.0.1, as used in IBM WebSphere Application Server (WAS) Community Edition 3.0.0.3 and other products, does not properly implement the RMI classloader, which allows remote attackers to execute arbitrary code by using the JMX connector to send a crafted serialized object. |
| CVE-2011-5034 | High | 2011-12-30 | Mitigation candidate | Working exploit published | 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. |
| CVE-2008-5518 | High | 2009-04-17 | Protected by Waratek | Working exploit published | Multiple directory traversal vulnerabilities in the web administration console in Apache Geronimo Application Server 2.1 through 2.1.3 on Windows allow remote attackers to upload files to arbitrary directories via directory traversal sequences in the (1) group, (2) artifact, (3) version, or (4) fileType parameter to console/portal//Services/Repository (aka the Services/Repository portlet); the (5) createDB parameter to console/portal/Embedded DB/DB Manager (aka the Embedded DB/DB Manager portlet); or the (6) filename parameter to the createKeystore script in the Security/Keystores portlet. |