Skip to content

Apache Jena vulnerable to Deserialization of Untrusted Data

Critical severity GitHub Reviewed Published Nov 14, 2022 to the GitHub Advisory Database • Updated Jan 29, 2023

Package

maven org.apache.jena:jena-sdb (Maven)

Affected versions

>= 0.0.0

Patched versions

None

Description

** UNSUPPORTED WHEN ASSIGNED ** 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

Published by the National Vulnerability Database Nov 14, 2022
Published to the GitHub Advisory Database Nov 14, 2022
Reviewed Nov 17, 2022
Last updated Jan 29, 2023

Severity

Critical
9.8
/ 10

CVSS base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weaknesses

CVE ID

CVE-2022-45136

GHSA ID

GHSA-g2qw-6vrr-v6pq

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.