# CVE-2019-0271: XML external entity in ABAP Server

> An attacker can exploit an XML External Entity vulnerability in SAP ABAP Server to read sensitive data or cause denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 12 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gxw2-45rm-hpm8

## What is CVE-2019-0271?

CVE-2019-0271 is a medium-severity vulnerability in SAP SE ABAP Server, published on 12 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ABAP Server (used in NetWeaver and Suite/ERP) and ABAP Platform does not sufficiently validate an XML document accepted from an untrusted source, leading to an XML External Entity (XEE) vulnerability. Fixed in Kernel 7.21 or 7.22, that is ABAP Server 7.00 to 7.31 and Kernel 7.45, 7.49 or 7.53, that is ABAP Server 7.40 to 7.52 or ABAP Platform. For more recent updates please refer to Security Note 2870067 (which supersedes the solution of Security Note 2736825) in the reference section below.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2019-0271?

It affects 3 products.


Products: Sap Advanced Business Application Programming Platform, Sap Advanced Business Application Programming Server, Sap Sap Kernel.

## How do I fix CVE-2019-0271?

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

## Is CVE-2019-0271 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-0271 and fix it if it is affected.

What it is: CVE-2019-0271 is a medium-severity vulnerability in SAP SE ABAP Server, published on 12 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-0271 in the wild and no public exploit code.

Affected product: SAP SE ABAP Server. 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-2019-0271/ (Markdown: https://insights.sbomify.com/CVE-2019-0271/index.md)
```

## Sources

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

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