# CVE-2024-22132: Code Injection vulnerability in SAP IDES Systems

> Attackers can execute arbitrary code in SAP IDES ECC-systems, potentially escalating privileges and controlling system behavior.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **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:** 13 Feb 2024
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-777j-4h5j-qg3c

## What is CVE-2024-22132?

CVE-2024-22132 is a high-severity code injection vulnerability in SAP_SE SAP IDES Systems, published on 13 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP IDES ECC-systems contain code that permits the execution of arbitrary program code of user's choice.An attacker can therefore control the behaviour of the system by executing malicious code which can potentially escalate privileges with low impact on confidentiality, integrity and availability of the system.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2024-22132?

It affects 1 product.


Products: Sap Ides Ecc.

## How do I fix CVE-2024-22132?

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

## Is CVE-2024-22132 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22132 and fix it if it is affected.

What it is: CVE-2024-22132 is a high-severity code injection vulnerability in SAP_SE SAP IDES Systems, published on 13 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22132 in the wild and no public exploit code.

Affected product: SAP_SE SAP IDES Systems. 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-2024-22132/ (Markdown: https://insights.sbomify.com/CVE-2024-22132/index.md)
```

## Sources

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

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