Cisco NX-OS Software CLI Command Injection Vulnerability
Affects Cisco NX-OS Software on devices running a release without bash-shell feature support. The checked facts give no fixed release and no vendor rating.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Cisco NX-OS Software, the operating system for Cisco Nexus switches, is affected by a flaw in its command-line interface that lets a user with Administrator credentials run arbitrary commands as root on the device's underlying operating system. Successful exploitation gives full root-level control of the affected device, though on some Nexus models administrators already have this access through the bash-shell feature.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A vulnerability in the CLI of Cisco NX-OS Software could allow an authenticated user in possession of Administrator credentials to execute arbitrary commands as root on the underlying operating system of an affected device. This vulnerability is due to insufficient validation of arguments that are passed to specific configuration CLI commands. An attacker could exploit this vulnerability by including crafted input as the argument of an affected configuration CLI command. A successful exploit could allow the attacker to execute arbitrary commands on the underlying operating system with the privileges of root. Note: To successfully exploit this vulnerability on a Cisco NX-OS device, an attacker must have Administrator credentials. The following Cisco devices already allow administrative users to access the underlying operating system through the bash-shell feature, so, for these devices, this vulnerability does not grant any additional privileges: Nexus 3000 Series Switches Nexus 7000 Series Switches that are running Cisco NX-OS Software releases 8.1(1) and later Nexus 9000 Series Switches in standalone NX-OS mode
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
Affected versions
- Cisco Cisco NX-OS Software
8.2(5), 7.3(6)N1(1a), 7.3(5)D1(1), 8.4(2), 7.3(6)N1(1), 6.2(2), 8.4(3), 9.2(3), 7.0(3)I5(2), 8.2(1), 6.0(2)A8(7a), 7.0(3)I4(5), 6.0(2)A6(1), 7.3(1)D1(1), 6.2(14a), 7.0(3)I4(6), 7.3(4)N1(1), 7.0(3)I4(3), 9.2(2v), 6.0(2)A6(5b), 7.3(0)D1(1), 6.2(17a), 7.0(3)I4(7), 6.0(2)U6(1a), 7.1(5)N1(1b), 7.0(3)I4(1), 7.0(3)I4(8), 7.0(3)I4(2), 7.1(4)N1(1c), 7.0(3)IM3(1), and 288 more
References 1
sec.cloudapps.cisco.com
Questions about CVE-2024-20399
What does this mean?
Specific configuration CLI commands in Cisco NX-OS Software do not properly validate their arguments. An authenticated Administrator can use this to run arbitrary commands as root on the device's underlying operating system.Source: sec.cloudapps.cisco.com
Am I affected, and how do I check?
The bug applies to NX-OS releases that do not support the bash-shell feature, when the device runs one of the affected configuration CLI commands. The checked facts do not list specific version numbers, so check the release running on the device against Cisco's advisory.Source: sec.cloudapps.cisco.com
What should I do about it?
The checked facts do not name a fixed release, so no upgrade target can be given from them. Consult Cisco's advisory for the fixed release and apply it.Source: sec.cloudapps.cisco.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-07-02, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data