dbcve.org
Diagnostics AgentApplication · Sap

CVE-2019-0330

CRITICAL · 9.1 CVSS v3.1 Published 2019-07-10
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
The OS Command Plugin in the transaction GPA_ADMIN and the OSCommand Console of SAP Diagnostic Agent (LM-Service), version 7.2, allow an attacker to inject code that can be executed by the application. An attacker could thereby control the behavior of the application.

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

OS command injection vulnerability in the OS Command Plugin of SAP Diagnostic Agent (LM-Service) version 7.2. The flaw exists in transaction GPA_ADMIN and the OSCommand Console, allowing unauthenticated attackers to inject arbitrary OS commands that the application will execute with the privileges of the running service.

MitigationApply the relevant SAP security patch for CVE-2019-0330. If a patch is unavailable, restrict network access to the GPA_ADMIN transaction and OSCommand Console, and review SAP Diagnostic Agent configurations for hardening options.

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:= 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 if SAP Diagnostic Agent is installed
    Check for SAP Diagnostic Agent processes running on the system (look for processes containing 'diagagent' or 'SAP DIAgent' in process list) or check standard SAP installation directories.
    Affected if SAP Diagnostic Agent process is running on the system
  2. Verify the installed version matches affected release
    Check the SAP Diagnostic Agent version by inspecting the agent's about dialog, version file in the installation directory, or querying the agent via its management interface. Compare the version to 7.20.
    Affected if The installed version is exactly 7.20
  3. Confirm OS Command Plugin is enabled
    Check the SAP Diagnostic Agent configuration files or management console for the OS Command Plugin status. Look for plugin configuration that enables OS command execution functionality.
    Affected if OS Command Plugin is installed and enabled in the agent configuration
  4. Verify GPA_ADMIN transaction accessibility
    Check if the GPA_ADMIN transaction endpoint is exposed and accessible. This typically involves checking the SAP Diagnostic Agent web interface or RFC access controls for this administrative transaction.
    Affected if GPA_ADMIN transaction is accessible without authentication or with default credentials
  5. Check network exposure of OSCommand Console
    Assess whether the OSCommand Console interface is reachable over the network. Verify if it is bound to external/network interfaces rather than localhost only, and whether authentication is required for access.
    Affected if OSCommand Console is exposed on a network interface accessible to unauthenticated users

A system is affected if it runs SAP Diagnostic Agent version 7.20 with the OS Command Plugin enabled and the GPA_ADMIN transaction or OSCommand Console accessible to unauthenticated users over the network.

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 the relevant SAP security patch for CVE-2019-0330. If a patch is unavailable, restrict network access to the GPA_ADMIN transaction and OSCommand Console, and review SAP Diagnostic Agent configurations for hardening options.

Fix this in Diagnostics Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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