dbcve.org
Netweaver Application Server JavaApplication · Sap

CVE-2020-6202

HIGH · 7.2 CVSS v3.1 Published 2020-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 Java (User Management Engine), versions- 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, 7.50; does not sufficiently validate the LDAP data source configuration XML document accepted from an untrusted source, leading to Missing XML Validation.

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 AS Java User Management Engine fails to properly validate LDAP data source configuration XML received from untrusted sources, allowing malicious XML injection. This missing XML validation vulnerability (likely XXE) enables attackers to inject crafted XML that could read local files, perform SSRF, or cause denial of service.

MitigationApply the SAP security patch for CVE-2020-6202 and ensure LDAP configuration XML parsers use secure settings with external entity resolution disabled and proper schema validation enabled.

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 JavaApplication
Affected:= 7.10= 7.20= 7.30= 7.31= 7.40= 7.50

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify SAP NetWeaver AS Java installation
    Check for SAP NetWeaver Application Server Java processes running on the system, or look for SAP NetWeaver Java installation directories (typically under /sapmnt/<SID>/j2ee or C:\sapmnt\<SID>\j2ee on Windows).
    Affected if SAP NetWeaver AS Java is installed and running.
  2. Determine NetWeaver AS Java version
    Locate the SAP JVM and NetWeaver AS Java version file, commonly found in the installation directory structure. On the SAP system, use transaction SM37 or check the SAP start profile for version information. Compare your installed version against the affected range: 7.10, 7.20, 7.30, 7.31, 7.40, 7.50.
    Affected if The installed version matches one of the affected versions (7.10, 7.20, 7.30, 7.31, 7.40, or 7.50).
  3. Verify LDAP data source configuration in use
    Check if the User Management Engine (UME) is configured to use an LDAP data source. In the SAP NetWeaver Administrator (NWA) or via config tool, examine the UME data source configuration under Identity Management settings. Look for LDAP as the data source backend.
    Affected if LDAP data source configuration is actively used in the User Management Engine.
  4. Inspect XML parser configuration for external entity settings
    Examine the LDAP configuration XML parser settings in the UME configuration. Specifically check whether the XML parser has external entity resolution (XXE protection) disabled or enabled. This is typically found in the LDAP provider configuration files or parser settings within the J2EE Engine configuration.
    Affected if The XML parser used for LDAP configuration allows external entity resolution or lacks secure XML validation settings.

You are affected if you run SAP NetWeaver AS Java versions 7.10 through 7.50 with LDAP data source configuration enabled and the XML parser lacks protection against external entity injection (XXE).

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 SAP security patch for CVE-2020-6202 and ensure LDAP configuration XML parsers use secure settings with external entity resolution disabled and proper schema validation enabled.

Fix this in Netweaver Application Server Java Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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