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

> Remote attackers can read arbitrary files via crafted XML requests in SAP Mobile Platform 3, requiring immediate patching.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h548-2rxv-x7x7

## What is CVE-2015-5068?

CVE-2015-5068 is a high-severity vulnerability in n/a, published on 24 Jun 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

XML external entity (XXE) vulnerability in SAP Mobile Platform 3 allows remote attackers to read arbitrary files or possibly have other unspecified impact via a crafted XML request, aka SAP Security Note 2159601.

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

It affects 1 product.


Products: Sap Mobile Platform.

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

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

## Is CVE-2015-5068 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-2459](https://insights.sbomify.com/CVE-2018-2459/): Information disclosure in SAP Mobile Platform (high 7.5)
- [CVE-2015-8600](https://insights.sbomify.com/CVE-2015-8600/): Auth bypass in n/a (high 7.5)
- [CVE-2015-6664](https://insights.sbomify.com/CVE-2015-6664/): XML external entity in n/a (medium 6.8)
- [CVE-2015-7731](https://insights.sbomify.com/CVE-2015-7731/): Information disclosure in n/a (medium 5.5)
- [CVE-2015-2813](https://insights.sbomify.com/CVE-2015-2813/): XML external entity in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-5068 is a high-severity vulnerability in n/a, published on 24 Jun 2015. 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-2015-5068 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-5068/ (Markdown: https://insights.sbomify.com/CVE-2015-5068/index.md)
```

## Sources

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

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