# CVE-2019-0293: Missing authorization in SAP Solution Manager system (ST-PI)

> Attackers can bypass authorization checks to access sensitive information on RFC destinations in SAP Solution Manager systems.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 14 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mfmp-hpg9-83ch

## What is CVE-2019-0293?

CVE-2019-0293 is a medium-severity missing authorization vulnerability in SAP Solution Manager system (ST-PI), published on 14 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Read of RFC destination does not always perform necessary authorization checks, resulting in escalation of privileges to access information on RFC destinations on managed systems and SAP Solution Manager system (ST-PI, before versions 2008_1_700, 2008_1_710, and 740).

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Sap Sap Solution Manager System.

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

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

## Is CVE-2019-0293 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0293 is a medium-severity missing authorization vulnerability in SAP Solution Manager system (ST-PI), published on 14 May 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-0293 in the wild and no public exploit code.

Affected product: SAP Solution Manager system (ST-PI). 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-0293/ (Markdown: https://insights.sbomify.com/CVE-2019-0293/index.md)
```

## Sources

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

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