WaratekVRT Sign in
Reset
More filters (1)
Columns
Product platform✕
Overview 5 matches · 0 exploited · 0 CISA KEV · 0 public PoC
5matches 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0%
Protected by Waratek 5 100.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 0 0.0%
Critical 3 60.0% High 2 40.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 5 100.0% partly blocked 0 0.0% not blocked 0 0.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 5 100.0% No public exploit 0 0.0%
split by peak 2 / quarter
Protected by Waratek: 5 High: 2Critical: 3 blocked by ARMR today: 5 Forecast only: 5
Q2 181 Protected by Waratek1 Critical1 blocked by ARMR today1 Forecast only1 Q3 180 Q4 180 Q1 190 Q2 190 Q3 191 Protected by Waratek1 Critical1 blocked by ARMR today1 Forecast only1 Q4 190 Q1 200 Q2 200 Q3 200 Q4 200 Q1 211 Protected by Waratek1 Critical1 blocked by ARMR today1 Forecast only1 Q2 210 Q3 210 Q4 210 Q1 222 Protected by Waratek2 High2 blocked by ARMR today2 Forecast only2
Q3 18Q1 19Q3 19Q1 20Q3 20Q1 21Q3 21Q1 22
5 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-21344 Critical 2021-03-23 Protected by Waratek Forecast only XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
CVE-2019-10173 Critical 2019-07-23 Protected by Waratek Forecast only It was found that xstream API version 1.4.10 before 1.4.11 introduced a regression for a previous deserialization flaw. If the security framework has not been initialized, it may allow a remote attacker to run arbitrary shell commands when unmarshalling XML or any supported format. e.g. JSON. (regression of CVE-2013-7285)
CVE-2018-1275 Critical 2018-04-11 Protected by Waratek Forecast only Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.16 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack. This CVE addresses the partial fix for CVE-2018-1270 in the 4.3.x branch of the Spring Framework.