# CVE-2019-1935: Hardcoded credentials in Cisco Unified Computing System Director

> An attacker can log in using default SCP user credentials to execute arbitrary commands and access the database.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2019
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-c9g8-fgq6-h2wg

## What is CVE-2019-1935?

CVE-2019-1935 is a critical vulnerability in Cisco Unified Computing System Director, published on 21 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in Cisco Integrated Management Controller (IMC) Supervisor, Cisco UCS Director, and Cisco UCS Director Express for Big Data could allow an unauthenticated, remote attacker to log in to the CLI of an affected system by using the SCP User account (scpuser), which has default user credentials. The vulnerability is due to the presence of a documented default account with an undocumented default password and incorrect permission settings for that account. Changing the default password for this account is not enforced during the installation of the product. An attacker could exploit this vulnerability by using the account to log in to an affected system. A successful exploit could allow the attacker to execute arbitrary commands with the privileges of the scpuser account. This includes full read and write access to the system's database.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

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-1935?

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

## Is CVE-2019-1935 being exploited?

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

Public exploit code:

- Cisco UCS Director default scpuser password (metasploit)
- Cisco UCS Director - default scpuser password (Metasploit) (exploitdb)

## Other vulnerabilities in Cisco Unified Computing System Director

- [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)
- [CVE-2019-1865](https://insights.sbomify.com/CVE-2019-1865/): Cisco Integrated Management Controller Command Injection Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-1935 is a critical vulnerability in Cisco Unified Computing System Director, published on 21 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-1935 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-1935/ (Markdown: https://insights.sbomify.com/CVE-2019-1935/index.md)
```

## Sources

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

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