# CVE-2016-6256: XML external entity in n/a

> Remote attackers can exploit XML External Entity vulnerabilities in SAP Business One for Android to read sensitive data or cause denial of service.

- **Severity:** Critical 9.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jqcq-m297-wggx

## What is CVE-2016-6256?

CVE-2016-6256 is a critical vulnerability in n/a, published on 25 May 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SAP Business One for Android 1.2.3 allows remote attackers to conduct XML External Entity (XXE) attacks via crafted XML data in a request to B1iXcellerator/exec/soap/vP.001sap0003.in_WCSX/com.sap.b1i.vplatform.runtime/INB_WS_CALL_SYNC_XPT/INB_WS_CALL_SYNC_XPT.ipo/proc, aka SAP Security Note 2378065.

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

## Which versions are affected by CVE-2016-6256?

It affects 1 product.


Products: Sap Business One.

## How do I fix CVE-2016-6256?

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

## Is CVE-2016-6256 being exploited?

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

Public exploit code:

- SAP Business One for Android 1.2.3 - XML External Entity Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-33698](https://insights.sbomify.com/CVE-2021-33698/): File upload in SAP Business One (critical 9.9)
- [CVE-2021-38180](https://insights.sbomify.com/CVE-2021-38180/): Code injection in SAP Business One (critical 9.8)
- [CVE-2023-31403](https://insights.sbomify.com/CVE-2023-31403/): Improper Access Control vulnerability in SAP Business One product installation (critical 9.6)
- [CVE-2022-31593](https://insights.sbomify.com/CVE-2022-31593/): Code injection in SAP Business One (high 8.8)
- [CVE-2018-2425](https://insights.sbomify.com/CVE-2018-2425/): Information disclosure in SAP Business One (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6256 and fix it if it is affected.

What it is: CVE-2016-6256 is a critical vulnerability in n/a, published on 25 May 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-6256 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-2016-6256/ (Markdown: https://insights.sbomify.com/CVE-2016-6256/index.md)
```

## Sources

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

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