Overview 105 matches · 43 protected · 7 exploited · 2 CISA KEV · 19 public PoC · 13 EPSS ≥ 0.5
Protected by Waratek
43
41.0%
Rule in development
0
0.0%
Mitigation candidate
7
6.7%
No exploit published
55
52.4%
blocked by ARMR today
43
41.0%
partly blocked
0
0.0%
not blocked
62
59.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 27 / year
20091
No exploit published1
Medium1
not blocked1
No public exploit1
20102
Protected by Waratek1
No exploit published1
Medium2
blocked by ARMR today1
not blocked1
Working exploit published1
No public exploit1
20111
Protected by Waratek1
Medium1
blocked by ARMR today1
Proof of concept only1
20124
Mitigation candidate1
No exploit published3
High1
Medium3
not blocked4
Working exploit published1
No public exploit3
20130
20146
Protected by Waratek5
No exploit published1
Medium6
blocked by ARMR today5
not blocked1
Proof of concept only1
Forecast only2
No public exploit3
20152
Protected by Waratek2
Medium2
blocked by ARMR today2
No public exploit2
20164
Protected by Waratek3
No exploit published1
Critical1
High1
Medium2
blocked by ARMR today3
not blocked1
No public exploit4
201718
Protected by Waratek3
Mitigation candidate1
No exploit published14
Critical4
High11
Medium3
blocked by ARMR today3
not blocked15
Exploited1
No public exploit17
201827
Protected by Waratek12
No exploit published15
Critical6
High12
Medium9
blocked by ARMR today12
not blocked15
Exploited2
Working exploit published1
Proof of concept only1
Forecast only1
No public exploit22
201911
Protected by Waratek5
Mitigation candidate2
No exploit published4
Critical4
High1
Medium6
blocked by ARMR today5
not blocked6
Working exploit published3
No public exploit8
202013
Protected by Waratek4
Mitigation candidate2
No exploit published7
Critical3
High4
Medium6
blocked by ARMR today4
not blocked9
Exploited2
Working exploit published1
Proof of concept only2
No public exploit8
202116
Protected by Waratek7
Mitigation candidate1
No exploit published8
Critical3
High6
Medium7
blocked by ARMR today7
not blocked9
Exploited2
No public exploit14
2009201120132015201720192021
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2011-2730 | High | 2012-12-05 | No exploit published | No public exploit | VMware SpringSource Spring Framework before 2.5.6.SEC03, 2.5.7.SR023, and 3.x before 3.0.6, when a container supports Expression Language (EL), evaluates EL expressions in tags twice, which allows remote attackers to obtain sensitive information via a (1) name attribute in a (a) spring:hasBindErrors tag; (2) path attribute in a (b) spring:bind or (c) spring:nestedpath tag; (3) arguments, (4) code, (5) text, (6) var, (7) scope, or (8) message attribute in a (d) spring:message or (e) spring:theme tag; or (9) var, (10) scope, or (11) value attribute in a (f) spring:transform tag, aka "Expression Language Injection." |
| 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-2010-3700 | Medium | 2010-10-29 | No exploit published | No public exploit | VMware SpringSource Spring Security 2.x before 2.0.6 and 3.x before 3.0.4, and Acegi Security 1.0.0 through 1.0.7, as used in IBM WebSphere Application Server (WAS) 6.1 and 7.0, allows remote attackers to bypass security constraints via a path parameter. |
| CVE-2010-1622 | Medium | 2010-06-21 | Protected by Waratek | Working exploit published | SpringSource Spring Framework 2.5.x before 2.5.6.SEC02, 2.5.7 before 2.5.7.SR01, and 3.0.x before 3.0.3 allows remote attackers to execute arbitrary code via an HTTP request containing class.classLoader.URLs[0]=jar: followed by a URL of a crafted .jar file. |
| 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. |