Cisco Unified Computing System up to 4.3(6b) CLI os command injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in Cisco Unified Computing System. Affected is an unknown function of the component CLI. This manipulation causes os command injection. This vulnerability is registered as CVE-2025-20295. The attack needs to be launched locally. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Cisco Unified Computing System. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component CLI. The manipulation with an unknown input leads to a os command injection vulnerability. The CWE definition for the vulnerability is CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

A vulnerability in the CLI of Cisco UCS Manager Software could allow an authenticated, local attacker with administrative privileges to read or create a file or overwrite any file on the file system of the underlying operating system of an affected device, including system files.   This vulnerability is due to insufficient input validation of command arguments supplied by the user. An attacker could exploit this vulnerability by authenticating to a device and submitting crafted input to the affected command. A successful exploit could allow the attacker to read or create a file or overwrite any file on the file system of the underlying operating system of the affected device, including system files. To exploit this vulnerability, the attacker must have valid administrative credentials on the affected device.

It is possible to read the advisory at sec.cloudapps.cisco.com. This vulnerability is known as CVE-2025-20295 since 10/10/2024. The exploitation appears to be easy. Attacking locally is a requirement. The exploitation requires an enhanced level of successful authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1202 according to MITRE ATT&CK.

Upgrading eliminates this vulnerability.

The vulnerability is also documented in the databases at EUVD (EUVD-2025-25944) and CERT Bund (WID-SEC-2025-1917). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

• Cisco Unified Computing System (UCS)
• Cisco Integrated Management Controller

Productinfo

Type

• Virtualization Software

Vendor

• Cisco

Name

• Unified Computing System

Version

• 3.2(1d)
• 3.2(2b)
• 3.2(2c)
• 3.2(2d)
• 3.2(2e)
• 3.2(2f)
• 3.2(3a)
• 3.2(3b)
• 3.2(3d)
• 3.2(3e)
• 3.2(3g)
• 3.2(3h)
• 3.2(3i)
• 3.2(3j)
• 3.2(3k)
• 3.2(3l)
• 3.2(3n)
• 3.2(3o)
• 3.2(3p)
• 4.0(1a)
• 4.0(1b)
• 4.0(1c)
• 4.0(1d)
• 4.0(2a)
• 4.0(2b)
• 4.0(2d)
• 4.0(2e)
• 4.0(4a)
• 4.0(4b)
• 4.0(4c)
• 4.0(4d)
• 4.0(4e)
• 4.0(4f)
• 4.0(4g)
• 4.0(4h)
• 4.0(4i)
• 4.0(4k)
• 4.0(4l)
• 4.0(4m)
• 4.0(4n)
• 4.0(4o)
• 4.1(1a)
• 4.1(1b)
• 4.1(1c)
• 4.1(1d)
• 4.1(1e)
• 4.1(2a)
• 4.1(2b)
• 4.1(2c)
• 4.1(3a)
• 4.1(3b)
• 4.1(3c)
• 4.1(3d)
• 4.1(3e)
• 4.1(3f)
• 4.1(3h)
• 4.1(3i)
• 4.1(3j)
• 4.1(3k)
• 4.1(3l)
• 4.1(3m)
• 4.1(3n)
• 4.1(4a)
• 4.2(1c)
• 4.2(1d)
• 4.2(1f)
• 4.2(1i)
• 4.2(1k)
• 4.2(1l)
• 4.2(1m)
• 4.2(1n)
• 4.2(2a)
• 4.2(2c)
• 4.2(2d)
• 4.2(2e)
• 4.2(3b)
• 4.2(3d)
• 4.2(3e)
• 4.2(3g)
• 4.2(3h)
• 4.2(3i)
• 4.2(3j)
• 4.2(3k)
• 4.2(3l)
• 4.2(3m)
• 4.2(3n)
• 4.2(3o)
• 4.3(2b)
• 4.3(2c)
• 4.3(2e)
• 4.3(2f)
• 4.3(3a)
• 4.3(3c)
• 4.3(4a)
• 4.3(4b)
• 4.3(4c)
• 4.3(4d)
• 4.3(4e)
• 4.3(4f)
• 4.3(5a)
• 4.3(5c)
• 4.3(5d)
• 4.3(5e)
• 4.3(6a)
• 4.3(6b)

License

• commercial

Website

• Vendor: https://www.cisco.com/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion