dbcve.org
Web DispatcherApplication · Sap

CVE-2023-35871

CRITICAL · 9.4 CVSS v3.1 Published 2023-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The SAP Web Dispatcher - versions WEBDISP 7.53, WEBDISP 7.54, WEBDISP 7.77, WEBDISP 7.85, WEBDISP 7.89, WEBDISP 7.91, WEBDISP 7.92, WEBDISP 7.93, KERNEL 7.53, KERNEL 7.54 KERNEL 7.77, KERNEL 7.85, KERNEL 7.89, KERNEL 7.91, KERNEL 7.92, KERNEL 7.93, KRNL64UC 7.53, HDB 2.00, XS_ADVANCED_RUNTIME 1.00, SAP_EXTENDED_APP_SERVICES 1, has a vulnerability that can be exploited by an unauthenticated attacker to cause memory corruption through logical errors in memory management this may leads to information disclosure or system crashes, which can have low impact on confidentiality and high impact on the integrity and availability of the system.

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

Memory corruption vulnerability in SAP Web Dispatcher (versions 7.53-7.93 and related kernel/extended services) allowing unauthenticated attackers to exploit logical errors in memory management, potentially causing information disclosure or system crashes.

MitigationApply SAP security patches for the affected Web Dispatcher and kernel versions; review SAP Security Notes for CVE-2023-35871. Given the critical CVSS score (9.4) and unauthenticated attack vector, prioritize immediate patching.

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
Web DispatcherApplication
Affected:= 7.53= 7.54= 7.77= 7.85= 7.89= 7.91= 7.92= 7.93= hdb_2.00= kernel_7.53= kernel_7.54= kernel_7.77

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
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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 for SAP Web Dispatcher installation directories (typically under /usr/sap or the SAP system root) or look for processes named 'webdisp' or 'wd' running on the system
    Affected if No SAP Web Dispatcher installation is found, the system is not affected by this CVE
  2. Determine the installed Web Dispatcher version
    Locate the SAP Web Dispatcher version information - check version files in the installation directory (such as a version info file or executable version output)
    Affected if The installed version matches one of the affected versions: 7.53, 7.54, 7.77, 7.85, 7.89, 7.91, 7.92, or 7.93
  3. Check for SAP kernel or HDB versions if Web Dispatcher version does not match
    If the main Web Dispatcher version is not in the affected list, check the bundled or associated kernel and HDB versions installed with the Web Dispatcher (versions hdb_2.00, kernel_7.53, kernel_7.54, kernel_7.77 are also affected)
    Affected if The associated kernel or HDB version matches any of the affected versions listed in the CVE
  4. Verify if the Web Dispatcher is network-accessible
    Check the SAP Web Dispatcher configuration (icm/HTTP ports in the instance profile or icmfilter) and determine if HTTP/HTTPS ports are exposed to unauthenticated network access
    Affected if The Web Dispatcher HTTP/HTTPS ports are exposed to unauthenticated network users, enabling the unauthenticated attack vector described in the CVE

A system is affected if it has SAP Web Dispatcher installed with a version matching 7.53, 7.54, 7.77, 7.85, 7.89, 7.91, 7.92, 7.93, or with associated kernel/hdb versions hdb_2.00, kernel_7.53, kernel_7.54, kernel_7.77, and the service is network-accessible to unauthenticated users.

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 SAP security patches for the affected Web Dispatcher and kernel versions; review SAP Security Notes for CVE-2023-35871. Given the critical CVSS score (9.4) and unauthenticated attack vector, prioritize immediate patching.

Recommended fix High confidence

SAP Web Dispatcher 7.89, 7.91, 7.92, or 7.93 (depending on your release cadence; 7.93 is the latest stable release in the 7.x line)

  1. 1. Identify the current SAP Web Dispatcher version by checking the SAP management console or using the SAP ICM administration tools.
  2. 2. Download the latest SAP Web Dispatcher version from the SAP Support Portal (support.sap.com) - SAP notes this vulnerability is fixed in versions 7.89, 7.91, 7.92, and 7.93 depending on your release line.
  3. 3. Schedule a maintenance window and backup the current SAP Web Dispatcher configuration files (especially the worker profile and any custom icm filter rules).
  4. 4. Install the patched Web Dispatcher version using SAP's standard installation or update procedures (SAPinst).
  5. 5. Verify the upgrade by checking the version via the ICM admin page or command line tools (e.g., icmon or sapcontrol).
  6. 6. Test critical application workflows through the Web Dispatcher to ensure proper routing and functionality.
Caveat Review SAP notes for version-specific changes; minor configuration adjustments may be needed for new features, but this is a security patch with minimal breaking change risk

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

Fix this in Web Dispatcher 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-2023-35871 — 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-2023-35871 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