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

> Authenticated attackers can exploit XML external entity vulnerabilities in Assyst to perform server-side request forgery and access internal resources.

- **Severity:** High 7.7 (`CVSS:3.1/AC:H/AV:N/A:H/C:L/I:L/PR:L/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-92h7-3mpg-68jh

## What is CVE-2021-30137?

CVE-2021-30137 is a high-severity vulnerability in n/a, published on 15 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Assyst 10 SP7.5 has authenticated XXE leading to SSRF via XML unmarshalling. The application allows users to send JSON or XML data to the server. It was possible to inject malicious XML data through several access points.

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

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

It affects 1 product.


Products: Axiossystems Assyst.

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

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

## Is CVE-2021-30137 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-30137 is a high-severity vulnerability in n/a, published on 15 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-30137 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-30137/ (Markdown: https://insights.sbomify.com/CVE-2021-30137/index.md)
```

## Sources

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

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