# CVE-2023-30951: CVE-2023-30951

> An attacker can exploit an XML External Entity vulnerability in the Magritte rest-source plugin to read sensitive data or cause denial of service.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **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:** 3 Aug 2023
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-jcmm-4pwv-fqp4

## What is CVE-2023-30951?

CVE-2023-30951 is a medium-severity vulnerability in com.palantir.magritte:magritte-rest-source-bundle, published on 3 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Foundry Magritte plugin rest-source was found to be vulnerable to an an XML external Entity attack (XXE).

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

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

It affects 1 product.


Products: Palantir Magritte-Rest-Source-Bundle.

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

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

## Is CVE-2023-30951 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-30951 is a medium-severity vulnerability in com.palantir.magritte:magritte-rest-source-bundle, published on 3 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-30951 in the wild and no public exploit code.

Affected product: com.palantir.magritte:magritte-rest-source-bundle. 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-30951/ (Markdown: https://insights.sbomify.com/CVE-2023-30951/index.md)
```

## Sources

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

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