dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-0070

CRITICAL · 9.9 CVSS v3.1 Published 2025-01-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 allows an authenticated attacker to obtain illegitimate access to the system by exploiting improper authentication checks, resulting in privilege escalation. On successful exploitation, this can result in potential security concerns. This results in a high impact on confidentiality, integrity, and 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 · moderate confidence

SAP NetWeaver Application Server for ABAP and ABAP Platform contains an improper authentication check vulnerability that allows an authenticated attacker to bypass normal authentication controls and escalate privileges to gain unauthorized access to the system.

MitigationApply the relevant SAP security patches for CVE-2025-0070 immediately and review user role assignments and authentication logs for signs of exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Identify SAP NetWeaver AS ABAP installation
    Execute transaction SM37 or check process list for ABAP dispatcher processes (e.g., disp+work.exe on Windows, disp+work on Unix). Alternatively, query SAP system landscape directory or check for SAP GUI/Logon pad access.
    Affected if SAP NetWeaver Application Server for ABAP is installed and running
  2. Determine ABAP kernel version
    Execute transaction SM51 or use the SAP kernel version check: log into SAP GUI and run transaction 'SPAM' or use transaction 'KERNEL' to view kernel release and patch level. On OS level, check the 'disp+work' version in the kernel directory.
    Affected if Kernel version falls within the unpatched vulnerable range for CVE-2025-0070
  3. Verify authentication mechanism configuration
    Check SAP profile parameters related to authentication: execute transaction RZ10/RZ11 and review parameters like 'login/password_change', 'login/fails_to_session_end', and 'authentication/active'. Use transaction SM37 to review background jobs related to authentication.
    Affected if Standard SAP authentication is enabled without additional security patches applied
  4. Review privileged user role assignments
    Execute transaction PFCG to review roles with SAP_ALL, SAP_NEW, or sensitive authorization objects (e.g., S_ABAP_ALL, S_ADARSO). Use transaction SUIM to search for users with elevated roles. Check for unexpected role assignments since the patch release date.
    Affected if Users possess roles that allow privilege escalation or unauthorized system access
  5. Inspect authentication logs for exploitation signs
    Execute transaction SM37 to review job logs, use transaction SALRT for alert logs, and check transaction SUIM for failed login attempts. Review logs for: multiple failed auth attempts followed by success, unusual session creation, or privilege escalation events.
    Affected if Logs show authentication anomalies, unauthorized privilege escalation, or session takeover patterns

A user is affected if they run an unpatched version of SAP NetWeaver AS for ABAP where the authentication bypass can be exploited to escalate privileges.

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 patches for CVE-2025-0070 immediately and review user role assignments and authentication logs for signs of exploitation.

Have this fixed 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-2025-0070 — 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-2025-0070 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