# CVE-2020-24052: XML external entity in n/a

> Remote unauthenticated attackers can read arbitrary files on Moog EXO Series units via crafted XML requests containing malicious DTDs.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** No
- **Published:** 21 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rfhm-xwgj-v2q9

## What is CVE-2020-24052?

CVE-2020-24052 is a critical vulnerability in n/a, published on 21 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Several XML External Entity (XXE) vulnerabilities in the Moog EXO Series EXVF5C-2 and EXVP7C2-3 units allow remote unauthenticated users to read arbitrary files via a crafted Document Type Definition (DTD) in an XML request.

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

## Which versions are affected by CVE-2020-24052?

It affects 2 products.


Products: Moog Exvf5c-2 Firmware, Moog Exvp7c2-3 Firmware.

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

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

## Is CVE-2020-24052 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-24051](https://insights.sbomify.com/CVE-2020-24051/): Auth bypass in n/a (critical 9.8)
- [CVE-2020-24054](https://insights.sbomify.com/CVE-2020-24054/): Command injection in n/a (critical 9.8)
- [CVE-2020-24053](https://insights.sbomify.com/CVE-2020-24053/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-24052 is a critical vulnerability in n/a, published on 21 Aug 2020. 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-2020-24052 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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