WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Product cloud manager✕
Overview 4 matches · 3 in Waratek scope · 2 protected · 0 exploited · 0 CISA KEV · 0 public PoC
4matches 3in Waratek scope75.0% 2protected50.0% 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0%
Protected by Waratek 2 50.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 1 25.0% Outside Waratek scope 1 25.0% Not applicable 0 0.0% Withdrawn CVE 0 0.0%
Critical 0 0.0% High 3 75.0% Medium 1 25.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 2 50.0% partly blocked 0 0.0% not blocked 2 50.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 4 100.0% No public exploit 0 0.0%
split by peak 2 / month
Outside Waratek scope: 1No exploit published: 1Protected by Waratek: 2 Medium: 1High: 3 not blocked: 2blocked by ARMR today: 2 Forecast only: 4
Apr 211 No exploit published1 High1 not blocked1 Forecast only1 May 211 Outside Waratek scope1 Medium1 not blocked1 Forecast only1 Jun 210 Jul 210 Aug 210 Sep 210 Oct 210 Nov 210 Dec 210 Jan 222 Protected by Waratek2 High2 blocked by ARMR today2 Forecast only2
Apr 21May 21Jun 21Jul 21Aug 21Sep 21Oct 21Nov 21Dec 21Jan 22
4 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2022-23307 High 2022-01-18 Protected by Waratek Forecast only CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.
CVE-2022-23302 High 2022-01-18 Protected by Waratek Forecast only JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
CVE-2021-31806 Medium 2021-05-27 Outside Waratek scope Forecast only An issue was discovered in Squid before 4.15 and 5.x before 5.0.6. Due to a memory-management bug, it is vulnerable to a Denial of Service attack (against all clients using the proxy) via HTTP Range request processing.
CVE-2021-28165 High 2021-04-01 No exploit published Forecast only In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame.