# CVE-2022-45876: CVE-2022-45876

> A valid user opening a crafted file in VISAM VBASE Automation Base can cause information disclosure via XML External Entity injection.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **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:** 26 Apr 2023
- **Updated:** 17 Jan 2025
- **Also known as:** GHSA-w9p6-vq7q-w6q7

## What is CVE-2022-45876?

CVE-2022-45876 is a medium-severity vulnerability in VISAM VBASE, published on 26 Apr 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

Versions of VISAM VBASE Automation Base prior to 11.7.5 may disclose information if a valid user opens a specially crafted file.

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

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

It affects 1 product.


Products: Visam Vbase.

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

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

## Is CVE-2022-45876 being exploited?

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

## Other vulnerabilities in VISAM VBASE

- [CVE-2022-3217](https://insights.sbomify.com/CVE-2022-3217/): Weak cryptography in VISAM VBASE (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45876 is a medium-severity vulnerability in VISAM VBASE, published on 26 Apr 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: There is no known exploitation of CVE-2022-45876 in the wild and no public exploit code.

Affected product: VISAM VBASE. 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-45876/ (Markdown: https://insights.sbomify.com/CVE-2022-45876/index.md)
```

## Sources

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

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