CVE-2022-22532

9.8 CRITICAL

📋 TL;DR

CVE-2022-22532 is a critical memory corruption vulnerability in SAP NetWeaver Application Server Java that allows unauthenticated attackers to execute arbitrary code via crafted HTTP requests. This could lead to complete system compromise, session hijacking, and impersonation attacks. Affected systems include SAP NetWeaver Java servers running vulnerable kernel versions.

💻 Affected Systems

Products:
  • SAP NetWeaver Application Server Java
Versions: KRNL64NUC 7.22, 7.22EXT, 7.49; KRNL64UC 7.22, 7.22EXT, 7.49, 7.53; KERNEL 7.22, 7.49, 7.53
Operating Systems: All platforms running affected SAP NetWeaver versions
Default Config Vulnerable: ⚠️ Yes
Notes: All SAP NetWeaver Java installations with affected kernel versions are vulnerable by default. No special configuration required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system takeover with administrative privileges, enabling data theft, ransomware deployment, and persistent backdoor installation across the SAP environment.

🟠

Likely Case

Session hijacking leading to unauthorized access to sensitive business data, privilege escalation within SAP systems, and lateral movement to connected systems.

🟢

If Mitigated

Limited impact with proper network segmentation and strong authentication controls, though system availability could still be affected.

🌐 Internet-Facing: HIGH - Unauthenticated remote exploitation makes internet-facing SAP systems extremely vulnerable to automated attacks.
🏢 Internal Only: HIGH - Even internally, unauthenticated exploitation allows attackers with network access to compromise systems without credentials.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The vulnerability requires sending crafted HTTP requests but doesn't need authentication, making exploitation straightforward for attackers with network access.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply SAP Security Note 3123427 patches for respective kernel versions

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

Restart Required: Yes

Instructions:

1. Download and apply SAP Security Note 3123427 patches from SAP Support Portal. 2. Apply kernel patches to all affected SAP NetWeaver Java instances. 3. Restart SAP systems to activate the fixes. 4. Verify patch application using transaction ST-PI.

🔧 Temporary Workarounds

Network Segmentation

all

Restrict network access to SAP NetWeaver Java instances to only trusted sources

firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="TRUSTED_IP_RANGE" port protocol="tcp" port="HTTP_PORT" accept'
netsh advfirewall firewall add rule name="SAP_HTTP_Restrict" dir=in action=allow protocol=TCP localport=HTTP_PORT remoteip=TRUSTED_IP_RANGE

SAP Router Protection

all

Ensure SAP Router is properly configured and updated to filter malicious requests

saprouter -r SAPROUTTAB -G "P TRUSTED_HOST,TRUSTED_PORT,*"
Verify saprouter version is current and security parameters are set

🧯 If You Can't Patch

  • Implement strict network access controls to limit HTTP access to SAP systems only from trusted sources
  • Deploy web application firewall (WAF) with specific rules to detect and block exploitation attempts

🔍 How to Verify

Check if Vulnerable:

Check kernel version using transaction ST-PI or SM51. Compare against affected versions: KRNL64NUC 7.22, 7.22EXT, 7.49; KRNL64UC 7.22, 7.22EXT, 7.49, 7.53; KERNEL 7.22, 7.49, 7.53

Check Version:

In SAP GUI: Execute transaction ST-PI or SM51 to view kernel version and patch level

Verify Fix Applied:

Verify SAP Security Note 3123427 is applied using transaction SNOTE or by checking kernel patch level in ST-PI

📡 Detection & Monitoring

Log Indicators:

  • Unusual HTTP requests to SAP Java server endpoints
  • Memory access violations in system logs
  • Unexpected process creation from SAP Java processes

Network Indicators:

  • HTTP requests with unusual headers or payloads to SAP ports (typically 8000, 50000+)
  • Multiple failed exploitation attempts from single sources

SIEM Query:

source="sap_java_logs" AND (http_request contains "malicious_pattern" OR error_code="MEMORY_VIOLATION")

🔗 References

📤 Share & Export