# CVE-2019-13990: XML external entity injection in Terracotta Quartz Scheduler

> An attacker can exploit an XML External Entity vulnerability in the Quartz Scheduler library to read sensitive files or cause denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jul 2019
- **Updated:** 15 Oct 2024
- **Also known as:** CLSA-2026-1778028240, DEBIAN-CVE-2019-13990, GHSA-9qcf-c26r-x5rf, MGASA-2021-0133, SUSE-SU-2020:0984-1, SUSE-SU-2020:1009-1, UBUNTU-CVE-2019-13990

## What is CVE-2019-13990?

CVE-2019-13990 is a critical vulnerability in Netapp Active Iq Unified Manager, published on 26 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

initDocumentParser in xml/XMLSchedulingDataProcessor.java in Terracotta Quartz Scheduler through 2.3.0 allows XXE attacks via a job description.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

2 open source packages ship an affected version, including org.quartz-scheduler:quartz. It affects 31 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.quartz-scheduler:quartz` | Maven | All versions | 2.3.2 |
| `org.quartz-scheduler:quartz` | Maven | All versions | 2.3.2 |
| `quartz` | SUSE:Manager Server 3.2 | All versions | 2.3.0-14.3.1 |
| `quartz` | SUSE:Manager Server Module 4.0 | All versions | 2.3.0-4.3.1 |

Products: Apache Tomee, Atlassian Jira Service Management, Netapp Active Iq Unified Manager, Netapp Cloud Secure Agent, Oracle Apache Batik Mapviewer, Oracle Banking Enterprise Originations, Oracle Banking Enterprise Product Manufacturing, Oracle Banking Payments, Oracle Communications Ip Service Activator, Oracle Communications Session Route Manager, Oracle Customer Management and Segmentation Foundation, Oracle Documaker, Oracle Enterprise Manager Base Platform, Oracle Enterprise Manager Ops Center, Oracle Flexcube Investor Servicing, Oracle Flexcube Private Banking, Oracle Fusion Middleware Mapviewer, Oracle Google Guava Mapviewer, Oracle Hyperion Infrastructure Technology, Oracle Jd Edwards Enterpriseone Orchestrator and 11 more.

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

Upgrade org.quartz-scheduler:quartz to 2.3.2 or later.

## Is CVE-2019-13990 being exploited?

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

Public exploit code:

- quartz with CVE-2019-13990 (github_poc): https://github.com/epicosy/Quartz-1

## Other vulnerabilities in Netapp Active Iq Unified Manager

- [CVE-2020-13931](https://insights.sbomify.com/CVE-2020-13931/): Remote code execution in Apache TomEE (critical 9.8)
- [CVE-2020-11969](https://insights.sbomify.com/CVE-2020-11969/): Missing Authentication for Critical Function in Apache TomEE (critical 9.8)
- [CVE-2016-0779](https://insights.sbomify.com/CVE-2016-0779/): Deserialization in n/a (critical 9.8)
- [CVE-2019-17359](https://insights.sbomify.com/CVE-2019-17359/): Out-of-Memory Error in Bouncy Castle Crypto (high 7.5)
- [CVE-2018-8031](https://insights.sbomify.com/CVE-2018-8031/): Apache TomEE console vulnerable to Cross-site Scripting (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-13990 is a critical vulnerability in Netapp Active Iq Unified Manager, published on 26 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-13990 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.quartz-scheduler:quartz (Maven): affected all versions; fixed in 2.3.2
- org.quartz-scheduler:quartz (Maven): affected all versions; fixed in 2.3.2

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-13990/ (Markdown: https://insights.sbomify.com/CVE-2019-13990/index.md)
```

## Sources

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

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