dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2020-6275

CRITICAL · 9.8 CVSS v3.1 Published 2020-06-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 AS ABAP, versions 700, 701, 702, 710, 711, 730, 731, 740, 750, 751, 752, 753, 754, are vulnerable for Server Side Request Forgery Attack where in an attacker can use inappropriate path names containing malicious server names in the import/export of sessions functionality and coerce the web server into authenticating with the malicious server. Furthermore, if NTLM is setup the attacker can compromise confidentiality, integrity and availability of the SAP database.

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 AS ABAP contains a Server Side Request Forgery (SSRF) vulnerability in the session import/export functionality. Attackers can exploit inappropriate path names containing malicious server names to coerce the web server into authenticating with an attacker-controlled server. When NTLM authentication is configured, this can lead to compromise of confidentiality, integrity, and availability of the SAP database.

MitigationApply SAP security patches for CVE-2020-6275. Additionally, restrict outbound authentication to untrusted servers and consider disabling NTLM authentication where possible to mitigate the credential theft vector.

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

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. Verify SAP Netweaver AS ABAP version
    Check the installed SAP Netweaver Application Server ABAP version using transaction code SM51 or by inspecting the SAP system version information.
    Affected if The installed version matches one of the affected versions: 700, 701, 702, 710, 711, 730, 731, 740, 750, 751, 752, or 753.
  2. Confirm session import/export functionality is active
    Identify whether the session import/export feature is enabled or being used in the SAP system. This may be accessible through relevant transaction codes or system configuration related to session management.
    Affected if The session import/export functionality is actively configured or being used on the affected system.
  3. Check NTLM authentication configuration
    Review the SAP system authentication settings to determine if NTLM authentication is configured for outbound connections or web server communications.
    Affected if NTLM authentication is enabled in the SAP environment, particularly for outbound connections.
  4. Inspect outbound authentication policies
    Examine the SAP system configuration for outbound authentication settings, specifically looking for policies that allow authentication to external or untrusted servers.
    Affected if The system is configured to allow outbound authentication to untrusted or external servers without proper restrictions.

The environment is affected if the SAP Netweaver AS ABAP version is one of the listed affected versions AND the session import/export functionality is in use, with NTLM or unrestricted outbound authentication enabled.

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 SAP security patches for CVE-2020-6275. Additionally, restrict outbound authentication to untrusted servers and consider disabling NTLM authentication where possible to mitigate the credential theft vector.

Fix this in Netweaver Application Server Abap Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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