dbcve.org
Netweaver Application Server JavaApplication · Sap

CVE-2022-22533

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
Due to improper error handling in 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, an attacker could submit multiple HTTP server requests resulting in errors, such that it consumes the memory buffer. This could result in system shutdown rendering the system unavailable.

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

In SAP NetWeaver Application Server Java, improper error handling allows an attacker to submit multiple HTTP server requests that generate errors, causing memory buffer exhaustion and ultimately system shutdown, rendering the system unavailable. This is a denial-of-service vulnerability exploitable over the network.

MitigationApply the relevant SAP security patch for this vulnerability and upgrade to a supported kernel version. Implement network-level rate limiting or Web Application Firewall rules to mitigate rapid request flooding attempts.

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 Application Server JavaApplication
Affected:= 7.22= 7.49= 7.53= krnl64nuc_7.22= krnl64nuc_7.22ext= krnl64nuc_7.49= krnl64uc_7.22= krnl64uc_7.22ext= krnl64uc_7.49

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. Confirm SAP NetWeaver AS Java is running
    Identify Java processes related to SAP: check for Java processes with SAP-related names, or query the SAP OS abstraction layer using 'sapcontrol -nr <instance> -function GetProcessList' if sapcontrol is available
    Affected if No SAP NetWeaver Java processes are found (not affected)
  2. Determine Java kernel version
    Query the SAP kernel version: use 'sapcontrol -nr <instance> -function GetVersionInfo' or check the kernel version file in the /sapmnt/<SID>/exe directory, or use SAP LM NWA to view system information
    Affected if The installed Java kernel version matches exactly: 7.22, 7.49, 7.53, krnl64nuc_7.22, krnl64nuc_7.22ext, krnl64nuc_7.49, krnl64uc_7.22, krnl64uc_7.22ext, or krnl64uc_7.49
  3. Verify HTTP service is enabled
    Check if SAP HTTP provider is active: query ICM (Internet Communication Manager) status via 'sapcontrol -nr <instance> -function GetProcessList' or check ICM configuration in the SAP system profile (parameter icm/server_port_*)
    Affected if HTTP ports (typically 5xx00) are open and the ICM/HTTP service is active
  4. Review for memory exhaustion indicators
    Monitor Java heap and native memory: use SAP JVM Diagnostics tools, check via 'sapcontrol -nr <instance> -function JvmGetMemoryHeap' or observe OS-level memory consumption for the Java processes
    Affected if Memory usage is abnormally high or continuously increasing without corresponding workload, which may indicate active exploitation

The system is affected if it runs SAP NetWeaver AS Java with a kernel version matching one of the nine specific versions listed AND has HTTP services exposed, making it vulnerable to the memory exhaustion DoS via malformed HTTP 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 patch for this vulnerability and upgrade to a supported kernel version. Implement network-level rate limiting or Web Application Firewall rules to mitigate rapid request flooding attempts.

Recommended fix High confidence

SAP Kernel 7.22 PL600+ or Kernel 7.49 PL500+ (or higher versions such as 7.53, 7.81)

  1. 1. Identify the current SAP Kernel version running on the affected system using transaction SM51 or by checking the executable paths.
  2. 2. Navigate to the SAP Support Portal (support.sap.com) and locate SAP Security Note 3142351 which addresses CVE-2022-22533.
  3. 3. Download the appropriate kernel patch for your platform - for KRNL64NUC/KRNL64UC upgrade to kernel 7.22 patch level 600 or higher, or kernel 7.49 patch level 500 or higher.
  4. 4. Schedule a maintenance window and ensure complete system backup before applying the patch.
  5. 5. Apply the kernel patch following standard SAP kernel update procedures using SAP Kernel Update transaction or manually replacing executable files.
  6. 6. Restart the SAP instance to load the patched kernel components.
  7. 7. Verify the fix by checking the new kernel version (SM51) and monitoring system stability.
Caveat Standard SAP kernel patch - minimal risk but always test in development system first

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

Fix this in Netweaver Application Server Java Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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