dbcve.org
Netweaver As Abap Business Server PagesApplication · Sap

CVE-2023-29185

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 AS for ABAP (Business Server Pages) - versions 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756, 757, allows an attacker authenticated as a non-administrative user to craft a request with certain parameters in certain circumstances which can consume the server's resources sufficiently to make it unavailable over the network without any user interaction.

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

This is a Denial of Service (DoS) vulnerability in SAP NetWeaver AS for ABAP Business Server Pages where an authenticated non-administrative user can craft specially designed requests with specific parameters that excessively consume server resources, rendering the server unavailable over the network without requiring any user interaction.

MitigationApply the relevant SAP security patch for this vulnerability, implement request rate limiting on affected Business Server Pages, and monitor server resource consumption patterns for anomalous activity.

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 As Abap Business Server PagesApplication
Affected:= 700= 701= 702= 731= 740= 750= 751= 752= 753= 754= 755= 756

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify SAP NetWeaver AS ABAP is installed
    Check the SAP system version by executing transaction SM51 (Server Overview) or checking the kernel version via command 'disp+work -v' or in system profile. Confirm the system is running SAP NetWeaver AS for ABAP.
    Affected if The system is running SAP NetWeaver AS for ABAP.
  2. Confirm the ABAP version falls within the affected range
    Execute transaction SA01 or check via ABAP system information (System > Status). Identify the SAP_BASIS component version and correlate it with the ABAP release version (e.g., 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756).
    Affected if The installed ABAP version matches one of the listed versions: 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, or 756.
  3. Determine if Business Server Pages (BSP) is enabled
    Execute transaction SICF (Define Services) and check for BSP-related services under the /sap/bc/bsp path. Alternatively, use transaction BSP_STATUS to list active BSP applications.
    Affected if BSP is enabled and there are active BSP applications running on the system.
  4. Check for authenticated non-administrative users with BSP access
    Review user access via transaction SUIM (User Information System) or PFCG (Role Maintenance). Identify users with roles that grant access to BSP applications but without administrative privileges (e.g., not SAP_ALL, not with S_DEVELOP for ABAP admin).
    Affected if Non-administrative users exist with permissions to access BSP applications.
  5. Monitor for anomalous BSP request patterns
    Check transaction ST03N (Performance Monitoring) or ST03 (Workload Monitor) for BSP-related requests showing unusually high resource consumption. Review transaction SU01 or logs for repeated BSP request patterns from authenticated users.
    Affected if BSP requests from authenticated non-admin users are consuming excessive server resources.

You are affected if your SAP NetWeaver AS ABAP version is 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, or 756 AND Business Server Pages are enabled AND non-administrative users can submit requests to BSP applications.

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 patch for this vulnerability, implement request rate limiting on affected Business Server Pages, and monitor server resource consumption patterns for anomalous activity.

Fix this in Netweaver As Abap Business Server Pages Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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