Skip to content

Improper input validation in Apache Santuario XML Security for Java

Moderate severity GitHub Reviewed Published Aug 27, 2019 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

maven org.apache.santuario:xmlsec (Maven)

Affected versions

>= 2.0.3, < 2.1.4

Patched versions

2.1.4

Description

In version 2.0.3 Apache Santuario XML Security for Java, a caching mechanism was introduced to speed up creating new XML documents using a static pool of DocumentBuilders. However, if some untrusted code can register a malicious implementation with the thread context class loader first, then this implementation might be cached and re-used by Apache Santuario - XML Security for Java, leading to potential security flaws when validating signed documents, etc. The vulnerability affects Apache Santuario - XML Security for Java 2.0.x releases from 2.0.3 and all 2.1.x releases before 2.1.4.

References

Published by the National Vulnerability Database Aug 23, 2019
Reviewed Aug 27, 2019
Published to the GitHub Advisory Database Aug 27, 2019
Last updated Feb 1, 2023

Severity

Moderate

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
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.200%
(59th percentile)

Weaknesses

CVE ID

CVE-2019-12400

GHSA ID

GHSA-4q98-wr72-h35w

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.