CVE-2024-22246
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 · uneditedVMware SD-WAN Edge contains an unauthenticated command injection vulnerability potentially leading to remote code execution. A malicious actor with local access to the Edge Router UI during activation may be able to perform a command injection attack that could lead to full control of the router.
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 confidenceVMware SD-WAN Edge contains an unauthenticated command injection vulnerability that allows an attacker with local access to the Edge Router UI during the activation phase to inject arbitrary OS commands, potentially achieving remote code execution and full control of the router.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm VMware SD-WAN Edge is deployedIdentify if VMware SD-WAN Edge software is running on the device. This may be visible in the system hostname, management interface, or by checking for 'VMware' or 'SD-WAN' in the device documentation or management console.Affected if The device is running VMware SD-WAN Edge software.
-
Determine installed SD-WAN Edge versionAccess the Edge Router UI or CLI and retrieve the installed software version. This is typically found in the device's 'System' or 'About' section of the management interface, or via CLI command such as 'show version' or 'vgw-cli -c show system-info'. Compare your version to any vendor-released patch versions that address CVE-2024-22246.Affected if The installed version has not been patched and falls within the unpatched version range for this vulnerability.
-
Verify activation UI accessibilityDetermine whether the Edge Router is in or has recently passed through the activation phase. During activation, the device typically exposes a setup or activation web interface (often on HTTP/HTTPS) that does not require authentication. Check if this interface is reachable on the expected IP/hostname.Affected if The activation UI is accessible without authentication, indicating the device may be in a vulnerable state.
-
Check network exposure of activation interfaceReview firewall rules, network segmentation, and access controls to determine whether the activation interface (typically on the LAN or DMZ interface during setup) is reachable from untrusted networks. Use port scanning or log review to identify unauthorized access attempts to common activation ports.Affected if The activation interface is exposed to networks beyond physically isolated local access.
A defender is affected if their VMware SD-WAN Edge device runs an unpatched version and has its activation UI accessible, particularly if the device is not in a physically or network-isolated state during or after the activation phase.
Generated from the published advisory. Verify against your own configuration.
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 dataApply VMware's security patch for this vulnerability when available; ensure the activation process is performed in a physically and network-isolated environment to limit exposure to local attackers.
- Consultation6.0 h
- Implementation10.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22246 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-22246 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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