# CVE-2022-45397: XXE vulnerability on agents in Jenkins OSF Builder Suite : : XML Linter Plugin

> An attacker can exploit XML external entity vulnerabilities in the Jenkins XML Linter Plugin 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:** No
- **Published:** 15 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-8847-xvjw-9g43

## What is CVE-2022-45397?

CVE-2022-45397 is a critical vulnerability in Jenkins OSF Builder Suite : : XML Linter Plugin, published on 15 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jenkins OSF Builder Suite : : XML Linter Plugin 1.0.2 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.

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

## Which versions are affected by CVE-2022-45397?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci:update-center2` | Maven | All versions to 1.0.2 | None |
| `org.jenkins-ci:update-center2` | Maven | All versions to 1.0.2 | None |

Products: Jenkins Osf Builder Suite \.

## How do I fix CVE-2022-45397?

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

## Is CVE-2022-45397 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45397 and fix it if it is affected.

What it is: CVE-2022-45397 is a critical vulnerability in Jenkins OSF Builder Suite : : XML Linter Plugin, published on 15 Nov 2022. 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-2022-45397 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci:update-center2 (Maven): affected all versions up to 1.0.2; no fix listed
- org.jenkins-ci:update-center2 (Maven): affected all versions up to 1.0.2; 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-2022-45397/ (Markdown: https://insights.sbomify.com/CVE-2022-45397/index.md)
```

## Sources

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

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