Overview 205 matches · 87 protected · 81 exploited · 42 CISA KEV · 121 public PoC
Protected by Waratek
89
43.4%
Rule in development
2
1.0%
Mitigation candidate
46
22.4%
No exploit published
68
33.2%
blocked by ARMR today
87
42.4%
partly blocked
2
1.0%
not blocked
116
56.6%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
81
39.5%
Working exploit published
33
16.1%
Proof of concept only
24
11.7%
Forecast only
67
32.7%
No public exploit
0
0.0%
split by
peak 51 / year
202028
Protected by Waratek14
Mitigation candidate8
No exploit published6
Critical9
High13
Medium6
blocked by ARMR today14
not blocked14
Exploited13
Working exploit published8
Proof of concept only1
Forecast only6
202151
Protected by Waratek18
Rule in development1
Mitigation candidate9
No exploit published23
Critical19
High13
Medium19
blocked by ARMR today18
not blocked33
Exploited16
Working exploit published7
Proof of concept only3
Forecast only25
202243
Protected by Waratek23
Mitigation candidate4
No exploit published16
Critical22
High11
Medium10
blocked by ARMR today23
not blocked20
Exploited14
Working exploit published4
Proof of concept only9
Forecast only16
202339
Protected by Waratek11
Mitigation candidate12
No exploit published16
Critical21
High14
Medium4
blocked by ARMR today11
not blocked28
Exploited12
Working exploit published7
Proof of concept only8
Forecast only12
202422
Protected by Waratek10
Mitigation candidate5
No exploit published7
Critical13
High6
Medium3
blocked by ARMR today8
partly blocked2
not blocked12
Exploited9
Working exploit published4
Proof of concept only2
Forecast only7
202516
Protected by Waratek8
Rule in development1
Mitigation candidate7
Critical10
High4
Medium2
blocked by ARMR today8
not blocked8
Exploited11
Working exploit published3
Proof of concept only1
Forecast only1
20266
Protected by Waratek5
Mitigation candidate1
Critical2
High4
blocked by ARMR today5
not blocked1
Exploited6
2020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2020-13935 | High | 2020-07-14 | Mitigation candidate | Working exploit published | The payload length in a WebSocket frame was not correctly validated in Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to 9.0.36, 8.5.0 to 8.5.56 and 7.0.27 to 7.0.104. Invalid payload lengths could trigger an infinite loop. Multiple requests with invalid payload lengths could lead to a denial of service. |
| CVE-2020-13934 | High | 2020-07-14 | No exploit published | Forecast only | An h2c direct connection to Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M5 to 9.0.36 and 8.5.1 to 8.5.56 did not release the HTTP/1.1 processor after the upgrade to HTTP/2. If a sufficient number of such requests were made, an OutOfMemoryException could occur leading to a denial of service. |
| CVE-2020-5410 | High | 2020-06-02 | Protected by Waratek | Exploited | Spring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior to 2.1.9, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead to a directory traversal attack. |
| CVE-2020-1956 | High | 2020-05-22 | Protected by Waratek | Exploited | Apache Kylin 2.3.0, and releases up to 2.6.5 and 3.0.1 has some restful apis which will concatenate os command with the user input string, a user is likely to be able to execute any os command without any protection or validation. |
| CVE-2020-9484 | High | 2020-05-20 | Protected by Waratek | Working exploit published | When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server is configured to use the PersistenceManager with a FileStore; and c) the PersistenceManager is configured with sessionAttributeValueClassNameFilter="null" (the default unless a SecurityManager is used) or a sufficiently lax filter to allow the attacker provided object to be deserialized; and d) the attacker knows the relative file path from the storage location used by FileStore to the file the attacker has control over; then, using a specifically crafted request, the attacker will be able to trigger remote code execution via deserialization of the file under their control. Note that all of conditions a) to d) must be true for the attack to succeed. |