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.
References
Link | Resource |
---|---|
http://www.openwall.com/lists/oss-security/2022/11/14/5 | Mailing List Third Party Advisory |
https://lists.apache.org/thread/mc77cdl5stgjtjoldk467gdf756qjt31 | Mailing List Vendor Advisory |
Configurations
History
07 Nov 2023, 03:54
Type | Values Removed | Values Added |
---|---|---|
Summary | 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. |
Information
Published : 2022-11-14 16:15
Updated : 2024-08-03 14:15
NVD link : CVE-2022-45136
Mitre link : CVE-2022-45136
CVE.ORG link : CVE-2022-45136
JSON object : View
Products Affected
apache
- jena_sdb
CWE
CWE-502
Deserialization of Untrusted Data