dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-38817

MEDIUM · 6.7 CVSS v3.1 Published 2024-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
VMware NSX contains a command injection vulnerability.  A malicious actor with access to the NSX Edge CLI terminal may be able to craft malicious payloads to execute arbitrary commands on the operating system as root.

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 · moderate confidence

VMware NSX contains a command injection vulnerability in the NSX Edge CLI terminal. An attacker with access to the CLI can craft malicious payloads to execute arbitrary operating system commands with root privileges.

MitigationRestrict access to the NSX Edge CLI terminal to trusted personnel only. Apply vendor patches when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:L/AC:L/PR:H/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. Confirm VMware NSX installation
    Run 'get product' or 'show version' command on the system to identify the product name and version. Check if the system is running VMware NSX.
    Affected if The system is not running VMware NSX (not affected)
  2. Identify NSX Edge component
    Run 'get edge' or 'show edge' command in the CLI to verify if NSX Edge is deployed. Also check 'get cluster status' to see edge node status.
    Affected if NSX Edge is not deployed (not affected)
  3. Check NSX version
    Run 'get version' or check the NSX Manager UI under System > Software to determine the exact NSX version installed.
    Affected if Unable to determine version; compare your installed version against vendor advisories for CVE-2024-38817 fixed versions
  4. Verify CLI access controls
    Check NSX Edge CLI configuration for user access controls: run 'get users' and review the 'authz' or 'user' configuration. Verify which users have shell/CLI access privileges.
    Affected if Any untrusted or unauthorized user accounts have CLI access (potential attack vector present)
  5. Inspect recent CLI command history
    If logging is enabled, review NSX Edge CLI audit logs for suspicious commands. Check for unexpected shell spawns or commands containing unusual characters (;, |, $, `, etc.).
    Affected if Unexpected or suspicious CLI commands are found in logs

User is affected if NSX Edge is deployed and untrusted users have CLI access to the NSX Edge terminal, regardless of version - patch immediately per vendor guidance.

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

Restrict access to the NSX Edge CLI terminal to trusted personnel only. Apply vendor patches when available.

Have this fixed 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-2024-38817 — 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-2024-38817 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