WaratekVRT Sign in

Siemens CVEs

5 CVEs, 4 exploited, 4 protected by Waratek

Reset
More filters (1)
Columns
Vendor siemens✕
Overview 5 matches · 4 protected · 4 exploited · 4 CISA KEV · 4 public PoC · 4 EPSS ≥ 0.5
5matches 4protected80.0% 4exploited80.0% 4CISA KEV80.0% 4public PoC80.0% 4EPSS ≥ 0.580.0%
Protected by Waratek 4 80.0% Rule in development 0 0.0% Mitigation candidate 1 20.0% No exploit published 0 0.0%
Critical 3 60.0% High 1 20.0% Medium 1 20.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 4 80.0% partly blocked 0 0.0% not blocked 1 20.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 4 80.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 1 20.0%
split by peak 3 / quarter
Mitigation candidate: 1Protected by Waratek: 4 Medium: 1High: 1Critical: 3 not blocked: 1blocked by ARMR today: 4 No public exploit: 1Exploited: 4
Q4 213 Protected by Waratek3 Critical2 Medium1 blocked by ARMR today3 Exploited2 No public exploit1 Q1 220 Q2 221 Protected by Waratek1 Critical1 blocked by ARMR today1 Exploited1 Q3 220 Q4 220 Q1 230 Q2 230 Q3 230 Q4 231 Mitigation candidate1 High1 not blocked1 Exploited1
Q4 21Q1 22Q2 22Q3 22Q4 22Q1 23Q2 23Q3 23Q4 23
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-2023-44487 High 2023-10-10 Mitigation candidate Exploited The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
CVE-2022-22965 Critical 2022-04-01 Protected by Waratek Exploited A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding. The specific exploit requires the application to run on Tomcat as a WAR deployment. If the application is deployed as a Spring Boot executable jar, i.e. the default, it is not vulnerable to the exploit. However, the nature of the vulnerability is more general, and there may be other ways to exploit it.
CVE-2021-42550 Medium 2021-12-16 Protected by Waratek No public exploit In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers.
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.