dbcve.org
Diagnostics AgentApplication · Sap

CVE-2023-27267

HIGH · 8.1 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 →
90/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
Due to missing authentication and insufficient input validation, the OSCommand Bridge of SAP Diagnostics Agent - version 720, allows an attacker with deep knowledge of the system to execute scripts on all connected Diagnostics Agents. On successful exploitation, the attacker can completely compromise confidentiality, integrity and availability of the 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

The OSCommand Bridge in SAP Diagnostics Agent version 720 lacks authentication controls and proper input validation, allowing an authenticated attacker to execute arbitrary scripts on all connected Diagnostics Agents. This enables complete system compromise through the trusted agent communication channel.

MitigationApply the SAP security patch for CVE-2023-27267 and ensure OSCommand Bridge requires authentication with proper input sanitization before enabling remote script execution capabilities.

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
Diagnostics AgentApplication
Affected:= 720

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

CVSS:3.1/AV:N/AC:H/PR:N/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 if SAP Diagnostics Agent is installed
    Check for SAP Diagnostics Agent installation by looking for SAP diagnostic-related processes, services, or installation directories on the system. Common locations include SAP installation paths or Windows services.
    Affected if SAP Diagnostics Agent software is present on the system and version 720 is confirmed
  2. Confirm the installed version is 720
    Query the Diagnostics Agent version through SAP management tools, the agent's own version information, or installed software listings. Compare against the affected version range.
    Affected if The installed version is exactly 720 (no other versions are indicated as affected)
  3. Determine if OSCommand Bridge is configured or enabled
    Review Diagnostics Agent configuration settings, documentation, or management console for OSCommand Bridge module. Check whether this feature has been set up or activated in the agent deployment.
    Affected if OSCommand Bridge feature is enabled or configured in the Diagnostics Agent

The environment is affected if SAP Diagnostics Agent version 720 is installed and the OSCommand Bridge feature is enabled, allowing unauthenticated remote script execution.

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 SAP security patch for CVE-2023-27267 and ensure OSCommand Bridge requires authentication with proper input sanitization before enabling remote script execution capabilities.

Recommended fix Moderate confidence

SAP Diagnostics Agent version 720 with latest Security Note patch applied, or upgrade to a subsequent version as specified in SAP Security Note 3287028

  1. Check the current Diagnostics Agent version using SAP LMDB or the SAP Solution Manager system landscape
  2. Review SAP Security Note 3287028 (or the relevant SAP Note for this CVE) for the specific patch information
  3. Apply the latest available Support Package or patch for SAP Diagnostics Agent that addresses CVE-2023-27267
  4. Verify the patch was applied successfully by checking the Diagnostics Agent version again
  5. Restart the Diagnostics Agent services if required by the patch
  6. Validate that the OSCommand Bridge now requires proper authentication
Caveat Review SAP Note for any prerequisites or configuration changes required; some patches may require downtime window

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

Fix this in Diagnostics Agent Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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