Overview 5 matches · 4 in Waratek scope · 1 protected · 3 exploited · 1 CISA KEV · 4 public PoC
Protected by Waratek
1
20.0%
Rule in development
0
0.0%
Mitigation candidate
2
40.0%
No exploit published
1
20.0%
Outside Waratek scope
0
0.0%
Not applicable
1
20.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
1
20.0%
partly blocked
0
0.0%
not blocked
4
80.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
3
60.0%
Working exploit published
1
20.0%
Proof of concept only
0
0.0%
Forecast only
1
20.0%
No public exploit
0
0.0%
split by
peak 2 / year
20071
Not applicable1
High1
not blocked1
Working exploit published1
20080
20090
20100
20110
20120
20130
20140
20150
20160
20170
20180
20191
Mitigation candidate1
Medium1
not blocked1
Exploited1
20201
Mitigation candidate1
Medium1
not blocked1
Exploited1
20212
Protected by Waratek1
No exploit published1
Medium2
blocked by ARMR today1
not blocked1
Exploited1
Forecast only1
20072009201120132015201720192021
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2021-45105 | Medium | 2021-12-18 | Protected by Waratek | Exploited | Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1. |
| CVE-2021-33037 | Medium | 2021-07-12 | No exploit published | Forecast only | Apache Tomcat 10.0.0-M1 to 10.0.6, 9.0.0.M1 to 9.0.46 and 8.5.0 to 8.5.66 did not correctly parse the HTTP transfer-encoding request header in some circumstances leading to the possibility to request smuggling when used with a reverse proxy. Specifically: - Tomcat incorrectly ignored the transfer encoding header if the client declared it would only accept an HTTP/1.0 response; - Tomcat honoured the identify encoding; and - Tomcat did not ensure that, if present, the chunked encoding was the final encoding. |
| CVE-2020-11023 | Medium | 2020-04-29 | Mitigation candidate | Exploited | In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
| CVE-2019-11358 | Medium | 2019-04-20 | Mitigation candidate | Exploited | jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype. |
| CVE-2007-2676 | High | 2007-05-14 | Not applicable | Working exploit published | PHP remote file inclusion vulnerability in skins/header.php in Open Translation Engine (OTE) 0.7.8 allows remote attackers to execute arbitrary PHP code via a URL in the ote_home parameter. |