dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2023-23853

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
An unauthenticated attacker in AP NetWeaver Application Server for ABAP and ABAP Platform - versions 700, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756, 757, 789, 790, can craft a link which when clicked by an unsuspecting user can be used to redirect a user to a malicious site which could read or modify some sensitive information or expose the victim to a phishing attack. Vulnerability has no direct impact on availability.

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 an open redirect vulnerability in SAP NetWeaver Application Server for ABAP. An unauthenticated attacker can craft malicious URLs that, when clicked by a user, redirect the victim to an attacker-controlled external site. This enables phishing attacks and potential exposure of sensitive information transmitted through the redirected session.

MitigationApply the relevant SAP security note/patch for this vulnerability and review URL redirect handling configurations in SAP NetWeaver to ensure proper validation of redirect targets.

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= 702= 731= 740= 750= 751= 752= 753= 754= 755= 756= 757

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
    Log into the SAP system and execute transaction code SM51, or use the SAP META directory or system information transaction to retrieve the SAP NetWeaver Application Server for ABAP version number.
    Affected if The displayed version matches any of the following: 700, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756, or 757.
  2. Verify ABAP Support Package Stack level
    In the SAP system, use transaction code SPAM (Support Package Manager) or check the system information to confirm the exact kernel and support package version of the ABAP application server.
    Affected if The kernel version corresponds to one of the affected versions listed (700 through 757).
  3. Review HTTP redirect handling configuration
    Use transaction code SICF (SAP Internet Communication Manager) to inspect the active ICF services and their redirect URL configurations, looking for any custom or third-party URL handlers that may process external redirect parameters.
    Affected if External redirect handlers are enabled and no validation is applied to the redirect target parameter.
  4. Examine web dispatcher or load balancer redirect rules
    If SAP Web Dispatcher or an external load balancer is in use, review the configuration for URL rewrite or redirect rules that may allow arbitrary external URLs to be injected into redirect responses.
    Affected if Redirect rules accept arbitrary hostnames or query parameters without validation.
  5. Audit URL redirect behavior with test URLs
    Using an unauthenticated browser session, attempt to access a known SAP ABAP transaction or portal URL with a crafted redirect parameter pointing to an external domain (for example, adding a parameter like ~redirect=httpexample.com) to observe if the application allows the redirect.
    Affected if The system redirects to an external domain controlled by the tester instead of rejecting or neutralizing the redirect.

Your environment is affected if the installed SAP NetWeaver Application Server for ABAP version matches any of the affected versions (700, 702, 731, 740, 750-757) and external redirect parameters are not validated.

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 note/patch for this vulnerability and review URL redirect handling configurations in SAP NetWeaver to ensure proper validation of redirect targets.

Fix this in Netweaver Application Server Abap Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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