dbcve.org
Netweaver Process IntegrationApplication · Sap

CVE-2023-35873

MEDIUM · 6.5 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 →
74/100
Remediation priority · Elevated
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 Runtime Workbench (RWB) of SAP NetWeaver Process Integration - version SAP_XITOOL 7.50, does not perform authentication checks for certain functionalities that require user identity. An unauthenticated user might access technical data about the product status and its configuration. The vulnerability does not allow access to sensitive information or administrative functionalities. On successful exploitation an attacker can cause limited impact on confidentiality and availability of the application.

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

The Runtime Workbench (RWB) in SAP NetWeaver Process Integration version 7.50 (SAP_XITOOL) lacks authentication checks for certain functionalities that should require user identity. An unauthenticated attacker can access technical status and configuration data about the product, but NOT sensitive information or administrative functions. This represents a limited confidentiality and availability impact.

MitigationApply the relevant SAP security note/patch for SAP_XITOOL 7.50 to enforce proper authentication on the affected Runtime Workbench functionalities. Verify that unauthenticated access to technical status and configuration data is no longer possible.

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 Process IntegrationApplication
Affected:= 7.50

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
None
Availability
Low

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

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. Verify SAP NetWeaver PI version
    Check the installed SAP NetWeaver Process Integration version. In SAP system, verify the product version through SAP System Landscape Directory (SLD) or via transaction SM51, or check the SAP_XITOOL component version via transaction SPAM or SAINT. Confirm the version is 7.50.
    Affected if The installed SAP NetWeaver Process Integration version equals 7.50 (specifically SAP_XITOOL version 7.50). Versions outside 7.50 are not affected by this specific CVE.
  2. Confirm Runtime Workbench (RWB) is deployed
    Identify whether the Runtime Workbench component is deployed in the SAP NetWeaver PI environment. Access the SAP NetWeaver Administrator (NWA) or check the PI landscape configuration to determine if RWB is available as part of the installation.
    Affected if RWB is present and accessible in the environment. If RWB is not deployed, this CVE does not apply.
  3. Test unauthenticated RWB access
    Attempt to access the Runtime Workbench URLs without providing any credentials. Common RWB endpoints include: http(s)://<host>:/rep/ and status/monitoring endpoints under the Runtime Workbench context. Try accessing technical status and configuration data views without logging in.
    Affected if Unauthenticated access to technical status and configuration data through RWB is successful without any authentication challenge. This confirms the vulnerability is present.
  4. Verify authentication is enforced on RWB endpoints
    Check the security configuration for the Runtime Workbench in the SAP NetWeaver Application Server Java. Review the security settings via SAP NetWeaver Administrator under Configuration > Security > Application Security, or examine the web.xml and login-config.xml for the RWB application to confirm authentication is required.
    Affected if Authentication is NOT enforced or is missing for the RWB technical status and configuration functionality. The security configuration allows anonymous or unauthenticated access to these functions.

You are affected if you run SAP NetWeaver Process Integration version 7.50 with Runtime Workbench deployed, and unauthenticated access to RWB technical status and configuration data is possible without any login.

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 note/patch for SAP_XITOOL 7.50 to enforce proper authentication on the affected Runtime Workbench functionalities. Verify that unauthenticated access to technical status and configuration data is no longer possible.

Fix this in Netweaver Process Integration Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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