dbcve.org
Solution ManagerApplication · Sap

CVE-2020-26823

CRITICAL · 10.0 CVSS v3.1 Published 2020-11-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 Solution Manager (JAVA stack), version - 7.20, allows an unauthenticated attacker to compromise the system because of missing authorization checks in the Upgrade Diagnostics Agent Connection Service, this has an impact to the integrity and availability of the service.

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 Solution Manager version 7.20 (Java stack) contains a critical authorization bypass vulnerability in the Upgrade Diagnostics Agent Connection Service. An unauthenticated remote attacker can exploit missing authorization checks to compromise the system, affecting both integrity and availability of the service.

MitigationApply the relevant SAP security patch for CVE-2020-26823 to implement proper authorization checks in the Upgrade Diagnostics Agent Connection Service, and restrict network exposure of the affected SAP Solution Manager components.

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
Solution ManagerApplication
Affected:= 7.20

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/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 Solution Manager version
    Check the installed SAP Solution Manager version using SAP transaction code SM37 or system information pages. Look for version 7.20 specifically.
    Affected if The installed version is exactly 7.20 (version 7.20 without additional patches)
  2. Verify Java stack deployment
    Confirm that the SAP Solution Manager Java stack is deployed. This vulnerability affects only the Java stack, not the ABAP stack. Check via SAP NetWeaver Administrator or system configuration logs.
    Affected if The Java stack of SAP Solution Manager 7.20 is deployed and running
  3. Confirm Upgrade Diagnostics Agent Connection Service status
    Locate and verify the status of the Upgrade Diagnostics Agent Connection Service in the SAP system configuration. This service handles diagnostics agent communications during upgrade processes.
    Affected if The Upgrade Diagnostics Agent Connection Service is enabled and accessible in the environment
  4. Assess network exposure of affected component
    Review network accessibility of the SAP Solution Manager Java stack ports and services. Check if the diagnostics agent connection endpoints are exposed to untrusted networks.
    Affected if The SAP Solution Manager Java stack or the Upgrade Diagnostics Agent Connection Service is exposed to untrusted or public networks without proper access controls

The environment is affected if SAP Solution Manager version 7.20 with an active Java stack has the Upgrade Diagnostics Agent Connection Service enabled and accessible, particularly if exposed to untrusted networks.

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 the relevant SAP security patch for CVE-2020-26823 to implement proper authorization checks in the Upgrade Diagnostics Agent Connection Service, and restrict network exposure of the affected SAP Solution Manager components.

Recommended fix Moderate confidence

Apply SAP Solution Manager 7.20 Security Patch (consult SAP Note for specific patch number)

  1. 1. Access the SAP Support Portal at https://support.sap.com/patches
  2. 2. Navigate to SAP Solution Manager → SAP Solution Manager 7.20 → Security Patches
  3. 3. Locate the patch for CVE-2020-26823 (search by CVE ID or security note number)
  4. 4. Download and apply the relevant security patch following SAP's standard patching procedures
  5. 5. After patching, verify the Upgrade Diagnostics Agent Connection Service is functioning correctly
  6. 6. Confirm the security fix is applied by reviewing system configuration or consulting SAP Note associated with this vulnerability

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

Fix this in Solution Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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