Overview 104 matches · 15 protected · 6 exploited · 4 CISA KEV · 19 public PoC · 14 EPSS ≥ 0.5
Protected by Waratek
15
14.4%
Rule in development
0
0.0%
Mitigation candidate
10
9.6%
No exploit published
79
76.0%
blocked by ARMR today
15
14.4%
partly blocked
0
0.0%
not blocked
89
85.6%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 40 / year
20194
Protected by Waratek1
Mitigation candidate1
No exploit published2
High3
Medium1
blocked by ARMR today1
not blocked3
Working exploit published1
Forecast only1
No public exploit2
202010
Protected by Waratek2
Mitigation candidate2
No exploit published6
Critical1
High6
Medium3
blocked by ARMR today2
not blocked8
Exploited1
Working exploit published2
Proof of concept only1
Forecast only2
No public exploit4
20218
Protected by Waratek3
No exploit published5
High5
Medium3
blocked by ARMR today3
not blocked5
Forecast only1
No public exploit7
20226
Protected by Waratek2
Mitigation candidate1
No exploit published3
High4
Medium1
Low1
blocked by ARMR today2
not blocked4
Exploited1
Working exploit published1
No public exploit4
202311
Mitigation candidate3
No exploit published8
High6
Medium5
not blocked11
Exploited1
Working exploit published1
Proof of concept only1
No public exploit8
202411
Protected by Waratek1
Mitigation candidate3
No exploit published7
Critical3
High3
Medium5
blocked by ARMR today1
not blocked10
Exploited1
Proof of concept only3
No public exploit7
202514
Protected by Waratek4
No exploit published10
Critical2
High10
Medium2
blocked by ARMR today4
not blocked10
Exploited1
Working exploit published1
Proof of concept only1
No public exploit11
202640
Protected by Waratek2
No exploit published38
Critical13
High18
Medium8
Low1
blocked by ARMR today2
not blocked38
Exploited1
Working exploit published1
No public exploit38
20192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2019-17563 | High | 2019-12-23 | Protected by Waratek | No public exploit | When using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where an attacker could perform a session fixation attack. The window was considered too narrow for an exploit to be practical but, erring on the side of caution, this issue has been treated as a security vulnerability. |
| CVE-2019-12418 | High | 2019-12-23 | No exploit published | No public exploit | When Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance. |
| CVE-2019-10072 | High | 2019-06-21 | No exploit published | Forecast only | The fix for CVE-2019-0199 was incomplete and did not address HTTP/2 connection window exhaustion on write in Apache Tomcat versions 9.0.0.M1 to 9.0.19 and 8.5.0 to 8.5.40 . By not sending WINDOW_UPDATE messages for the connection window (stream 0) clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS. |
| CVE-2019-0221 | Medium | 2019-05-28 | Mitigation candidate | Working exploit published | The SSI printenv command in Apache Tomcat 9.0.0.M1 to 9.0.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 echoes user provided data without escaping and is, therefore, vulnerable to XSS. SSI is disabled by default. The printenv command is intended for debugging and is unlikely to be present in a production website. |