# CVE-2019-10309: Jenkins Self-Organizing Swarm Plug-in Modules Plugin XXE vulnerability via UDP broadcast response

> An attacker on the same network can read arbitrary files from Jenkins Swarm clients due to XML External Entity processing in UDP discovery responses.

- **Severity:** Critical 9.3 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w898-3ph8-5pgm

## What is CVE-2019-10309?

CVE-2019-10309 is a critical vulnerability in Jenkins Self-Organizing Swarm Plug-in Modules Plugin, published on 30 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Jenkins Self-Organizing Swarm Plug-in Modules Plugin clients that use UDP broadcasts to discover Jenkins masters do not prevent XML External Entity processing when processing the responses, allowing unauthorized attackers on the same network to read arbitrary files from Swarm clients.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:swarm` | Maven | All versions to 3.15 | None |
| `org.jenkins-ci.plugins:swarm` | Maven | All versions to 3.15 | None |

Products: Jenkins Self-Organizing Swarm Modules.

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

No fix has been published for CVE-2019-10309 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-10309 being exploited?

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

## Other vulnerabilities in Jenkins Self-Organizing Swarm Plug-in Modules Plugin

- [CVE-2020-2192](https://insights.sbomify.com/CVE-2020-2192/): CSRF vulnerability in Jenkins Swarm Plugin (medium 6.5)
- [CVE-2020-2191](https://insights.sbomify.com/CVE-2020-2191/): Improper permission checks in Jenkins Swarm Plugin (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10309 is a critical vulnerability in Jenkins Self-Organizing Swarm Plug-in Modules Plugin, published on 30 Apr 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-10309 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:swarm (Maven): affected all versions up to 3.15; no fix listed
- org.jenkins-ci.plugins:swarm (Maven): affected all versions up to 3.15; no fix listed

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

## Sources

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

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