WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Product spring-core✕
Overview 9 matches · 4 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 0 EPSS ≥ 0.5
9matches 4protected44.4% 0exploited0.0% 0CISA KEV0.0% 2public PoC22.2% 0EPSS ≥ 0.50.0%
Protected by Waratek 4 44.4% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 5 55.6% Outside Waratek scope 0 0.0% Not applicable 0 0.0% Withdrawn CVE 0 0.0%
Critical 0 0.0% High 0 0.0% Medium 9 100.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 4 44.4% partly blocked 0 0.0% not blocked 5 55.6% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 1 11.1% Proof of concept only 1 11.1% Forecast only 0 0.0% No public exploit 7 77.8%
split by peak 3 / year
No exploit published: 5Protected by Waratek: 4 Medium: 9 not blocked: 5blocked by ARMR today: 4 No public exploit: 7Proof of concept only: 1Working exploit published: 1
20091 No exploit published1 Medium1 not blocked1 No public exploit1 20100 20111 Protected by Waratek1 Medium1 blocked by ARMR today1 Proof of concept only1 20120 20130 20140 20152 Protected by Waratek2 Medium2 blocked by ARMR today2 No public exploit2 20160 20170 20183 Protected by Waratek1 No exploit published2 Medium3 blocked by ARMR today1 not blocked2 Working exploit published1 No public exploit2 20190 20200 20211 No exploit published1 Medium1 not blocked1 No public exploit1 20221 No exploit published1 Medium1 not blocked1 No public exploit1
2010201220142016201820202022
9 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-2021-22060 Medium 2022-01-10 No exploit published No public exploit In Spring Framework versions 5.3.0 - 5.3.13, 5.2.0 - 5.2.18, and older unsupported versions, it is possible for a user to provide malicious input to cause the insertion of additional log entries. This is a follow-up to CVE-2021-22096 that protects against additional types of input and in more places of the Spring Framework codebase.
CVE-2021-22096 Medium 2021-10-28 No exploit published No public exploit In Spring Framework versions 5.3.0 - 5.3.10, 5.2.0 - 5.2.17, and older unsupported versions, it is possible for a user to provide malicious input to cause the insertion of additional log entries.
CVE-2018-1257 Medium 2018-05-11 No exploit published No public exploit Spring Framework, versions 5.0.x prior to 5.0.6, versions 4.3.x prior to 4.3.17, and older unsupported versions allows 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 regular expression, denial of service attack.
CVE-2018-1271 Medium 2018-04-06 Protected by Waratek Working exploit published Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to configure Spring MVC to serve static resources (e.g. CSS, JS, images). When static resources are served from a file system on Windows (as opposed to the classpath, or the ServletContext), a malicious user can send a request using a specially crafted URL that can lead a directory traversal attack.
CVE-2018-1199 Medium 2018-03-16 No exploit published No public exploit Spring Security (Spring Security 4.1.x before 4.1.5, 4.2.x before 4.2.4, and 5.0.x before 5.0.1; and Spring Framework 4.3.x before 4.3.14 and 5.0.x before 5.0.3) does not consider URL path parameters when processing security constraints. By adding a URL path parameter with special encodings, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification. Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. In this particular attack, different character encodings used in path parameters allows secured Spring MVC static resource URLs to be bypassed.
CVE-2015-0201 Medium 2015-03-10 Protected by Waratek No public exploit The Java SockJS client in Pivotal Spring Framework 4.1.x before 4.1.5 generates predictable session ids, which allows remote attackers to send messages to other sessions via unspecified vectors.
CVE-2014-3578 Medium 2015-02-19 Protected by Waratek No public exploit Directory traversal vulnerability in Pivotal Spring Framework 3.x before 3.2.9 and 4.0 before 4.0.5 allows remote attackers to read arbitrary files via a crafted URL.
CVE-2011-2894 Medium 2011-10-04 Protected by Waratek Proof of concept only Spring Framework 3.0.0 through 3.0.5, Spring Security 3.0.0 through 3.0.5 and 2.0.0 through 2.0.6, and possibly other versions deserialize objects from untrusted sources, which allows remote attackers to bypass intended security restrictions and execute untrusted code by (1) serializing a java.lang.Proxy instance and using InvocationHandler, or (2) accessing internal AOP interfaces, as demonstrated using deserialization of a DefaultListableBeanFactory instance to execute arbitrary commands via the java.lang.Runtime class.
CVE-2009-1190 Medium 2009-04-27 No exploit published No public exploit Algorithmic complexity vulnerability in the java.util.regex.Pattern.compile method in Sun Java Development Kit (JDK) before 1.6, when used with spring.jar in SpringSource Spring Framework 1.1.0 through 2.5.6 and 3.0.0.M1 through 3.0.0.M2 and dm Server 1.0.0 through 1.0.2, allows remote attackers to cause a denial of service (CPU consumption) via serializable data with a long regex string containing multiple optional groups, a related issue to CVE-2004-2540.