Overview 9 matches · 7 protected · 1 exploited · 0 CISA KEV · 2 EPSS ≥ 0.5
Protected by Waratek
7
77.8%
Rule in development
0
0.0%
Mitigation candidate
2
22.2%
No exploit published
0
0.0%
blocked by ARMR today
7
77.8%
partly blocked
0
0.0%
not blocked
2
22.2%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
11.1%
Working exploit published
5
55.6%
Proof of concept only
3
33.3%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 2 / year
20111
Protected by Waratek1
Medium1
blocked by ARMR today1
Proof of concept only1
20121
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
20131
Protected by Waratek1
Medium1
blocked by ARMR today1
Working exploit published1
20141
Protected by Waratek1
Medium1
blocked by ARMR today1
Proof of concept only1
20150
20160
20170
20181
Protected by Waratek1
Medium1
blocked by ARMR today1
Working exploit published1
20191
Protected by Waratek1
Medium1
blocked by ARMR today1
Working exploit published1
20202
Protected by Waratek1
Mitigation candidate1
Medium2
blocked by ARMR today1
not blocked1
Exploited1
Working exploit published1
20210
20220
20231
Protected by Waratek1
Medium1
blocked by ARMR today1
Proof of concept only1
2011201320152017201920212023
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2023-34050 | Medium | 2023-10-19 | Protected by Waratek | Proof of concept only | In spring AMQP versions 1.0.0 to 2.4.16 and 3.0.0 to 3.0.9 , allowed list patterns for deserializable class names were added to Spring AMQP, allowing users to lock down deserialization of data in messages from untrusted sources; however by default, when no allowed list was provided, all classes could be deserialized. Specifically, an application is vulnerable if * the SimpleMessageConverter or SerializerMessageConverter is used * the user does not configure allowed list patterns * untrusted message originators gain permissions to write messages to the RabbitMQ broker to send malicious content |
| CVE-2020-5412 | Medium | 2020-08-07 | Mitigation candidate | Exploited | Spring Cloud Netflix, versions 2.2.x prior to 2.2.4, versions 2.1.x prior to 2.1.6, and older unsupported versions allow applications to use the Hystrix Dashboard proxy.stream endpoint to make requests to any server reachable by the server hosting the dashboard. A malicious user, or attacker, can send a request to other servers that should not be exposed publicly. |
| CVE-2020-5405 | Medium | 2020-03-05 | Protected by Waratek | Working exploit published | Spring Cloud Config, versions 2.2.x prior to 2.2.2, versions 2.1.x prior to 2.1.7, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead a directory traversal attack. |
| CVE-2019-3799 | Medium | 2019-05-06 | Protected by Waratek | Working exploit published | Spring Cloud Config, versions 2.1.x prior to 2.1.2, versions 2.0.x prior to 2.0.4, and versions 1.4.x prior to 1.4.6, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead a directory traversal 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-2014-3625 | Medium | 2014-11-20 | Protected by Waratek | Proof of concept only | Directory traversal vulnerability in Pivotal Spring Framework 3.0.4 through 3.2.x before 3.2.12, 4.0.x before 4.0.8, and 4.1.x before 4.1.2 allows remote attackers to read arbitrary files via unspecified vectors, related to static resource handling. |
| CVE-2013-6366 | Medium | 2013-11-04 | Protected by Waratek | Working exploit published | The Groovy script console in VMware Hyperic HQ 4.6.6 allows remote authenticated administrators to execute arbitrary code via a Runtime.getRuntime().exec call. |
| 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-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. |