WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Product log4j✕
Overview 6 matches · 4 in Waratek scope · 4 protected · 2 exploited · 0 CISA KEV · 1 public PoC · 3 EPSS ≥ 0.5
6matches 4in Waratek scope66.7% 4protected66.7% 2exploited33.3% 0CISA KEV0.0% 1public PoC16.7% 3EPSS ≥ 0.550.0%
Protected by Waratek 4 66.7% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 0 0.0% Outside Waratek scope 0 0.0% Not applicable 2 33.3% Withdrawn CVE 0 0.0%
Critical 0 0.0% High 6 100.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 4 66.7% partly blocked 0 0.0% not blocked 2 33.3% not established 0 0.0% unrecorded 0 0.0%
Exploited 2 33.3% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 2 33.3% No public exploit 2 33.3%
split by peak 2 / month
Not applicable: 2Protected by Waratek: 4 High: 6 not blocked: 2blocked by ARMR today: 4 No public exploit: 2Forecast only: 2Exploited: 2
Dec 211 Protected by Waratek1 High1 blocked by ARMR today1 Exploited1 Jan 222 Protected by Waratek2 High2 blocked by ARMR today2 Forecast only2 Feb 220 Mar 220 Apr 222 Not applicable2 High2 not blocked2 No public exploit2 May 220 Jun 220 Jul 220 Aug 220 Sep 220 Oct 220 Nov 220 Dec 220 Jan 230 Feb 230 Mar 231 Protected by Waratek1 High1 blocked by ARMR today1 Exploited1
Jan 22Mar 22May 22Jul 22Sep 22Nov 22Jan 23Mar 23
6 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-2023-26464 High 2023-03-10 Protected by Waratek Exploited ** UNSUPPORTED WHEN ASSIGNED ** When using the Chainsaw or SocketAppender components with Log4j 1.x on JRE less than 1.7, an attacker that manages to cause a logging entry involving a specially-crafted (ie, deeply nested) hashmap or hashtable (depending on which logging component is in use) to be processed could exhaust the available memory in the virtual machine and achieve Denial of Service when the object is deserialized. This issue affects Apache Log4j before 2. Affected users are recommended to update to Log4j 2.x. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
CVE-2022-0070 High 2022-04-19 Not applicable No public exploit Incomplete fix for CVE-2021-3100. The Apache Log4j hotpatch package starting with log4j-cve-2021-44228-hotpatch-1.1-16 will now explicitly mimic the Linux capabilities and cgroups of the target Java process that the hotpatch is applied to.
CVE-2021-3100 High 2022-04-19 Not applicable No public exploit The Apache Log4j hotpatch package before log4j-cve-2021-44228-hotpatch-1.1-13 didn’t mimic the permissions of the JVM being patched, allowing it to escalate privileges.
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-4104 High 2021-12-14 Protected by Waratek Exploited JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, 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.