CVE-2023-28763
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 · uneditedSAP NetWeaver AS for ABAP and ABAP Platform - versions 740, 750, 751, 752, 753, 754, 755, 756, 757, 791, allows an attacker authenticated as a non-administrative user to craft a request with certain parameters 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 confidenceA resource exhaustion vulnerability in SAP NetWeaver AS for ABAP allows authenticated non-administrative users to craft specific requests that consume excessive server resources, potentially causing denial of service. The attack is network-based and requires no user interaction.
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= 740= 750= 751= 752= 753= 754= 755= 756= 757= 791CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP NetWeaver AS for ABAP versionExecute transaction code SM51 or use the SAP kernel version check (disp+work -v) to retrieve the installed ABAP application server versionAffected if The version number matches 740, 750, 751, 752, 753, 754, 755, 756, 757, or 791
-
Verify network exposure of the ABAP systemReview SAP gateway configuration (SMGW) and ICM (SMICM) to determine if the system accepts external network requests. Check profile parameters icm/server_port_ and gw/accept_remote_procsAffected if The system is accessible from untrusted networks without proper segmentation or filtering
-
Monitor for abnormal resource consumptionUse transaction SM37 or SM66 to review job and process resource usage. Look for jobs with unusually high CPU or memory consumption, particularly those run by non-administrative usersAffected if High resource consumption is observed from processes initiated by non-privileged users that cannot be explained by normal business activity
-
Review security audit log for suspicious request patternsExecute transaction SM20 or review the security audit log (secudit) for repeated requests from authenticated non-administrative users that may indicate resource exhaustion attemptsAffected if Repeated requests from low-privileged users are logged that target specific transactions or RFC-enabled modules with high frequency
You are affected if your installed SAP NetWeaver AS ABAP version matches 740, 750, 751, 752, 753, 754, 755, 756, 757, or 791 and the system is exposed to network traffic where resource exhaustion attempts could be performed.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the relevant SAP Security Note/patch for CVE-2023-28763 to address the resource consumption issue. Consider implementing network-level rate limiting or request throttling as a temporary mitigation.
Upgrade to SAP NetWeaver AS for ABAP version 753 or higher (754, 755, 756, 757, or 791)
- Review the SAP Security Note for CVE-2023-28763 on the SAP Support Portal (launchpad.support.sap.com) to obtain the specific patch or confirm the fixed version
- Plan the upgrade to a patched version (753 or higher) in a non-production system first
- Test custom ABAP code and interfaces for compatibility with the target version
- Schedule maintenance window for production upgrade
- Execute upgrade following SAP standard upgrade procedures
- Verify the patch is applied by checking the kernel version and SAP Note implementation status
- Monitor system resources after deployment to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28763 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-28763 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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