Solution ManagerApplication · Sap

CVE-2022-22544

CRITICAL · 9.1 CVSS v3.1 Published 2022-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/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
Solution Manager (Diagnostics Root Cause Analysis Tools) - version 720, allows an administrator to execute code on all connected Diagnostics Agents and browse files on their systems. An attacker could thereby control the managed systems. It is considered that this is a missing segregation of duty for the SAP Solution Manager administrator. Impacts of unauthorized execution of commands can lead to sensitive information disclosure, loss of system integrity and denial of 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 · high confidence

SAP Solution Manager 720 Diagnostics Root Cause Analysis Tools lacks proper segregation of duty controls, allowing administrators to execute arbitrary code on all connected Diagnostics Agents and browse files on those systems, enabling full control over managed endpoints.

MitigationImplement role-based segregation of duties in SAP Solution Manager to restrict administrator capabilities from executing arbitrary code on Diagnostics Agents, following principle of least privilege.

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

CVSS:3.1/AV:N/AC:L/PR:H/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 installed SAP Solution Manager version
    Access SAP Solution Manager administration interface or check system information via SAP transaction SM37, or inspect the SAP System Landscape Directory (SLD) for Solution Manager version details
    Affected if The installed version is SAP Solution Manager 7.20 (specifically version 7.20)
  2. Verify Root Cause Analysis Tools availability
    Navigate to SAP Solution Manager transaction SOLMAN_WORKCENTER or search for Root Cause Analysis functionality in the Solution Manager workcenter. Check if RCA tools are listed as available or configured
    Affected if Root Cause Analysis Tools are present and accessible in the Solution Manager environment
  3. Confirm Diagnostics Agents are connected
    In SAP Solution Manager, go to the Diagnostics section (transaction SMDAEMON or via the Solution Manager Configuration wizard) and check the list of connected Diagnostics Agents
    Affected if One or more Diagnostics Agents are connected to the Solution Manager system
  4. Check administrator role assignments for RCA permissions
    Review user role assignments using transaction PFCG or SUIM. Look for roles that grant RCA administration privileges such as SAP_SLM_ADMIN or similar administrative roles associated with Root Cause Analysis
    Affected if Users with administrator roles have permissions to access RCA tools and execute code on connected agents
  5. Inspect RCA configuration for unrestricted execution capability
    Access RCA configuration settings via the Solution Manager administration console. Check if the RCA functionality permits arbitrary command execution or file browsing on connected agents
    Affected if RCA configuration allows unrestricted command execution or file system access to Diagnostics Agents without additional approval workflows

The environment is affected if SAP Solution Manager 7.20 is installed with Root Cause Analysis Tools enabled and Diagnostics Agents are connected, allowing administrators to execute arbitrary code on agents.

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

Implement role-based segregation of duties in SAP Solution Manager to restrict administrator capabilities from executing arbitrary code on Diagnostics Agents, following principle of least privilege.

Fix this in Solution Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22544 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2022-22544 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