Skip to main content
Mallory
MediumCISA KEVExploited in the wildPublic exploit

Command Injection in Cisco NX-OS CLI

IdentifiersCVE-2024-20399CWE-77

CVE-2024-20399 is a command-injection vulnerability in the CLI of Cisco NX-OS Software. It is caused by insufficient validation of arguments passed to specific configuration CLI commands. An authenticated attacker who already possesses Administrator credentials can supply crafted input to an affected configuration command and cause arbitrary commands to be executed on the device’s underlying operating system as root. Cisco noted that exploitation effectively allows escape from the NX-OS CLI into the underlying OS. The flaw has been observed in the wild, including use to deploy the VELVETSHELL backdoor on Cisco Nexus switches.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary command execution as root on the underlying operating system of an affected Cisco NX-OS device. This can enable full device compromise, installation of malware or backdoors, persistence, credential access, manipulation of device configuration, and use of the switch as an internal pivot point. On platforms where administrative users already have bash-shell access, the vulnerability may not provide additional privilege elevation, but it still enables root-level OS command execution through affected CLI paths and may support stealthier post-compromise activity.

Mitigation

If you can’t patch tonight, do this now.

No workarounds are available according to Cisco. Compensating controls are to strictly limit and monitor Administrator access to NX-OS devices and to the affected configuration CLI commands, closely monitor for unexpected configuration changes and related syslog events, and rotate/secure administrative credentials such as network-admin and vdc-admin. Where feasible, reduce exposure of management interfaces and investigate devices for signs of post-exploitation persistence.

Remediation

Patch, then assume compromise.

Apply Cisco-provided software updates that address CVE-2024-20399. Use Cisco’s Software Checker to determine whether the deployed NX-OS release and platform are vulnerable and identify the earliest fixed release, then upgrade to the appropriate fixed version for the affected device. Because this vulnerability has been exploited in the wild and used for persistence, remediation should also include integrity review of affected devices for unauthorized OS-level changes, backdoors, or malware.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Cisco SystemsNx-Osoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence4

Every observed campaign linking this CVE to a named adversary.

Associated malware1

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.