Apache Jena SDB 3.17.0 and earlier is vulnerable to a JDBC Deserialisation attack if the attacker is able to control the JDBC URL used or cause the underlying database server to return malicious data. The mySQL JDBC driver in particular is known to be vulnerable to this class of attack. As a result an application using Apache Jena SDB can be subject to RCE when connected to a malicious database server. Apache Jena SDB has been EOL since December 2020 and users should migrate to alternative options e.g. Apache Jena TDB 2.
The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Jena_sdb | Apache | * | 3.17.0 (including) |
| Apache-jena | Ubuntu | kinetic | * |
| Apache-jena | Ubuntu | lunar | * |
| Apache-jena | Ubuntu | mantic | * |
| Apache-jena | Ubuntu | trusty | * |
| Apache-jena | Ubuntu | xenial | * |
| Sdb | Ubuntu | bionic | * |
| Sdb | Ubuntu | kinetic | * |
| Sdb | Ubuntu | lunar | * |
| Sdb | Ubuntu | trusty | * |
| Sdb | 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.