dbcve.org
NetweaverApplication · Sap

CVE-2022-28773

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
Due to an uncontrolled recursion in SAP Web Dispatcher and SAP Internet Communication Manager, the application may crash, leading to denial of service, but can be restarted automatically.

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

An uncontrolled recursion vulnerability in SAP Web Dispatcher and SAP Internet Communication Manager allows remote attackers to trigger excessive recursive processing, causing the application to crash and resulting in denial of service. The application has automatic restart capability, allowing recovery but leaving the service intermittently unavailable.

MitigationApply the relevant SAP security patches for CVE-2022-28773. Until patches are available, implement request rate limiting and monitoring to detect and mitigate anomalous request patterns that could trigger the recursion condition.

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 SAP Web Dispatcher installation
    Check for SAP Web Dispatcher by examining the SAP system landscape: look for the Web Dispatcher binary (e.g., disp+work.exe or sapwebdisp) in the SAP installation directory, or query the SAP system for installed software components using SAP LM or the SAP Installation Wizard.
    Affected if SAP Web Dispatcher is installed and running in the environment
  2. Determine Web Dispatcher version
    Execute the command: sapwebdisp -v or disp+work -v, or check the SAP Software Provisioning Manager (SWPM) for installed component versions. The version is typically displayed in the output or found in the SAP Web Dispatcher parameter file (default: sapwebdisp.pfl).
    Affected if The installed version matches any of the following: 7.53, 7.77, 7.81, 7.85, or 7.86
  3. Identify SAP NetWeaver kernel version
    Execute the command: disp+work -version or check the kernel version via SAP transaction SM51, or inspect the kernel directory for version information files.
    Affected if The kernel version matches any of the following: 7.22ext, 7.49, 7.53, 7.77, 7.81, 7.85, 7.86, kernel_7.22, krnl64nuc_7.22, or krnl64uc_7.22
  4. Verify ICM service status and exposure
    Check if the Internet Communication Manager (ICM) is running by executing transaction SMICM or by checking the ICM process (icman) in the operating system process list. Determine if the ICM is exposed to untrusted networks by reviewing ICM configuration parameters (icm/host_name, icm/port).
    Affected if The ICM service is running and exposed to external network requests without proper request rate limiting in place

The environment is affected if SAP Web Dispatcher (versions 7.53, 7.77, 7.81, 7.85, 7.86) or SAP NetWeaver kernel (versions 7.22ext, 7.49, 7.53, 7.77, 7.81, 7.85, 7.86, kernel_7.22, krnl64nuc_7.22, krnl64uc_7.22) with ICM is running and exposed to network traffic.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security patches for CVE-2022-28773. Until patches are available, implement request rate limiting and monitoring to detect and mitigate anomalous request patterns that could trigger the recursion condition.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28773 — 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-28773 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