# CVE-2021-22501: XML external entity in Operations Bridge Manager

> An XML External Entity vulnerability in OpenText Operations Bridge Manager allows attackers to access confidential information.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/S:N/AU:Y/R:A/V:C/RE:M/U:Amber`)
- **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:** 19 Dec 2024
- **Updated:** 20 Dec 2024
- **Also known as:** GHSA-j3gf-gcj2-hmm5

## What is CVE-2021-22501?

CVE-2021-22501 is a medium-severity vulnerability in OpenText™ Operations Bridge Manager, published on 19 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Restriction of XML External Entity Reference vulnerability in OpenText™ Operations Bridge Manager allows Input Data Manipulation. 

The vulnerability could be exploited to confidential information

This issue affects Operations Bridge Manager: 2017.05, 2017.11, 2018.05, 2018.11, 2019.05, 2019.11, 2020.05, 2020.10.

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

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


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

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

## Is CVE-2021-22501 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-22501 is a medium-severity vulnerability in OpenText™ Operations Bridge Manager, published on 19 Dec 2024. 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-22501 in the wild and no public exploit code.

Affected product: OpenText™ Operations Bridge Manager. 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-22501/ (Markdown: https://insights.sbomify.com/CVE-2021-22501/index.md)
```

## Sources

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

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