# CVE-2019-1936: Command injection in Cisco Unified Computing System Director

> Authenticated administrators can execute arbitrary root commands on Cisco UCS Director via insufficient input validation in the web interface.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2019
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-v93p-j269-v6hr

## What is CVE-2019-1936?

CVE-2019-1936 is a high-severity command injection vulnerability in Cisco Unified Computing System Director, published on 21 Aug 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in the web-based management interface of Cisco Integrated Management Controller (IMC) Supervisor, Cisco UCS Director, and Cisco UCS Director Express for Big Data could allow an authenticated, remote attacker to execute arbitrary commands on the underlying Linux shell as the root user. Exploitation of this vulnerability requires privileged access to an affected device. The vulnerability is due to insufficient validation of user-supplied input by the web-based management interface. An attacker could exploit this vulnerability by logging in to the web-based management interface with administrator privileges and then sending a malicious request to a certain part of the interface.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2019-1936?

It affects 3 products.


Products: Cisco Integrated Management Controller Supervisor, Cisco Ucs Director, Cisco Ucs Director Express for Big Data.

## How do I fix CVE-2019-1936?

No fix has been published for CVE-2019-1936 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-1936 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-1936 exists.

Public exploit code:

- Cisco UCS Director Unauthenticated Remote Code Execution (metasploit)

## Other vulnerabilities in Cisco Unified Computing System Director

- [CVE-2019-1935](https://insights.sbomify.com/CVE-2019-1935/): Hardcoded credentials in Cisco Unified Computing System Director (critical 9.8)
- [CVE-2019-1937](https://insights.sbomify.com/CVE-2019-1937/): Auth bypass in Cisco Unified Computing System Director (critical 9.8)
- [CVE-2019-1974](https://insights.sbomify.com/CVE-2019-1974/): Auth bypass in Cisco Unified Computing System Director (critical 9.8)
- [CVE-2015-6259](https://insights.sbomify.com/CVE-2015-6259/): Path traversal in n/a (critical 9.4)
- [CVE-2019-1864](https://insights.sbomify.com/CVE-2019-1864/): Cisco Integrated Management Controller Command Injection Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1936 and fix it if it is affected.

What it is: CVE-2019-1936 is a high-severity command injection vulnerability in Cisco Unified Computing System Director, published on 21 Aug 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-1936 exists.

Affected product: Cisco Unified Computing System Director. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-1936/ (Markdown: https://insights.sbomify.com/CVE-2019-1936/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1936
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1936
- OSV: https://osv.dev/vulnerability/CVE-2019-1936

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-1936/
Summaries are generated and may contain mistakes; the official description above is the record.