CVE-2022-22536

10.0 CRITICAL

📋 TL;DR

CVE-2022-22536 is a critical HTTP request smuggling vulnerability in multiple SAP components that allows unauthenticated attackers to prepend malicious data to legitimate user requests. This enables impersonation attacks, cache poisoning, and potential complete system compromise. Affected systems include SAP NetWeaver Application Server ABAP/Java, ABAP Platform, SAP Content Server 7.53, and SAP Web Dispatcher.

💻 Affected Systems

Products:
  • SAP NetWeaver Application Server ABAP
  • SAP NetWeaver Application Server Java
  • ABAP Platform
  • SAP Content Server 7.53
  • SAP Web Dispatcher
Versions: Multiple versions - check SAP notes for specific affected versions
Operating Systems: All supported OS platforms
Default Config Vulnerable: ⚠️ Yes
Notes: All standard configurations are vulnerable; no special configuration required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise allowing attackers to execute arbitrary code, access sensitive data, and disrupt business operations.

🟠

Likely Case

Attackers impersonating legitimate users to perform unauthorized actions, steal sensitive data, and poison web caches.

🟢

If Mitigated

Limited impact with proper network segmentation, WAF protection, and monitoring in place.

🌐 Internet-Facing: HIGH - Directly exploitable over HTTP/HTTPS without authentication.
🏢 Internal Only: HIGH - Exploitable from internal networks if systems are accessible.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: CONFIRMED
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation is straightforward and has been observed in the wild. CISA has added this to its Known Exploited Vulnerabilities catalog.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply SAP Security Note 3123396

Vendor Advisory: https://launchpad.support.sap.com/#/notes/3123396

Restart Required: Yes

Instructions:

1. Download and apply SAP Security Note 3123396. 2. Restart affected SAP systems. 3. Verify the patch is applied correctly.

🔧 Temporary Workarounds

Web Application Firewall (WAF) Rules

all

Implement WAF rules to detect and block HTTP request smuggling attempts

Configure WAF to validate HTTP request headers and reject malformed requests

Network Segmentation

all

Restrict access to SAP systems to only trusted networks

Implement firewall rules to limit inbound connections to SAP ports

🧯 If You Can't Patch

  • Implement strict network segmentation and isolate SAP systems from untrusted networks
  • Deploy a Web Application Firewall (WAF) with specific rules to detect and block HTTP request smuggling patterns

🔍 How to Verify

Check if Vulnerable:

Check if SAP Security Note 3123396 is applied in your system using transaction SNOTE

Check Version:

Use SAP transaction SM51 or SM50 to check system information

Verify Fix Applied:

Verify SAP Security Note 3123396 is successfully implemented and system has been restarted

📡 Detection & Monitoring

Log Indicators:

  • Unusual HTTP request patterns
  • Multiple requests from single source with malformed headers
  • Cache poisoning attempts in web server logs

Network Indicators:

  • HTTP requests with conflicting Content-Length and Transfer-Encoding headers
  • Requests that appear to contain multiple HTTP requests

SIEM Query:

Search for HTTP requests with suspicious header combinations or request smuggling patterns in web server logs

🔗 References

📤 Share & Export