# CVE-2019-10337: Improper Restriction of XML External Entity Reference Jenkins Token Macro Plugin

> Attackers can exploit an XML External Entity vulnerability in the Jenkins Token Macro Plugin to extract secrets, cause SSRF, or trigger denial-of-service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 11 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g6h2-4x64-c59x

## What is CVE-2019-10337?

CVE-2019-10337 is a high-severity vulnerability in Jenkins Token Macro Plugin, published on 11 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An XML external entities (XXE) vulnerability in Jenkins Token Macro Plugin 2.7 and earlier allowed attackers able to control a the content of the input file for the "XML" macro to have Jenkins resolve external entities, resulting in the extraction of secrets from the Jenkins agent, server-side request forgery, or denial-of-service attacks.

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

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

2 open source packages ship an affected version, including org.jenkins-ci.plugins:token-macro. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:token-macro` | Maven | All versions | 2.8 |
| `org.jenkins-ci.plugins:token-macro` | Maven | All versions | 2.8 |

Products: Jenkins Token Macro.

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

Upgrade org.jenkins-ci.plugins:token-macro to 2.8 or later.

## Is CVE-2019-10337 being exploited?

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

## Other vulnerabilities in Jenkins Token Macro Plugin

- [CVE-2019-1003011](https://insights.sbomify.com/CVE-2019-1003011/): Jenkins Token Macro Plugin's recursive token expansion results in information disclosure and DoS (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10337 is a high-severity vulnerability in Jenkins Token Macro Plugin, published on 11 Jun 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-10337 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:token-macro (Maven): affected all versions; fixed in 2.8
- org.jenkins-ci.plugins:token-macro (Maven): affected all versions; fixed in 2.8

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

## Sources

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

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