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 Aug 2, 2024

Package

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

Affected versions

<= 3.17.0

Patched versions

None

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.

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 Aug 2, 2024

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

4.629%
(93rd percentile)

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.