Solution ManagerApplication · Sap

CVE-2023-27893

HIGH · 8.8 CVSS v3.1 Published 2023-03-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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
An attacker authenticated as a user with a non-administrative role and a common remote execution authorization in SAP Solution Manager and ABAP managed systems (ST-PI) - versions 2088_1_700, 2008_1_710, 740, can use a vulnerable interface to execute an application function to perform actions which they would not normally be permitted to perform.  Depending on the function executed, the attack can read or modify any user or application data and can make the application unavailable.

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

This is a privilege escalation vulnerability in SAP Solution Manager and ABAP managed systems (ST-PI). An authenticated user with non-administrative role and remote execution authorization can exploit a vulnerable interface to execute application functions beyond their permitted scope, allowing unauthorized access to read/modify any user or application data or cause denial of service.

MitigationApply relevant SAP security notes/patches for CVE-2023-27893 and review user authorizations to ensure the remote execution authorization is only granted to necessary administrative users.

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:= 740

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Solution Manager version
    Execute transaction SM37 or check system version via SAP manager. Look for system information showing SAP Solution Manager version 740 specifically.
    Affected if The installed SAP Solution Manager version is exactly 740.
  2. Verify ST-PI component installation
    Check the ST-PI (SAP Solution Manager Integration Package) component via transaction SPAM or SAINT package manager. Look for installed support packages related to ST-PI.
    Affected if ST-PI component is installed on the SAP Solution Manager system.
  3. Check remote execution authorization configuration
    Use transaction SUIM or SU53 to examine authorization objects. Specifically look for authorization object S_RFC or similar remote execution authorizations assigned to users.
    Affected if Users possess remote execution authorization (S_RFC or equivalent) but lack full administrative privileges.
  4. Review user role assignments
    Execute transaction PFCG to analyze role assignments. Identify users with non-administrative roles who also have remote execution capabilities granted.
    Affected if There exist users with non-administrative roles that include remote execution authorization privileges.

A user is affected if running SAP Solution Manager 740 with ST-PI installed, where non-administrative users have been granted remote execution authorization through role assignments.

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 relevant SAP security notes/patches for CVE-2023-27893 and review user authorizations to ensure the remote execution authorization is only granted to necessary administrative users.

Fix this in Solution Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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