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

> An attacker can exploit an XML External Entity vulnerability in ASG-Zena Cross Platform Server to read sensitive data 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:** 17 Jun 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-64vq-q588-gmpm

## What is CVE-2021-45024?

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

### Official description

ASG technologies ( A Rocket Software Company) ASG-Zena Cross Platform Server Enterprise Edition 4.2.1 is vulnerable to XML External Entity (XXE).

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

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

It affects 1 product.


Products: Rocketsoftware Ags-Zena.

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

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

## Is CVE-2021-45024 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-45025](https://insights.sbomify.com/CVE-2021-45025/): Information disclosure in n/a (high 7.5)
- [CVE-2021-45026](https://insights.sbomify.com/CVE-2021-45026/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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