dbcve.org
Netweaver AbapApplication · Sap

CVE-2022-22543

HIGH · 7.5 CVSS v3.1 Published 2022-02-09
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
SAP NetWeaver Application Server for ABAP (Kernel) and ABAP Platform (Kernel) - versions KERNEL 7.22, 8.04, 7.49, 7.53, 7.77, 7.81, 7.85, 7.86, 7.87, KRNL64UC 8.04, 7.22, 7.22EXT, 7.49, 7.53, KRNL64NUC 7.22, 7.22EXT, 7.49, does not sufficiently validate sap-passport information, which could lead to a Denial-of-Service attack. This allows an unauthorized remote user to provoke a breakdown of the SAP Web Dispatcher or Kernel work process. The crashed process can be restarted immediately, other processes are not affected.

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 · high confidence

A denial-of-service vulnerability exists in SAP NetWeaver Application Server for ABAP and ABAP Platform kernels where insufficient validation of sap-passport data allows unauthenticated remote attackers to crash the SAP Web Dispatcher or kernel work processes by sending specially crafted requests.

MitigationApply the relevant SAP Security Notes to update the affected kernel versions to patched releases, and ensure monitoring is in place for process restarts.

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
Netweaver AbapApplication
Affected:= 7.22= 7.22ext= 7.49= 7.53= 7.77= 7.81= 7.85= 7.86= 7.87= 8.04= krnl64nuc_7.22= krnl64nuc_8.04
Netweaver As AbapApplication
Affected:= 7.22= 7.22ext= 7.49= 7.53= 7.77= 7.81= 7.85= 7.86= 7.87= 8.04= krnl64nuc_7.22= krnl64nuc_8.04

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 the SAP kernel version
    Execute 'SAPCAR -tvf <kernel_archive>' or check the kernel executable version using 'disp+work -v' or 'gwrd' in the kernel directory. Also check via SAP transaction SM51 or kernel version display in SAP MII.
    Affected if The kernel version matches 7.22, 7.22ext, 7.49, 7.53, 7.77, 7.81, 7.85, 7.86, 7.87, 8.04, krnl64nuc_7.22, or krnl64nuc_8.04.
  2. Confirm SAP NetWeaver ABAP or AS ABAP is installed
    Verify the product installation by checking transaction SM37 for ABAP work processes, or execute 'SAP kernel' command in theusr/sap/<SID>/SYS/exe/run directory.
    Affected if The system is running SAP NetWeaver ABAP or SAP NetWeaver AS ABAP with any of the affected kernel versions.
  3. Check if Web Dispatcher or network listeners are active
    Review SAP transaction SMICM (ICM Monitor) for Web Dispatcher status, or check process list for disp+work processes listening on network ports (typically 32XX, 80, 443, 8000, 50000).
    Affected if The Web Dispatcher or ABAP work processes are exposed on network interfaces accessible to attackers.
  4. Verify sap-passport processing is enabled
    Check ICM profile parameters ICM/ sapmpc and profile parameters related to sap-passport validation in default.pfl or instance profiles. Use transaction RZ11 to view current ICM parameters.
    Affected if sap-passport handling is enabled in the ICM configuration, which is the default behavior for HTTP request processing.
  5. Review recent process crashes or restarts
    Check SAP transaction SM37 for abnormal work process terminations, review system logs via transaction SM21, and check operating system logs for disp+work or sapwebdisp process failures.
    Affected if There are unexplained work process or Web Dispatcher crashes correlating with external network requests.

A user is affected if they run any SAP NetWeaver ABAP or AS ABAP kernel version matching 7.22 through 8.04 (or krnl64nuc variants) with network-accessible work processes or Web Dispatcher that process incoming requests containing sap-passport data.

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 Notes to update the affected kernel versions to patched releases, and ensure monitoring is in place for process restarts.

Fix this in Netweaver Abap Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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