WaratekVRT Sign in

Critical Studio CVEs

10 CVEs, 3 exploited, 8 protected by Waratek

Reset
More filters (1)
Columns
Product studio✕
Overview 10 matches · 8 protected · 3 exploited · 3 CISA KEV · 7 public PoC · 8 EPSS ≥ 0.5
10matches 8protected80.0% 3exploited30.0% 3CISA KEV30.0% 7public PoC70.0% 8EPSS ≥ 0.580.0%
Protected by Waratek 8 80.0% Rule in development 0 0.0% Mitigation candidate 1 10.0% No exploit published 1 10.0%
Critical 10 100.0% High 0 0.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 8 80.0% partly blocked 0 0.0% not blocked 2 20.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 3 30.0% Working exploit published 2 20.0% Proof of concept only 2 20.0% Forecast only 2 20.0% No public exploit 1 10.0%
split by peak 2 / quarter
No exploit published: 1Mitigation candidate: 1Protected by Waratek: 8 Critical: 10 not blocked: 2blocked by ARMR today: 8 No public exploit: 1Forecast only: 2Proof of concept only: 2Working exploit published: 2Exploited: 3
Q2 171 Protected by Waratek1 Critical1 blocked by ARMR today1 Working exploit published1 Q3 170 Q4 170 Q1 180 Q2 181 Protected by Waratek1 Critical1 blocked by ARMR today1 Exploited1 Q3 180 Q4 180 Q1 190 Q2 191 Protected by Waratek1 Critical1 blocked by ARMR today1 Working exploit published1 Q3 191 Protected by Waratek1 Critical1 blocked by ARMR today1 Forecast only1 Q4 191 Protected by Waratek1 Critical1 blocked by ARMR today1 Proof of concept only1 Q1 200 Q2 200 Q3 200 Q4 201 Protected by Waratek1 Critical1 blocked by ARMR today1 No public exploit1 Q1 210 Q2 210 Q3 211 No exploit published1 Critical1 not blocked1 Forecast only1 Q4 212 Protected by Waratek2 Critical2 blocked by ARMR today2 Exploited2 Q1 220 Q2 221 Mitigation candidate1 Critical1 not blocked1 Proof of concept only1
Q2 17Q4 17Q2 18Q4 18Q2 19Q4 19Q2 20Q4 20Q2 21Q4 21Q2 22
10 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-22978 Critical 2022-05-19 Mitigation candidate Proof of concept only In spring security versions prior to 5.4.11+, 5.5.7+ , 5.6.4+ and older unsupported versions, RegexRequestMatcher can easily be misconfigured to be bypassed on some servlet containers. Applications using RegexRequestMatcher with `.` in the regular expression are possibly vulnerable to an authorization bypass.
CVE-2021-45046 Critical 2021-12-14 Protected by Waratek Exploited It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.
CVE-2021-44228 Critical 2021-12-10 Protected by Waratek Exploited Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
CVE-2021-41303 Critical 2021-09-17 No exploit published Forecast only Apache Shiro before 1.8.0, when using Apache Shiro with Spring Boot, a specially crafted HTTP request may cause an authentication bypass. Users should update to Apache Shiro 1.8.0.
CVE-2017-15681 Critical 2020-11-27 Protected by Waratek No public exploit In Crafter CMS Crafter Studio 3.0.1 a directory traversal vulnerability exists which allows unauthenticated attackers to overwrite files from the operating system which can lead to RCE.
CVE-2019-17571 Critical 2019-12-20 Protected by Waratek Proof of concept only Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
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-2013-7285 Critical 2019-05-15 Protected by Waratek Working exploit published Xstream API versions up to 1.4.6 and version 1.4.10, if the security framework has not been initialized, may allow a remote attacker to run arbitrary shell commands by manipulating the processed input stream when unmarshaling XML or any supported format. e.g. JSON.
CVE-2018-1273 Critical 2018-04-11 Protected by Waratek Exploited Spring Data Commons, versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property binder vulnerability caused by improper neutralization of special elements. An unauthenticated remote malicious user (or attacker) can supply specially crafted request parameters against Spring Data REST backed HTTP resources or using Spring Data's projection-based request payload binding hat can lead to a remote code execution attack.
CVE-2017-5645 Critical 2017-04-17 Protected by Waratek Working exploit published In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.