Vulnerability in the Java SE, Java SE Embedded product of Oracle Java SE (component: Serialization). Supported versions that are affected are Java SE: 7u241, 8u231, 11.0.5 and 13.0.1; Java SE Embedded: 8u231. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks of this vulnerability can result in takeover of Java SE, Java SE Embedded. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets (in Java SE 8), that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability can also be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. CVSS v3.0 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).
The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Commerce_experience_manager | Oracle | 11.3.2 (including) | 11.3.2 (including) |
| Commerce_guided_search | Oracle | 11.3.2 (including) | 11.3.2 (including) |
| Graalvm | Oracle | 19.3.0.2 (including) | 19.3.0.2 (including) |
| Jdk | Oracle | 1.7.0-update241 (including) | 1.7.0-update241 (including) |
| Jdk | Oracle | 1.8.0-update231 (including) | 1.8.0-update231 (including) |
| Jdk | Oracle | 11.0.5 (including) | 11.0.5 (including) |
| Jdk | Oracle | 13.0.1 (including) | 13.0.1 (including) |
| Jre | Oracle | 1.8.0-update231 (including) | 1.8.0-update231 (including) |
It is often convenient to serialize objects for communication or to save them for later use. However, deserialized data or code can often be modified without using the provided accessor functions if it does not use cryptography to protect itself. Furthermore, any cryptography would still be client-side security – which is a dangerous security assumption. Data that is untrusted can not be trusted to be well-formed. When developers place no restrictions on “gadget chains,” or series of instances and method invocations that can self-execute during the deserialization process (i.e., before the object is returned to the caller), it is sometimes possible for attackers to leverage them to perform unauthorized actions, like generating a shell.