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

> An attacker can exploit an XML External Entity vulnerability in the BlueCat Device Registration Portal to exfiltrate sensitive single-line files, such as credentials.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2023
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-pxhp-jr2p-7hw7

## What is CVE-2023-23595?

CVE-2023-23595 is a high-severity vulnerability in n/a, published on 15 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BlueCat Device Registration Portal 2.2 allows XXE attacks that exfiltrate single-line files. A single-line file might contain credentials, such as "machine example.com login daniel password qwerty" in the documentation example for the .netrc file format. NOTE: 2.x versions are no longer supported. There is no available information about whether any later version is affected.

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

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

It affects 1 product.


Products: Bluecatnetworks Device Registration Portal.

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

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

## Is CVE-2023-23595 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-23595 is a high-severity vulnerability in n/a, published on 15 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-23595 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-2023-23595/ (Markdown: https://insights.sbomify.com/CVE-2023-23595/index.md)
```

## Sources

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

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