dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2023-23860

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 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.

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

Open redirect vulnerability in SAP NetWeaver AS for ABAP and ABAP Platform allows unauthenticated attackers to craft malicious links that redirect users to external websites, enabling phishing attacks and potential sensitive information exposure.

MitigationApply SAP security notes/patches for CVE-2023-23860 and implement URL validation/whitelist-based redirect controls in SAP NetWeaver to prevent unauthorized redirects.

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 SAP NetWeaver ABAP version
    Execute transaction SM51 or use SAPMMC to view the kernel release and version of the SAP NetWeaver Application Server ABAP. Alternatively, check the kernel version via 'disp+work -v' command or in the /sapmnt/<SID>/exe directory.
    Affected if The installed version matches 740, 750, 751, 752, 753, 754, 755, 756, 757, 789, or 790.
  2. Verify SAP Gateway service is running
    Check via transaction SMGW or by reviewing the SAP Management Console to confirm the SAP Gateway (sapgw00) is active and listening on the configured port.
    Affected if The Gateway is exposed to untrusted networks and the ABAP version is in the affected list.
  3. Confirm Internet Communication Manager (ICM) is enabled
    Review transaction SMICM or check icman process status. The ICM handles HTTP/HTTPS requests for SAP web applications and is required for this open redirect to be exploitable.
    Affected if ICM is active and accessible via HTTP/HTTPS from external networks.
  4. Inspect ICM redirect parameters
    Use transaction RZ10 or check the icm/logging file to review parameters such as icm/HTTP/redirect_0 or similar redirect rules that may allow external URLs.
    Affected if ICM contains redirect rules allowing arbitrary external domains without whitelist validation.
  5. Check for URL parameter logging in HTTP access logs
    Review ICM access logs (default location: /sapmnt/<SID>/log/icm* or via transaction SMICM -> Log Files) for suspicious redirect parameter patterns such as 'redirect=' or 'url=' pointing to external domains.
    Affected if Logs show redirect parameters being passed to external non-SAP domains.

You are affected if your SAP NetWeaver ABAP version matches 740, 750, 751, 752, 753, 754, 755, 756, 757, 789, or 790 AND the ICM/Gateway is accessible via HTTP/HTTPS from networks where attackers could craft malicious redirect links.

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 SAP security notes/patches for CVE-2023-23860 and implement URL validation/whitelist-based redirect controls in SAP NetWeaver to prevent unauthorized redirects.

Recommended fix Moderate confidence

Upgrade to SAP NetWeaver AS ABAP 754 or higher where the vulnerability is resolved

  1. 1. Identify the specific SAP Security Note for CVE-2023-23860 by searching the SAP Support Portal at support.sap.com/securitynotes
  2. 2. Download and review the security note to understand the required corrections
  3. 3. Apply the security note via SAP Transport Management System (TMS) or manual correction as specified in the note
  4. 4. Verify the changes by testing the redirect functionality that was vulnerable
  5. 5. Ensure proper change transport and documentation procedures are followed per SAP governance
Caveat Minor - Upgrading to 754+ may require compatibility testing of custom ABAP code and dependencies

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

Fix this in Netweaver Application Server Abap Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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