# CVE-2019-0243: Missing authorization in SAP BW/4HANA (DW4CORE)

> An authenticated user can escalate privileges in SAP BW/4HANA due to missing authorization checks during masterdata maintenance.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 8 Jan 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jggg-8pv3-vr9q

## What is CVE-2019-0243?

CVE-2019-0243 is a high-severity missing authorization vulnerability in SAP BW/4HANA (DW4CORE), published on 8 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Under some circumstances, masterdata maintenance in SAP BW/4HANA (fixed in DW4CORE version 1.0 (SP08)) does not perform necessary authorization checks for an authenticated user, resulting in escalation of privileges.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Sap Bw\/4hana.

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

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

## Is CVE-2019-0243 being exploited?

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

## Other vulnerabilities in SAP BW/4HANA (DW4CORE)

- [CVE-2024-37176](https://insights.sbomify.com/CVE-2024-37176/): Missing Authorization check in SAP BW/4HANA Transformation and DTP (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0243 is a high-severity missing authorization vulnerability in SAP BW/4HANA (DW4CORE), published on 8 Jan 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-0243 in the wild and no public exploit code.

Affected product: SAP BW/4HANA (DW4CORE). 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-0243/ (Markdown: https://insights.sbomify.com/CVE-2019-0243/index.md)
```

## Sources

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

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