# CVE-2021-37425: XML external entity in n/a

> An attacker can exploit XML External Entity vulnerabilities to read sensitive configuration files and private keys from the server.

- **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:** 10 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mwxw-r5fq-rx8v

## What is CVE-2021-37425?

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

### Official description

Altova MobileTogether Server before 7.3 SP1 allows XXE attacks, such as an InfoSetChanges/Changes attack against /workflowmanagement, or reading mobiletogetherserver.cfg and then reading the certificate and private key.

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

## Which versions are affected by CVE-2021-37425?

It affects 1 product.


Products: Altova Mobiletogether Server.

## How do I fix CVE-2021-37425?

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

## Is CVE-2021-37425 being exploited?

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

Public exploit code:

- Altova MobileTogether Server 7.3 - XML External Entity Injection (XXE) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-38490](https://insights.sbomify.com/CVE-2021-38490/): Altova MobileTogether Server before 7.3 SP1 allows XML exponential entity expansion, a different vulnerability than CVE-2021-37425. (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-37425 and fix it if it is affected.

What it is: CVE-2021-37425 is a critical vulnerability in n/a, published on 10 Aug 2021. 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-2021-37425 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-2021-37425/ (Markdown: https://insights.sbomify.com/CVE-2021-37425/index.md)
```

## Sources

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

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