WaratekVRT Sign in
Reset
More filters (1)
Columns
Product communications messaging server✕
Overview 6 matches · 1 exploited · 0 CISA KEV · 1 public PoC · 3 EPSS ≥ 0.5
6matches 1exploited16.7% 0CISA KEV0.0% 1public PoC16.7% 3EPSS ≥ 0.550.0%
Protected by Waratek 6 100.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 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 6 100.0% partly blocked 0 0.0% not blocked 0 0.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 1 16.7% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 2 33.3% No public exploit 3 50.0%
split by peak 2 / month
Protected by Waratek: 6 High: 6 blocked by ARMR today: 6 No public exploit: 3Forecast only: 2Exploited: 1
Sep 201 Protected by Waratek1 High1 blocked by ARMR today1 No public exploit1 Oct 200 Nov 200 Dec 201 Protected by Waratek1 High1 blocked by ARMR today1 No public exploit1 Jan 210 Feb 210 Mar 210 Apr 210 May 210 Jun 211 Protected by Waratek1 High1 blocked by ARMR today1 No public exploit1 Jul 210 Aug 210 Sep 210 Oct 210 Nov 210 Dec 211 Protected by Waratek1 High1 blocked by ARMR today1 Exploited1 Jan 222 Protected by Waratek2 High2 blocked by ARMR today2 Forecast only2
Sep 20Nov 20Jan 21Mar 21May 21Jul 21Sep 21Nov 21Jan 22
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-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.
CVE-2021-33813 High 2021-06-16 Protected by Waratek No public exploit An XXE issue in SAXBuilder in JDOM through 2.0.6 allows attackers to cause a denial of service via a crafted HTTP request.
CVE-2020-25649 High 2020-12-03 Protected by Waratek No public exploit A flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly. This flaw allows vulnerability to XML external entity (XXE) attacks. The highest threat from this vulnerability is data integrity.
CVE-2020-24750 High 2020-09-17 Protected by Waratek No public exploit FasterXML jackson-databind 2.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to com.pastdev.httpcomponents.configuration.JndiConfiguration.