# CVE-2018-2416: XML external entity in SAP Identity Management

> Attackers can exploit insufficient XML validation in SAP Identity Management to read sensitive data or cause denial of service.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L`)
- **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:** 9 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f95c-99jv-mf4r

## What is CVE-2018-2416?

CVE-2018-2416 is a medium-severity vulnerability in SAP Identity Management, published on 9 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP Identity Management 7.2 and 8.0 do not sufficiently validate an XML document accepted from an untrusted source.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-2416?

It affects 1 product.


Products: Sap Identity Management.

## How do I fix CVE-2018-2416?

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

## Is CVE-2018-2416 being exploited?

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

## Other vulnerabilities in SAP Identity Management

- [CVE-2019-0301](https://insights.sbomify.com/CVE-2019-0301/): Privilege escalation in SAP Identity Management (REST Interface) (high 8.8)
- [CVE-2018-2417](https://insights.sbomify.com/CVE-2018-2417/): Information disclosure in SAP Identity Management (medium 5.3)
- [CVE-2020-6258](https://insights.sbomify.com/CVE-2020-6258/): Missing authorization in SAP Identity Management (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-2416 and fix it if it is affected.

What it is: CVE-2018-2416 is a medium-severity vulnerability in SAP Identity Management, published on 9 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-2416 in the wild and no public exploit code.

Affected product: SAP Identity Management. 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-2018-2416/ (Markdown: https://insights.sbomify.com/CVE-2018-2416/index.md)
```

## Sources

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

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