dbcve.org
NetweaverApplication · Sap

CVE-2022-28772

HIGH · 7.5 CVSS v3.1 Published 2022-04-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
By overlong input values an attacker may force overwrite of the internal program stack in SAP Web Dispatcher - versions 7.53, 7.77, 7.81, 7.85, 7.86, or Internet Communication Manager - versions KRNL64NUC 7.22, 7.22EXT, 7.49, KRNL64UC 7.22, 7.22EXT, 7.49, 7.53, KERNEL 7.22, 7.49, 7.53, 7.77, 7.81, 7.85, 7.86, which makes these programs unavailable, leading to denial of service.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This vulnerability in SAP Web Dispatcher and Internet Communication Manager allows attackers to overwrite the internal program stack by sending overlong input values. This stack manipulation leads to program unavailability, causing a denial of service condition.

MitigationApply the relevant SAP security patches for the affected Web Dispatcher and Internet Communication Manager versions. Implement input validation and length checks on incoming requests as a compensating control until patches can be deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NetweaverApplication
Affected:= 7.22ext= 7.49= 7.53= 7.77= 7.81= 7.85= 7.86= kernel_7.22= krnl64nuc_7.22= krnl64uc_7.22
Web DispatcherApplication
Affected:= 7.53= 7.77= 7.81= 7.85= 7.86

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if SAP Web Dispatcher is installed
    Check your system for SAP Web Dispatcher components. Common locations include /usr/sap, /sapmnt, or look for processes named 'wd' or 'sapwebdisp'. On Windows, check services for SAP Web Dispatcher.
    Affected if SAP Web Dispatcher version 7.53, 7.77, 7.81, 7.85, or 7.86 is installed
  2. Identify if Internet Communication Manager is installed
    Check for ICM process (sapcontrol -function GetProcessList or similar). ICM is part of SAP NetWeaver ABAP or Java stack. Look for the SAP kernel components.
    Affected if SAP NetWeaver kernel versions 7.22, 7.49, 7.53, 7.77, 7.81, 7.85, or 7.86 are running
  3. Determine installed version of Web Dispatcher
    Run: sapwebdisp -v or check version via SAPMMC if on Windows. Alternatively, check the SAP note or patch level applied to the Web Dispatcher installation directory.
    Affected if Version matches 7.53, 7.77, 7.81, 7.85, or 7.86 exactly
  4. Determine installed kernel version for ICM
    Execute: disp+work -v or sapkernel -v from the kernel directory. Check the SAP kernel version file or use transaction SM51 to view kernel release information.
    Affected if Kernel version equals 7.22ext, 7.49, 7.53, 7.77, 7.81, 7.85, 7.86, kernel_7.22, krnl64nuc_7.22, or krnl64uc_7.22
  5. Verify component is network exposed
    Check configuration files (icm filter rules, icm/HTTP/... parameters in default.pfl or instance profile) to determine if HTTP/HTTPS ports are open and accessible. Review SAP Web Dispatcher administration ports.
    Affected if The Web Dispatcher or ICM HTTP ports are reachable from network and component version is in affected list

You are affected if SAP Web Dispatcher or Internet Communication Manager with a version matching the exact numbers listed (7.53, 7.77, 7.81, 7.85, 7.86 for Web Dispatcher or 7.22ext/7.49/7.53/7.77/7.81/7.85/7.86/kernel_7.22/krnl64nuc_7.22/krnl64uc_7.22 for NetWeaver kernel) is installed and exposed to network requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security patches for the affected Web Dispatcher and Internet Communication Manager versions. Implement input validation and length checks on incoming requests as a compensating control until patches can be deployed.

Recommended fix Moderate confidence

SAP Kernel 7.86 or later for kernel; SAP Web Dispatcher 7.86 or later - obtain specific patched versions from SAP Security Note 3222097

  1. 1. Identify the exact SAP NetWeaver Kernel version currently running using transaction SM51 or by checking the executable version
  2. 2. Identify the exact SAP Web Dispatcher version using the web administration interface (SAP_MITS) or command line: disp+work -v
  3. 3. Access the SAP Support Portal (launchpad.support.sap.com) and navigate to the SAP Security Notes for CVE-2022-28772
  4. 4. Download the appropriate kernel patch for your specific version (7.22, 7.22EXT, 7.49, 7.53, 7.77, 7.81, 7.85, or 7.86)
  5. 5. For Web Dispatcher, download and apply the patch for versions 7.53, 7.77, 7.81, 7.85, or 7.86
  6. 6. Apply the kernel patch following standard SAP kernel update procedures - stop the SAP system, replace the kernel executables, restart
  7. 7. For Web Dispatcher, replace the disp+work executable and related components, then restart the Web Dispatcher
  8. 8. Verify the patch was applied correctly by checking the version again and monitoring for stability
Caveat Kernel patches should be applied in a maintenance window with system downtime; test thoroughly in development/QA before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Netweaver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28772 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-28772 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data