# CVE-2023-37364: XML external entity in n/a

> Attackers can exploit XML entity resolution in WS-Inc J WBEM Server to read arbitrary files or cause denial of service.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 3 Aug 2023
- **Updated:** 17 Oct 2024
- **Also known as:** GHSA-cv36-jhxc-fvcj

## What is CVE-2023-37364?

CVE-2023-37364 is a critical vulnerability in n/a, published on 3 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In WS-Inc J WBEM Server 4.7.4 before 4.7.5, the CIM-XML protocol adapter does not disable entity resolution. This allows context-dependent attackers to read arbitrary files or cause a denial of service, a similar issue to CVE-2013-4152.

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

## Which versions are affected by CVE-2023-37364?

It affects 1 product.


Products: Ws-Inc J Wbem.

## How do I fix CVE-2023-37364?

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

## Is CVE-2023-37364 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-37364 and fix it if it is affected.

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

## Sources

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

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