dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2023-27269

CRITICAL · 9.6 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 →
100/100
Remediation priority · Urgent
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, allows an attacker with non-administrative authorizations to exploit a directory traversal flaw in an available service to overwrite the system files.  In this attack, no data can be read but potentially critical OS files can be overwritten making the system unavailable.

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 · high confidence

This is a directory traversal vulnerability in SAP NetWeaver Application Server for ABAP that allows authenticated non-administrative users to overwrite critical operating system files by manipulating file paths in an exposed service. The flaw enables complete system unavailability through file overwrite attacks, though it does not permit reading sensitive data.

MitigationApply the relevant SAP security patch for affected versions and implement strict input validation on file path parameters within the vulnerable service to prevent directory traversal sequences.

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
Changed
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/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. Verify SAP NetWeaver AS ABAP version
    Execute transaction SM51 and note the kernel version, or use transaction SAINT/SPAM to view installed support packages. Alternatively, check System > Status from the SAP menu to view the SAP Release and kernel version.
    Affected if The installed version matches one of the affected releases: 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, or 756.
  2. Identify exposed ICF file services
    Use transaction SICF (Internet Communication Framework) to list active services. Look for services under /sap/public/bc or similar paths that handle file upload, download, or file path parameters.
    Affected if File-related ICF services are active and accessible via HTTP/HTTPS without additional restrictions.
  3. Review ICF service authorization configuration
    In transaction SICF, select each file-related service and double-click to view the 'Handler List' and 'Logon Data' tabs. Check whether the service allows authenticated non-administrative (non-SAP_ALL) users.
    Affected if Non-administrative users have execute permission on exposed file-handling ICF services.
  4. Check for directory traversal patterns in security logs
    Use transaction SM37 or SLG1 (Object: BC_XSS_STRING_SCAN or security-related audit logs) to review logs for patterns containing '../' or '..\' in file path parameters within the last 30 days.
    Affected if Recent logs show directory traversal attempts or unusual file path parameters being processed by ABAP services.

Your environment is affected if you run any of the listed SAP NetWeaver AS ABAP versions (700-756) and have exposed ICF services that allow authenticated non-administrative users to manipulate file paths.

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 the relevant SAP security patch for affected versions and implement strict input validation on file path parameters within the vulnerable service to prevent directory traversal sequences.

Recommended fix Moderate confidence
  1. 1. Access the SAP ONE Support Launchpad (launchpad.support.sap.com) and search for the relevant security note for CVE-2023-27269
  2. 2. Identify the SAP Note number (typically a Security Note) that addresses this path traversal vulnerability
  3. 3. Review the SAP Note to determine the applicable corrections and prerequisites
  4. 4. Implement the corrections as outlined in the SAP Note - this may involve applying a kernel update, patches, or configuration changes
  5. 5. After applying the patch, verify the vulnerability is remediated by testing the affected service
  6. 6. Ensure proper authorization controls are in place as recommended by the SAP Note

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

Fix this in Netweaver Application Server Abap Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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