# CVE-2022-22536: SAP Multiple Products HTTP Request Smuggling

> Unauthenticated attackers can perform request smuggling to impersonate victims and poison caches, leading to system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 18 Aug 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-6hc3-539h-6xc6

## What is CVE-2022-22536?

CVE-2022-22536 is a critical vulnerability in Sap Netweaver Application Server Abap, published on 9 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SAP NetWeaver Application Server ABAP, SAP NetWeaver Application Server Java, ABAP Platform, SAP Content Server 7.53 and SAP Web Dispatcher are vulnerable for request smuggling and request concatenation. An unauthenticated attacker can prepend a victim's request with arbitrary data. This way, the attacker can execute functions impersonating the victim or poison intermediary Web caches. A successful attack could result in complete compromise of Confidentiality, Integrity and Availability of the system.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2022-22536?

It affects 3 products.


Products: Sap Content Server, Sap Netweaver Application Server Abap, Sap Web Dispatcher.

## How do I fix CVE-2022-22536?

No fix has been published for CVE-2022-22536 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 8 Sep 2022.

## Is CVE-2022-22536 being exploited?

Yes. Attackers have exploited CVE-2022-22536 in the wild since at least 18 Aug 2022.

Public exploit code:

- SAP memory pipes(MPI)  desynchronization vulnerability CVE-2022-22536. (github_poc): https://github.com/ZZ-SOCMAP/CVE-2022-22536
- https://github.com/tess-ss/SAP-memory-pipes-desynchronization-vulnerability-MPI-CVE-2022-22536 (github_poc): https://github.com/tess-ss/SAP-memory-pipes-desynchronization-vulnerability-MPI-CVE-2022-22536
- SAPGateBreaker is a PoC exploit for CVE-2022-22536, a critical HTTP Request Smuggling vulnerability in SAP NetWeaver. It demonstrates how to bypass ACLs by desynchronizing request parsing between ICM and backend services using crafted Content-Length-based payloads. (github_poc): https://github.com/BecodoExploit-mrCAT/SAPGateBreaker-Exploit
- SAP NetWeaver - 7.53 - HTTP Request Smuggling (exploitdb)
- Fast, socket-level scanner for detecting CVE-2022-22536 in SAP ICM or Web Dispatcher instances. Performs request smuggling tests with a crafted MPI-desync payload. Supports batch scanning IP:PORT targets via plain text files. (github_poc): https://github.com/abrewer251/CVE-2022-22536_SAP_Request_Smuggling_Scanner
- SAP Memory Pipes (MPI) Desynchronization (nuclei): http/cves/2022/CVE-2022-22536.yaml

## Other vulnerabilities in Sap Netweaver Application Server Abap

- [CVE-2024-33005](https://insights.sbomify.com/CVE-2024-33005/): Missing authorization in SAP NetWeaver Application Server (ABAP and Java),SAP Web Dispatcher and SAP Content Server (medium 6.3)
- [CVE-2023-26457](https://insights.sbomify.com/CVE-2023-26457/): Cross-Site Scripting (XSS) vulnerability in SAP Content Server (medium 6.1)
- [CVE-2015-4157](https://insights.sbomify.com/CVE-2015-4157/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22536 and fix it if it is affected.

What it is: CVE-2022-22536 is a critical vulnerability in Sap Netweaver Application Server Abap, published on 9 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-22536 in the wild since at least 18 Aug 2022.

Affected product: Sap Netweaver Application Server Abap. 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-2022-22536/ (Markdown: https://insights.sbomify.com/CVE-2022-22536/index.md)
```

## Sources

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

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