# CVE-2022-41221: XML external entity in n/a

> Authenticated attackers can exploit XML External Entity vulnerabilities in OpenText Archive Center Administration to exfiltrate data or cause denial of service.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 May 2023
- **Updated:** 17 Jan 2025
- **Also known as:** GHSA-vqq8-vphp-8x9c

## What is CVE-2022-41221?

CVE-2022-41221 is a high-severity vulnerability in n/a, published on 24 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The client in OpenText Archive Center Administration through 21.2 allows XXE attacks. Authenticated users of the OpenText Archive Center Administration client (Versions 16.2.3, 21.2, and older versions) could upload XML files to the application that it did not sufficiently validate. As a result, attackers could craft XML files that, when processed by the application, would cause a negative security impact such as data exfiltration or localized denial of service against the application instance and system of the user running it.

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

## Which versions are affected by CVE-2022-41221?

It affects 1 product.


Products: Opentext Archive Center Administration.

## How do I fix CVE-2022-41221?

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

## Is CVE-2022-41221 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41221 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41221 and fix it if it is affected.

What it is: CVE-2022-41221 is a high-severity vulnerability in n/a, published on 24 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41221 exists.

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

## Sources

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

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