Overview 113 matches · 0 protected · 3 exploited · 0 CISA KEV · 15 public PoC · 3 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
20
17.7%
No exploit published
93
82.3%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
113
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 30 / year
20131
Mitigation candidate1
High1
not blocked1
No public exploit1
20140
20150
20161
Mitigation candidate1
High1
not blocked1
Working exploit published1
20175
No exploit published5
Critical3
High2
not blocked5
No public exploit5
20186
No exploit published6
Critical3
High1
Medium2
not blocked6
No public exploit6
20195
No exploit published5
Critical5
not blocked5
No public exploit5
202026
Mitigation candidate7
No exploit published19
Critical9
High17
not blocked26
Exploited2
Proof of concept only4
No public exploit20
202130
Mitigation candidate7
No exploit published23
Critical1
High28
Medium1
not blocked30
Exploited1
Working exploit published3
Proof of concept only3
Forecast only1
No public exploit22
20229
Mitigation candidate2
No exploit published7
Critical3
High5
Medium1
not blocked9
Proof of concept only4
No public exploit5
20235
Mitigation candidate1
No exploit published4
Critical4
High1
not blocked5
Proof of concept only2
No public exploit3
20241
Mitigation candidate1
High1
not blocked1
Proof of concept only1
20250
202624
No exploit published24
Critical9
High11
Medium2
Low2
not blocked24
Proof of concept only2
No public exploit22
2014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2018-1904 | Critical | 2018-12-11 | No exploit published | No public exploit | IBM WebSphere Application Server 7.0, 8.0, 8.5, and 9.0 could allow remote attackers to execute arbitrary Java code through an administrative client class with a serialized object from untrusted sources. IBM X-Force ID: 152533. |
| CVE-2018-18240 | Critical | 2018-10-11 | No exploit published | No public exploit | Pippo through 1.11.0 allows remote code execution via a command to java.lang.ProcessBuilder because the XstreamEngine component does not use XStream's available protection mechanisms to restrict unmarshalling. |
| CVE-2018-1567 | Critical | 2018-09-07 | No exploit published | No public exploit | IBM WebSphere Application Server 7.0, 8.0, 8.5, and 9.0 could allow remote attackers to execute arbitrary Java code through the SOAP connector with a serialized object from untrusted sources. IBM X-Force ID: 143024. |
| CVE-2018-1999042 | Medium | 2018-08-23 | No exploit published | No public exploit | A vulnerability exists in Jenkins 2.137 and earlier, 2.121.2 and earlier in XStream2.java that allows attackers to have Jenkins resolve a domain name when deserializing an instance of java.net.URL. |
| CVE-2017-2608 | High | 2018-05-15 | No exploit published | No public exploit | Jenkins before versions 2.44, 2.32.2 is vulnerable to a remote code execution vulnerability involving the deserialization of various types in javax.imageio in XStream-based APIs (SECURITY-383). |
| CVE-2017-1000355 | Medium | 2018-01-29 | No exploit published | No public exploit | Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to an XStream: Java crash when trying to instantiate void/Void. |
| CVE-2017-4995 | High | 2017-11-27 | No exploit published | No public exploit | An issue was discovered in Pivotal Spring Security 4.2.0.RELEASE through 4.2.2.RELEASE, and Spring Security 5.0.0.M1. When configured to enable default typing, Jackson contained a deserialization vulnerability that could lead to arbitrary code execution. Jackson fixed this vulnerability by blacklisting known "deserialization gadgets." Spring Security configures Jackson with global default typing enabled, which means that (through the previous exploit) arbitrary code could be executed if all of the following is true: (1) Spring Security's Jackson support is being leveraged by invoking SecurityJackson2Modules.getModules(ClassLoader) or SecurityJackson2Modules.enableDefaultTyping(ObjectMapper); (2) Jackson is used to deserialize data that is not trusted (Spring Security does not perform deserialization using Jackson, so this is an explicit choice of the user); and (3) there is an unknown (Jackson is not blacklisting it already) "deserialization gadget" that allows code execution present on the classpath. Jackson provides a blacklisting approach to protecting against this type of attack, but Spring Security should be proactive against blocking unknown "deserialization gadgets" when Spring Security enables default typing. |
| CVE-2016-8744 | High | 2017-09-13 | No exploit published | No public exploit | Apache Brooklyn uses the SnakeYAML library for parsing YAML inputs. SnakeYAML allows the use of YAML tags to indicate that SnakeYAML should unmarshal data to a Java type. In the default configuration in Brooklyn before 0.10.0, SnakeYAML will allow unmarshalling to any Java type available on the classpath. This could provide an authenticated user with a means to cause the JVM running Brooklyn to load and run Java code without detection by Brooklyn. Such code would have the privileges of the Java process running Brooklyn, including the ability to open files and network connections, and execute system commands. There is known to be a proof-of-concept exploit using this vulnerability. |
| CVE-2016-3690 | Critical | 2017-06-08 | No exploit published | No public exploit | The PooledInvokerServlet in JBoss EAP 4.x and 5.x allows remote attackers to execute arbitrary code via a crafted serialized payload. |
| CVE-2016-8749 | Critical | 2017-03-28 | No exploit published | No public exploit | Apache Camel's Jackson and JacksonXML unmarshalling operation are vulnerable to Remote Code Execution attacks. |
| CVE-2017-3159 | Critical | 2017-03-07 | No exploit published | No public exploit | Apache Camel's camel-snakeyaml component is vulnerable to Java object de-serialization vulnerability. De-serializing untrusted data can lead to security flaws. |
| CVE-2016-0792 | High | 2016-04-07 | Mitigation candidate | Working exploit published | Multiple unspecified API endpoints in Jenkins before 1.650 and LTS before 1.642.2 allow remote authenticated users to execute arbitrary code via serialized data in an XML file, related to XStream and groovy.util.Expando. |
| CVE-2013-1768 | High | 2013-07-11 | Mitigation candidate | No public exploit | The BrokerFactory functionality in Apache OpenJPA 1.x before 1.2.3 and 2.x before 2.2.2 creates local executable JSP files containing logging trace data produced during deserialization of certain crafted OpenJPA objects, which makes it easier for remote attackers to execute arbitrary code by creating a serialized object and leveraging improperly secured server programs. |