WaratekVRT Sign in

High Qos CVEs

4 CVEs, 3 protected by Waratek

Reset
More filters (1)
Columns
Vendor qos✕
Overview 4 matches · 3 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 2 EPSS ≥ 0.5
4matches 3protected75.0% 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0% 2EPSS ≥ 0.550.0%
Protected by Waratek 3 75.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 1 25.0%
Critical 0 0.0% High 4 100.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 3 75.0% partly blocked 0 0.0% not blocked 1 25.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 2 50.0% No public exploit 2 50.0%
split by peak 2 / quarter
No exploit published: 1Protected by Waratek: 3 High: 4 not blocked: 1blocked by ARMR today: 3 No public exploit: 2Forecast only: 2
Q1 222 Protected by Waratek2 High2 blocked by ARMR today2 Forecast only2 Q2 220 Q3 220 Q4 220 Q1 230 Q2 230 Q3 230 Q4 232 Protected by Waratek1 No exploit published1 High2 blocked by ARMR today1 not blocked1 No public exploit2
Q1 22Q2 22Q3 22Q4 22Q1 23Q2 23Q3 23Q4 23
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-2023-6481 High 2023-12-04 No exploit published No public exploit A serialization vulnerability in logback receiver component part of logback version 1.4.13, 1.3.13 and 1.2.12 allows an attacker to mount a Denial-Of-Service attack by sending poisoned data.
CVE-2023-6378 High 2023-11-29 Protected by Waratek No public exploit A serialization vulnerability in logback receiver component part of logback version 1.4.11 allows an attacker to mount a Denial-Of-Service attack by sending poisoned data.
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.