Scala 2.13.x before 2.13.9 has a Java deserialization chain in its JAR file. On its own, it cannot be exploited. There is only a risk in conjunction with Java object deserialization within an application. In such situations, it allows attackers to erase contents of arbitrary files, make network connections, or possibly run arbitrary code (specifically, Function0 functions) via a gadget chain.
The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Scala | Scala-lang | 2.13.0 (including) | 2.13.9 (excluding) |
| Scala-collection-compat | Scala-lang | * | 2.9.0 (excluding) |
| Red Hat AMQ Streams 2.4.0 | RedHat | scala | * |
| Red Hat AMQ Streams 2.5.0 | RedHat | * | |
| Scala | Ubuntu | bionic | * |
| Scala | Ubuntu | focal | * |
| Scala | Ubuntu | kinetic | * |
| Scala | Ubuntu | lunar | * |
| Scala | Ubuntu | mantic | * |
| Scala | Ubuntu | oracular | * |
| Scala | Ubuntu | trusty | * |
| Scala | Ubuntu | upstream | * |
| Scala | Ubuntu | xenial | * |
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.