WaratekVRT Sign in
Reset
More filters (2)
Columns
Including CVEs outside Waratek scope✕EPSS ≥ 0.5✕Product communications cloud native core network function cloud native environment✕
Overview 7 matches · 4 in Waratek scope · 3 protected · 4 exploited · 3 CISA KEV · 4 public PoC
7matches 4in Waratek scope57.1% 3protected42.9% 4exploited57.1% 3CISA KEV42.9% 4public PoC57.1%
Protected by Waratek 3 42.9% Rule in development 0 0.0% Mitigation candidate 1 14.3% No exploit published 0 0.0% Outside Waratek scope 3 42.9% Not applicable 0 0.0% Withdrawn CVE 0 0.0%
Critical 3 42.9% High 3 42.9% Medium 1 14.3% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 3 42.9% partly blocked 0 0.0% not blocked 4 57.1% not established 0 0.0% unrecorded 0 0.0%
Exploited 4 57.1% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 3 42.9% No public exploit 0 0.0%
split by peak 2 / month
Outside Waratek scope: 3Mitigation candidate: 1Protected by Waratek: 3 Medium: 1High: 3Critical: 3 not blocked: 4blocked by ARMR today: 3 Forecast only: 3Exploited: 4
Jun 211 Outside Waratek scope1 High1 not blocked1 Forecast only1 Jul 210 Aug 210 Sep 212 Outside Waratek scope2 High2 not blocked2 Forecast only2 Oct 210 Nov 210 Dec 211 Protected by Waratek1 Medium1 blocked by ARMR today1 Exploited1 Jan 220 Feb 220 Mar 221 Mitigation candidate1 Critical1 not blocked1 Exploited1 Apr 222 Protected by Waratek2 Critical2 blocked by ARMR today2 Exploited2
Jun 21Jul 21Aug 21Sep 21Oct 21Nov 21Dec 21Jan 22Feb 22Mar 22Apr 22
7 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-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-2022-22963 Critical 2022-04-01 Protected by Waratek Exploited In Spring Cloud Function versions 3.1.6, 3.2.2 and older unsupported versions, when using routing functionality it is possible for a user to provide a specially crafted SpEL as a routing-expression that may result in remote code execution and access to local resources.
CVE-2022-22947 Critical 2022-03-03 Mitigation candidate Exploited In spring cloud gateway versions prior to 3.1.1+ and 3.0.7+ , applications are vulnerable to a code injection attack when the Gateway Actuator endpoint is enabled, exposed and unsecured. A remote attacker could make a maliciously crafted request that could allow arbitrary remote execution on the remote host.
CVE-2021-45105 Medium 2021-12-18 Protected by Waratek Exploited Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.
CVE-2021-36160 High 2021-09-16 Outside Waratek scope Forecast only A carefully crafted request uri-path can cause mod_proxy_uwsgi to read above the allocated memory and crash (DoS). This issue affects Apache HTTP Server versions 2.4.30 to 2.4.48 (inclusive).
CVE-2021-34798 High 2021-09-16 Outside Waratek scope Forecast only Malformed requests may cause the server to dereference a NULL pointer. This issue affects Apache HTTP Server 2.4.48 and earlier.
CVE-2021-22901 High 2021-06-11 Outside Waratek scope Forecast only curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session ticket arrives over a connection. A malicious server can use this in rare unfortunate circumstances to potentially reach remote code execution in the client. When libcurl at run-time sets up support for TLS 1.3 session tickets on a connection using OpenSSL, it stores pointers to the transfer in-memory object for later retrieval when a session ticket arrives. If the connection is used by multiple transfers (like with a reused HTTP/1.1 connection or multiplexed HTTP/2 connection) that first transfer object might be freed before the new session is established on that connection and then the function will access a memory buffer that might be freed. When using that memory, libcurl might even call a function pointer in the object, making it possible for a remote code execution if the server could somehow manage to get crafted memory content into the correct place in memory.