# CVE-2020-26808: Code injection in SAP AS ABAP(DMIS)

> An authenticated attacker can inject arbitrary code into SAP DMIS function modules, leading to code execution and compromising application confidentiality, integrity, and availability.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-49f8-w2xp-h8gq

## What is CVE-2020-26808?

CVE-2020-26808 is a critical code injection vulnerability in SAP AS ABAP(DMIS), published on 10 Nov 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SAP AS ABAP(DMIS), versions - 2011_1_620, 2011_1_640, 2011_1_700, 2011_1_710, 2011_1_730, 2011_1_731, 2011_1_752, 2020 and SAP S4 HANA(DMIS), versions - 101, 102, 103, 104, 105, allows an authenticated attacker to inject arbitrary code into function module leading to code injection that can be executed in the application which affects the confidentiality, availability and integrity of the application.

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

It affects 2 products.


Products: Sap Sap as Abap\(dmis\), Sap Sap S4 Hana\(dmis\).

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

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

## Is CVE-2020-26808 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-26808 is a critical code injection vulnerability in SAP AS ABAP(DMIS), published on 10 Nov 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-26808 in the wild and no public exploit code.

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

## Sources

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

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