dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2023-23859

MEDIUM · 6.1 CVSS v3.1 Published 2023-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 and ABAP Platform - versions 740, 750, 751, 752, 753, 754, 755, 756, 757, 789, 790, allows an unauthenticated attacker to craft a malicious link, which when clicked by an unsuspecting user, can be used to read or modify some sensitive 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 an unauthenticated link injection vulnerability in SAP NetWeaver AS for ABAP that allows attackers to craft malicious URLs which, when clicked by authenticated users, can be used to read or modify sensitive information. The vulnerability requires user interaction (clicking a crafted link) and affects versions 740-790.

MitigationImplement proper authorization checks on all URL parameters and validate incoming requests to prevent manipulation of object references. Apply SAP security notes and ensure CSRF protection is enabled for sensitive operations.

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:= 740= 750= 751= 752= 753= 754= 755= 756= 757= 789= 790

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 installed SAP NetWeaver ABAP version
    Execute transaction SM51 to view server release version, or use transaction SW01 and navigate to System -> System Information. Alternatively, check the SAP kernel version via transaction SK03 or by reviewing the 'sapinst' log files in the usr/sap/<SID>/SYS directory.
    Affected if The displayed version matches 740, 750, 751, 752, 753, 754, 755, 756, 757, 789, or 790.
  2. Verify ICF HTTP services are active
    Execute transaction SICF and check whether the default_root, sap/public, or other public ICF services are set to 'active' status. The HTTP service must be running for URL-based link injection to be possible.
    Affected if ICF services are active and accessible via HTTP/HTTPS without proper filtering.
  3. Check public-facing ICF nodes
    In transaction SICF, expand the tree under 'default_host' and review which services are published. Look particularly at /sap/public and /sap/bc/ directories which handle URL processing.
    Affected if Public ICF nodes are enabled and unauthenticated access is permitted to URL-handling paths.
  4. Review URL parameter authorization checks
    Examine custom ABAP code that processes incoming URL parameters in reports or function modules. Use transaction SE80 to search for direct usage of parameters like '~transaction', '~urlparameter', or custom parameters passed via HTTP requests.
    Affected if The application accepts URL parameters without verifying user authorization or object references.
  5. Confirm user session handling for external links
    Check whether the SAP system implements CSRF tokens for state-changing operations via the ICF layer. Review transaction SESSION to see if secure session management is enforced for web-based access.
    Affected if The system accepts requests from external crafted URLs without validating session integrity or requiring additional authentication.

Your system is affected if it runs SAP NetWeaver AS ABAP versions 740-790 (specifically 740, 750-757, 789, or 790) and has ICF HTTP services enabled that accept unauthenticated or insufficiently validated URL parameters.

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

Implement proper authorization checks on all URL parameters and validate incoming requests to prevent manipulation of object references. Apply SAP security notes and ensure CSRF protection is enabled for sensitive operations.

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-23859 — 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-23859 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