# CVE-2020-2178: XXE vulnerability in Jenkins Parasoft Findings Plugin

> An attacker can exploit XML external entity vulnerabilities in the Jenkins Parasoft Findings Plugin to read sensitive files or cause denial of service.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2rh4-xgmq-63jp

## What is CVE-2020-2178?

CVE-2020-2178 is a high-severity vulnerability in Jenkins Parasoft Findings Plugin, published on 16 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Parasoft Findings Plugin 10.4.3 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-2020-2178?

2 open source packages ship an affected version, including com.parasoft:parasoft-findings. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.parasoft:parasoft-findings` | Maven | All versions | 10.4.4 |
| `com.parasoft:parasoft-findings` | Maven | All versions | 10.4.4 |

Products: Jenkins Parasoft Findings.

## How do I fix CVE-2020-2178?

Upgrade com.parasoft:parasoft-findings to 10.4.4 or later.

## Is CVE-2020-2178 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-2178 and fix it if it is affected.

What it is: CVE-2020-2178 is a high-severity vulnerability in Jenkins Parasoft Findings Plugin, published on 16 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-2178 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.parasoft:parasoft-findings (Maven): affected all versions; fixed in 10.4.4
- com.parasoft:parasoft-findings (Maven): affected all versions; fixed in 10.4.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-2020-2178/ (Markdown: https://insights.sbomify.com/CVE-2020-2178/index.md)
```

## Sources

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

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