dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022.
Netweaver Application Server JavaApplication · Sap

CVE-2020-6287

CRITICAL · 10.0 CVSS v3.1 Published 2020-07-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
In the wild High EPSS Public exploit 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 JAVA (LM Configuration Wizard), versions - 7.30, 7.31, 7.40, 7.50, does not perform an authentication check which allows an attacker without prior authentication to execute configuration tasks to perform critical actions against the SAP Java system, including the ability to create an administrative user, and therefore compromising Confidentiality, Integrity and Availability of the system, leading to Missing Authentication Check.

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 LM Configuration Wizard lacks authentication checks, enabling unauthenticated attackers to execute configuration tasks and create administrative users, fully compromising the system.

MitigationApply SAP security patches for CVE-2020-6287 immediately; if patching is not possible, disable the LM Configuration Wizard component and restrict network access to SAP NetWeaver Java ports.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Java version
    Use SAP transaction code SM51 to display the kernel version, or check the SAP system information via SAPMMC or the SAP NetWeaver Administrator (NWA) console. Alternatively, check the file SAPEXE.SAR or SAPJVM version on the server.
    Affected if The installed version is 7.30, 7.31, 7.40, or 7.50
  2. Locate LM Configuration Wizard component
    Verify the presence of the LM Configuration Wizard (also known as ConfigWizard or TC) in the SAP NetWeaver AS Java deployment. Check if the application is deployed by accessing the SAP NetWeaver Administrator and reviewing the deployed applications list.
    Affected if The LM Configuration Wizard application is deployed and accessible on the system
  3. Check LM Configuration Wizard accessibility
    Attempt to access the LM Configuration Wizard endpoint. Common paths include /config wizard/ or /ConfigWizard. Use a web browser or curl command to attempt access without credentials to the endpoint such as http://<host>:<port>/config wizard/.
    Affected if The LM Configuration Wizard endpoint responds without requiring authentication credentials
  4. Verify authentication enforcement on vulnerable endpoint
    Review the SAP ICM (Internet Communication Manager) configuration and web dispatcher settings to determine if the /config wizard/ path requires authentication. Check the SAP UME (User Management Engine) and any ICF (Internet Communication Framework) service settings related to the Configuration Wizard.
    Affected if The Configuration Wizard endpoint is exposed without enforced authentication or is accessible via the ICF without authentication requirements

A system is affected if it runs SAP NetWeaver AS Java versions 7.30 through 7.50 with the LM Configuration Wizard component deployed and accessible without authentication.

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 patches for CVE-2020-6287 immediately; if patching is not possible, disable the LM Configuration Wizard component and restrict network access to SAP NetWeaver Java ports.

Recommended fix High confidence

Apply SAP Security Note 2934135 for your respective version (7.30, 7.31, 7.40, 7.50); for version 7.50, apply Support Package 08 or higher

  1. 1. Identify the exact SAP NetWeaver AS JAVA version and patch level by checking the system information in SAP MII (SAP_DEFAULT system).
  2. 2. Access the SAP Launchpad (support.sap.com) and search for SAP Security Note 2934135, which addresses CVE-2020-6287.
  3. 3. Download the relevant correction instructions and transport requests for your specific NetWeaver version (7.30, 7.31, 7.40, or 7.50).
  4. 4. Apply the SAP Security Note using the SAP Transaction SNOTE or via the SAP Maintenance Optimizer/Transaction SPAM.
  5. 5. After applying the patch, verify the LM Configuration Wizard (lmconfigwizard) is properly secured by attempting an unauthenticated access attempt to confirm the vulnerability is remediated.
  6. 6. Alternatively, as a temporary mitigation, disable the LM Configuration Wizard application in the SAP Java NetWeaver AS by navigating to the SAP NetWeaver Administrator (NWA) -> Configuration -> Applications and undeploying or disabling the lmconfigwizard application.
Caveat Review SAP Security Note 2934135 for any post-processing steps required; patches may require system restart

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

Fix this in Netweaver Application Server Java Exploited in the wild — priority engagement
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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