dbcve.org
Landscape ManagementApplication · Sap

CVE-2023-26458

HIGH · 8.7 CVSS v3.1 Published 2023-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/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 information disclosure vulnerability exists in SAP Landscape Management - version 3.0, enterprise edition. It allows an authenticated SAP Landscape Management user to obtain privileged access to other systems making those other systems vulnerable to information disclosure and modification.The disclosed information is for Diagnostics Agent Connection via Java SCS Message Server of an SAP Solution Manager system and can only be accessed by authenticated SAP Landscape Management users, but they can escalate their privileges to the SAP Solution Manager system.

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

Authenticated SAP Landscape Management 3.0 (enterprise edition) users can access privileged Diagnostics Agent Connection information via Java SCS Message Server of connected SAP Solution Manager systems, enabling privilege escalation and unauthorized access to those systems.

MitigationApply SAP security patches for CVE-2023-26458 when available; restrict SAP Landscape Management access to only necessary personnel and implement principle of least privilege for cross-system connections.

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
Landscape ManagementApplication
Affected:= 3.0

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
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N

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. Verify SAP Landscape Management version
    Access SAP LM system information via SAP GUI transaction code 'SLM' or check the installed product version in SAP Solution Manager system landscape directory. Use transaction 'SM37' or 'SLD' to confirm the exact version number.
    Affected if Installed version is exactly 3.0 (enterprise edition)
  2. Confirm enterprise edition is in use
    Check the SAP Landscape Management license information or product edition via transaction 'SLICENSE' or within the LM enterprise edition administrative console. Look for enterprise-specific features or licensing.
    Affected if The product edition is enterprise edition (standard edition is not affected)
  3. Identify Java SCS Message Server configuration
    Check SAP Landscape Management configuration for Java SCS (System Communication Services) Message Server connections. Look in LM configuration files or transaction 'SM51' to see if Message Server is active for Solution Manager connections.
    Affected if Java SCS Message Server is configured and connected to SAP Solution Manager systems
  4. Review Diagnostics Agent connections
    Examine the Diagnostics Agent connection settings within SAP Landscape Management. Check LM administrative interface for any configured agent connections that expose privileged connection information via the Message Server.
    Affected if Any Diagnostics Agent connections are configured pointing to Solution Manager systems

Environment is affected if running SAP Landscape Management enterprise edition version exactly 3.0 with Java SCS Message Server configured for Solution Manager connections that expose Diagnostics Agent information to authenticated users without proper privilege separation.

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 SAP security patches for CVE-2023-26458 when available; restrict SAP Landscape Management access to only necessary personnel and implement principle of least privilege for cross-system connections.

Fix this in Landscape Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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