# CVE-2020-6262: Code injection in SAP Application Server ABAP (ST-PI)

> An attacker can inject code into SAP Application Server ABAP via Service Data Download, leading to full system control.

- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/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:** 12 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5m7w-q5h8-8h9j

## What is CVE-2020-6262?

CVE-2020-6262 is a critical code injection vulnerability in SAP Application Server ABAP (ST-PI), published on 12 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Service Data Download in SAP Application Server ABAP (ST-PI, before versions 2008_1_46C, 2008_1_620, 2008_1_640, 2008_1_700, 2008_1_710, 740) allows an attacker to inject code that can be executed by the application. An attacker could thereby control the behavior of the application and the whole ABAP system leading to Code Injection.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2020-6262?

It affects 1 product.


Products: Sap Application Server.

## How do I fix CVE-2020-6262?

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

## Is CVE-2020-6262 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6262 and fix it if it is affected.

What it is: CVE-2020-6262 is a critical code injection vulnerability in SAP Application Server ABAP (ST-PI), published on 12 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6262 in the wild and no public exploit code.

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

## Sources

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

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