# CVE-2015-4091: XML external entity in n/a

> Remote attackers can exploit an XML external entity vulnerability in SAP NetWeaver AS Java to access intranet servers or cause other impacts.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x4m2-h5qg-m95h

## What is CVE-2015-4091?

CVE-2015-4091 is a high-severity vulnerability in n/a, published on 26 May 2015. It can be exploited over the network, with no action from the victim.

### Official description

XML external entity (XXE) vulnerability in SAP NetWeaver AS Java 7.4 allows remote attackers to send TCP requests to intranet servers or possibly have unspecified other impact via an XML request to tc~sld~wd~main/Main, related to "CIM UPLOAD," aka SAP Security Note 2090851.

## Which versions are affected by CVE-2015-4091?

It affects 1 product.


Products: Sap Sap Netweaver Application Server Java.

## How do I fix CVE-2015-4091?

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

## Is CVE-2015-4091 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4091 and fix it if it is affected.

What it is: CVE-2015-4091 is a high-severity vulnerability in n/a, published on 26 May 2015. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-4091 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-2015-4091/ (Markdown: https://insights.sbomify.com/CVE-2015-4091/index.md)
```

## Sources

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

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