Security readout for executives and security teams
Plain-English summary
This vulnerability lets an unauthenticated attacker confuse how SAP front-end components parse HTTP requests. If successful, the attacker may attach malicious data to a victim’s request, act as that victim, poison web caches, and compromise sensitive SAP systems.
Executive priority
Treat as urgent for any exposed SAP environment. The issue is critical, remotely reachable, unauthenticated, and listed by CISA as known exploited. Prioritize identifying affected SAP systems and applying SAP’s vendor guidance.
Technical view
CVE-2022-22536 is a CWE-444 request smuggling and request concatenation flaw affecting listed SAP NetWeaver AS ABAP/Java, ABAP Platform, SAP Content Server 7.53, and SAP Web Dispatcher versions. The CVSS 3.1 score is 9.8, with network access, low complexity, no privileges, and no user interaction required.
Likely exposure
Exposure is most likely where affected SAP Web Dispatcher, SAP Content Server 7.53, NetWeaver, or ABAP Platform versions handle HTTP traffic, especially internet-facing or proxy-fronted SAP environments. The provided data does not identify specific deployment configurations beyond the named products and versions.
Exploitation context
CISA lists CVE-2022-22536 in its Known Exploited Vulnerabilities catalog, so active exploitation is supported by the provided sources. The bundle does not provide exploit details, exploit volume, or named threat actors.
Researcher notes
Evidence supports severe request desynchronization risk, but the source bundle does not include patch mechanics or safe detection artifacts. Validation should focus on version exposure, SAP note application status, and architecture review rather than active probing.
Mitigation direction
- Review SAP Note 3123396 and SAP’s February 2022 security guidance.
- Prioritize remediation for internet-facing SAP HTTP endpoints and Web Dispatcher deployments.
- Inventory listed SAP products and kernel versions across production and disaster recovery.
- Restrict external access where possible until vendor guidance is applied.
- Review intermediary cache and proxy exposure for SAP request handling paths.
Validation and detection
- Confirm whether listed SAP product versions are present in the environment.
- Verify SAP Note 3123396 guidance has been applied to each affected system.
- Check CISA KEV tracking for mandated remediation timelines if applicable.
- Review SAP HTTP ingress paths, Web Dispatcher placement, and cache layers.
- Look for unusual authenticated actions or cache anomalies around SAP endpoints.
Public sources used
Michael Williams reviewed this cited source version on .
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-444: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-22536 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://launchpad.support.sap.com/#/notes/3123396CVE reference · x_refsource_MISC
- https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.htmlCVE reference · x_refsource_MISC
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-22536CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.