dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2023-0014

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-10
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 No privileges 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 ABAP Server and ABAP Platform - versions SAP_BASIS 700, 701, 702, 710, 711, 730, 731, 740, 750, 751, 752, 753, 754, 755, 756, 757, KERNEL 7.22, 7.53, 7.77, 7.81, 7.85, 7.89, KRNL64UC 7.22, 7.22EXT, 7.53, KRNL64NUC 7.22, 7.22EXT, creates information about system identity in an ambiguous format. This could lead to capture-replay vulnerability and may be exploited by malicious users to obtain illegitimate access to the system.

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

SAP NetWeaver ABAP Server and ABAP Platform contain a capture-replay vulnerability due to ambiguous system identity information creation. The vulnerable component generates identity data in a format that can be captured and replayed by attackers, enabling unauthorized access to the system. This affects core authentication mechanisms in the ABAP kernel and basis components.

MitigationApply the relevant SAP security patch (SAP Note) for CVE-2023-0014 and update affected SAP_BASIS and KERNEL versions to patched releases. Review system identity configuration and implement additional session integrity controls where possible.

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= 710= 711= 730= 731= 740= 750= 751= 752= 753
Netweaver Application Server Abap KernelApplication
Affected:= 7.22= 7.53= 7.77= 7.81= 7.85= 7.89
Netweaver Application Server Abap Krnl64nucApplication
Affected:= 7.22= 7.22ext
Netweaver Application Server Abap Krnl64ucApplication
Affected:= 7.22= 7.22ext= 7.53

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Check ABAP Kernel version
    Execute 'disp+work -V' from the kernel directory or use transaction SM51 to view the kernel release. Also check via SAP transaction SM37 and look at system process information.
    Affected if Kernel version equals 7.22, 7.53, 7.77, 7.81, 7.85, or 7.89 (unpatched)
  2. Check SAP_BASIS version
    Use transaction SPAM (Support Package Manager) and select 'Status' to view the current SAP_BASIS version, or use transaction SAINT (Add-On Installation Tool) and check the installed support package level.
    Affected if ABAP Server version equals 700, 701, 702, 710, 711, 730, 731, 740, 750, 751, 752, or 753 without security patches applied
  3. Check kernel subcomponent versions
    Query system component information via transaction SM51, or execute 'disp+work -v' to display detailed kernel build information including KRNL64NUC and KRNL64UC components.
    Affected if KRNL64NUC version is 7.22 or 7.22ext, or KRNL64UC version is 7.22, 7.22ext, or 7.53 (unpatched)
  4. Review system identity configuration
    Check SAP system identity settings via transaction SU01 (user maintenance) or SUCON (system configuration) for ambiguous or duplicate identity parameters that could be replayed.
    Affected if System generates identity data in a format that lacks unique session binding or can be captured from logs/network traces

You are affected if your SAP NetWeaver ABAP kernel or SAP_BASIS version matches any of the listed unpatched versions and the system uses vulnerable identity generation for authentication sessions.

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 patch (SAP Note) for CVE-2023-0014 and update affected SAP_BASIS and KERNEL versions to patched releases. Review system identity configuration and implement additional session integrity controls where possible.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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