Overview 3 matches · 1 protected · 1 exploited · 1 CISA KEV · 2 public PoC
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
1
33.3%
Working exploit published
1
33.3%
Proof of concept only
0
0.0%
Forecast only
1
33.3%
No public exploit
0
0.0%
split by
peak 2 / month
Jul 202
Mitigation candidate1
No exploit published1
High2
not blocked2
Working exploit published1
Forecast only1
Aug 200
Sep 200
Oct 200
Nov 200
Dec 200
Jan 210
Feb 210
Mar 210
Apr 210
May 210
Jun 210
Jul 210
Aug 210
Sep 210
Oct 210
Nov 210
Dec 211
Protected by Waratek1
Critical1
blocked by ARMR today1
Exploited1
Aug 20Oct 20Dec 20Feb 21Apr 21Jun 21Aug 21Oct 21Dec 21
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2021-44228 | Critical | 2021-12-10 | Protected by Waratek | Exploited | Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects. |
| 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. |