Overview 212 matches · 34 protected · 14 exploited · 8 CISA KEV · 28 public PoC · 15 EPSS ≥ 0.5
Protected by Waratek
34
16.0%
Rule in development
0
0.0%
Mitigation candidate
17
8.0%
No exploit published
161
75.9%
blocked by ARMR today
34
16.0%
partly blocked
0
0.0%
not blocked
178
84.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 29 / year
20051
Mitigation candidate1
High1
not blocked1
Working exploit published1
20060
20070
20080
20090
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
20123
Mitigation candidate1
No exploit published2
Medium3
not blocked3
Working exploit published1
No public exploit2
20133
Protected by Waratek2
No exploit published1
Medium2
Low1
blocked by ARMR today2
not blocked1
No public exploit3
20143
No exploit published3
Medium3
not blocked3
No public exploit3
20152
No exploit published2
Medium2
not blocked2
No public exploit2
20162
No exploit published2
High2
not blocked2
No public exploit2
201712
Protected by Waratek1
Mitigation candidate1
No exploit published10
Critical1
High8
Medium2
Low1
blocked by ARMR today1
not blocked11
Exploited1
No public exploit11
201813
Protected by Waratek1
No exploit published12
Critical3
High6
Medium4
blocked by ARMR today1
not blocked12
No public exploit13
201928
Protected by Waratek4
Mitigation candidate6
No exploit published18
Critical4
High11
Medium12
Low1
blocked by ARMR today4
not blocked24
Exploited3
Working exploit published3
Proof of concept only1
No public exploit21
202014
Mitigation candidate1
No exploit published13
Critical1
High7
Medium5
Low1
not blocked14
Exploited1
No public exploit13
202117
Protected by Waratek8
Mitigation candidate2
No exploit published7
Critical3
High7
Medium7
blocked by ARMR today8
not blocked9
Exploited4
Proof of concept only2
No public exploit11
202229
Protected by Waratek4
Mitigation candidate3
No exploit published22
Critical12
High9
Medium8
blocked by ARMR today4
not blocked25
Exploited4
Proof of concept only5
No public exploit20
202329
Protected by Waratek9
Mitigation candidate2
No exploit published18
Critical3
High5
Medium14
Low7
blocked by ARMR today9
not blocked20
Exploited1
Working exploit published1
Proof of concept only2
No public exploit25
202421
Protected by Waratek3
No exploit published18
Critical2
High6
Medium7
Low6
blocked by ARMR today3
not blocked18
No public exploit21
202520
No exploit published20
Critical3
High7
Medium10
not blocked20
Proof of concept only3
No public exploit17
202612
No exploit published12
Critical3
High4
Medium4
Low1
not blocked12
No public exploit12
20062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2014-0034 | Medium | 2014-07-07 | No exploit published | No public exploit | The SecurityTokenService (STS) in Apache CXF before 2.6.12 and 2.7.x before 2.7.9 does not properly validate SAML tokens when caching is enabled, which allows remote attackers to gain access via an invalid SAML token. |
| CVE-2013-4517 | Medium | 2014-01-11 | No exploit published | No public exploit | Apache Santuario XML Security for Java before 1.5.6, when applying Transforms, allows remote attackers to cause a denial of service (memory consumption) via crafted Document Type Definitions (DTDs), related to signatures. |
| CVE-2013-5960 | Medium | 2013-09-30 | No exploit published | No public exploit | The authenticated-encryption feature in the symmetric-encryption implementation in the OWASP Enterprise Security API (ESAPI) for Java 2.x before 2.1.0.1 does not properly resist tampering with serialized ciphertext, which makes it easier for remote attackers to bypass intended cryptographic protection mechanisms via an attack against the intended cipher mode in a non-default configuration, a different vulnerability than CVE-2013-5679. |
| CVE-2013-5679 | Low | 2013-09-30 | Protected by Waratek | No public exploit | The authenticated-encryption feature in the symmetric-encryption implementation in the OWASP Enterprise Security API (ESAPI) for Java 2.x before 2.1.0 does not properly resist tampering with serialized ciphertext, which makes it easier for remote attackers to bypass intended cryptographic protection mechanisms via an attack against authenticity in the default configuration, involving a null MAC and a zero MAC length. |
| CVE-2013-2172 | Medium | 2013-08-20 | Protected by Waratek | No public exploit | jcp/xml/dsig/internal/dom/DOMCanonicalizationMethod.java in Apache Santuario XML Security for Java 1.4.x before 1.4.8 and 1.5.x before 1.5.5 allows context-dependent attackers to spoof an XML Signature by using the CanonicalizationMethod parameter to specify an arbitrary weak "canonicalization algorithm to apply to the SignedInfo part of the Signature." |
| CVE-2012-5055 | Medium | 2012-12-05 | No exploit published | No public exploit | DaoAuthenticationProvider in VMware SpringSource Spring Security before 2.0.8, 3.0.x before 3.0.8, and 3.1.x before 3.1.3 does not check the password if the user is not found, which makes the response delay shorter and might allow remote attackers to enumerate valid usernames via a series of login requests. |
| CVE-2011-2732 | Medium | 2012-12-05 | Mitigation candidate | Working exploit published | CRLF injection vulnerability in the logout functionality in VMware SpringSource Spring Security before 2.0.7 and 3.0.x before 3.0.6 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via the spring-security-redirect parameter. |
| CVE-2011-2731 | Medium | 2012-12-05 | No exploit published | No public exploit | Race condition in the RunAsManager mechanism in VMware SpringSource Spring Security before 2.0.7 and 3.0.x before 3.0.6 stores the Authentication object in the shared security context, which allows attackers to gain privileges via a crafted thread. |
| 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-3863 | Medium | 2010-11-05 | Protected by Waratek | Working exploit published | Apache Shiro before 1.1.0, and JSecurity 0.9.x, does not canonicalize URI paths before comparing them to entries in the shiro.ini file, which allows remote attackers to bypass intended access restrictions via a crafted request, as demonstrated by the /./account/index.jsp URI. |
| 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-2004-1029 | High | 2005-03-01 | Mitigation candidate | Working exploit published | The Sun Java Plugin capability in Java 2 Runtime Environment (JRE) 1.4.2_01, 1.4.2_04, and possibly earlier versions, does not properly restrict access between Javascript and Java applets during data transfer, which allows remote attackers to load unsafe classes and execute arbitrary code by using the reflection API to access private Java packages. |