Deserialization in Apache Jena Sdb
CVE-2022-45136
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.
Vulnerability class: Insecure Deserialization
EPSS: 0.015 (72.1th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Affected products
- Apache Jena_sdb
- Apache Software Foundation Jena Sdb — versions unspecified
Weakness classification (CWE)
Public proof-of-concept exploits
References
- security@apache.org (Mailing List, Vendor Advisory)
- security@apache.org (mailing-list, Mailing List, Third Party Advisory)
Frequently asked questions
- What is CVE-2022-45136?
- CVE-2022-45136 is a critical-severity vulnerability in Apache Jena Sdb, classified under Deserialization of Untrusted Data. CVSS score: 9.8/10. Published 2022-11-14.
- How severe is CVE-2022-45136?
- Critical severity. CVSS v3 base score is 9.8 out of 10.
- Is CVE-2022-45136 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.