CVE-2022-45136

Apache Jena SDB allows arbitrary deserialisation via JDBC

Published Nov 14, 2022 CVSS 3.1 · 9.8 Critical EPSS 1.8% KEV · Not listed
Description
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.

Remediation

Vendor Workaround

Apache Jena SDB has been EOL since December 2020, users should migrate to alternative options from the Apache Jena project e.g. Apache Jena TDB 2 or from 3rd party vendors.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-g2qw-6vrr-v6pq Apache Jena vulnerable to Deserialization of Untrusted Data
History
Type Values Removed Values Added
CPEs cpe:2.3:a:apache:jena_sdb:-:*:*:*:*:*:*:*
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Aug 3, 2024, 2:09 PM
Reserved
Nov 10, 2022, 12:00 AM
Status
Modified
Published
Nov 14, 2022, 4:15 PM
Modified
Jun 17, 2026, 5:09 AM