dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2023-25618

MEDIUM · 6.5 CVSS v3.1 Published 2023-03-14
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 Application Server for ABAP and ABAP Platform - versions 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756, 757, 791, has multiple vulnerabilities in an unused class for error handling in which an attacker authenticated as a non-administrative user can craft a request with certain parameters which will consume the server's resources sufficiently to make it unavailable. There is no ability to view or modify any information.

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 vulnerability in SAP NetWeaver ABAP where an authenticated non-administrative user can send specially crafted requests to an unused error handling class, causing excessive resource consumption that makes the server unavailable. The attack does not provide any ability to view or modify data.

MitigationDisable or remove the unused error handling class referenced in the vulnerability, and apply SAP security notes/patches for the affected versions.

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 AbapApplication
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. Identify SAP NetWeaver ABAP version
    Execute transaction code SM51 in the SAP GUI to display the system version, or use command 'sapcontrol -nr <instance> -function GetSystemInstanceList' to retrieve version information
    Affected if The displayed version matches any of the following: 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, or 756
  2. Confirm ABAP application server is running
    Check via transaction code SM51 or transaction code SM37 (background job monitoring) to verify the SAP system instances are active
    Affected if The ABAP application server is online and responsive, making the DoS condition possible when exploited
  3. Verify authentication is enabled for non-administrative users
    Review user access via transaction code SU01 (user maintenance) or transaction code SARFC (RFC authority checks) to confirm non-admin users have system access
    Affected if Authenticated non-administrative users exist in the system, as the vulnerability requires an authenticated user to send the malicious requests
  4. Monitor for excessive resource consumption
    Check transaction code ST03N (performance monitoring) or transaction code DB02 (database performance) for unusual spikes in CPU or memory usage, and review transaction code SM37 for stuck background jobs
    Affected if The system shows abnormally high resource consumption that cannot be explained by normal workloads, indicating potential exploitation
  5. Review SAP security notes applied
    Execute transaction code SNOTE or check SAP Solution Manager for applied security patches. Search for notes related to CVE-2023-25618
    Affected if No SAP security patches for this CVE have been applied, leaving the vulnerability open

If your SAP NetWeaver ABAP version is one of the affected versions (700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, or 756) and the system is running with authenticated users, you may be affected by this DoS vulnerability.

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

Disable or remove the unused error handling class referenced in the vulnerability, and apply SAP security notes/patches for the affected versions.

Fix this in Netweaver Application Server Abap Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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