# CVE-2019-12400: Improper input validation in Apache Santuario XML Security for Java

> Attackers can inject malicious code via thread context class loader caching, compromising XML document validation in Apache Santuario.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-12400, GHSA-4q98-wr72-h35w, UBUNTU-CVE-2019-12400

## What is CVE-2019-12400?

CVE-2019-12400 is a medium-severity code injection vulnerability in Oracle Weblogic Server, published on 23 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2019-12400?

2 open source packages ship an affected version, including org.apache.santuario:xmlsec. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.santuario:xmlsec` | Maven | From 2.0.3 | 2.1.4 |
| `org.apache.santuario:xmlsec` | Maven | From 2.0.3 | 2.1.4 |

Products: Apache Santuario Xml Security for Java, Oracle Weblogic Server, Redhat Jboss Enterprise Application Platform.

## How do I fix CVE-2019-12400?

Upgrade org.apache.santuario:xmlsec to 2.1.4 or later.

## Is CVE-2019-12400 being exploited?

There is no known exploitation of CVE-2019-12400 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Weblogic Server

- [CVE-2023-44483](https://insights.sbomify.com/CVE-2023-44483/): Apache Santuario: Private Key disclosure in debug-log output (medium 6.5)
- [CVE-2014-8152](https://insights.sbomify.com/CVE-2014-8152/): Improper Input Validation in Apache Santuario XML Security (medium 5.0)
- [CVE-2013-4517](https://insights.sbomify.com/CVE-2013-4517/): Improper Input Validation in Apache Santuario XML Security (medium 4.3)
- [CVE-2013-2172](https://insights.sbomify.com/CVE-2013-2172/): Inefficient Algorithmic Complexity in Apache Santuario XML Security (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12400 and fix it if it is affected.

What it is: CVE-2019-12400 is a medium-severity code injection vulnerability in Oracle Weblogic Server, published on 23 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12400 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.santuario:xmlsec (Maven): affected from 2.0.3; fixed in 2.1.4
- org.apache.santuario:xmlsec (Maven): affected from 2.0.3; fixed in 2.1.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-12400/ (Markdown: https://insights.sbomify.com/CVE-2019-12400/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-12400
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-12400
- OSV: https://osv.dev/vulnerability/CVE-2019-12400

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-12400/
Summaries are generated and may contain mistakes; the official description above is the record.