# CVE-2017-3801: Privilege escalation in Cisco UCS Director versions 6.0.0.0 and 6.0.0.1

> Authenticated local attackers can escalate privileges to execute arbitrary workflow items by enabling Developer Mode in Cisco UCS Director.

- **Severity:** High 8.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f4q6-c8q7-9mcw

## What is CVE-2017-3801?

CVE-2017-3801 is a high-severity vulnerability in Cisco UCS Director versions 6.0.0.0 and 6.0.0.1, published on 15 Feb 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the web-based GUI of Cisco UCS Director 6.0.0.0 and 6.0.0.1 could allow an authenticated, local attacker to execute arbitrary workflow items with just an end-user profile, a Privilege Escalation Vulnerability. The vulnerability is due to improper role-based access control (RBAC) after the Developer Menu is enabled in Cisco UCS Director. An attacker could exploit this vulnerability by enabling Developer Mode for his/her user profile with an end-user profile and then adding new catalogs with arbitrary workflow items to his/her profile. An exploit could allow an attacker to perform any actions defined by these workflow items, including actions affecting other tenants. Cisco Bug IDs: CSCvb64765.

Weakness: CWE-863 (Incorrect Authorization), CWE-264

## Which versions are affected by CVE-2017-3801?

It affects 1 product.


Products: Cisco Unified Computing System Director.

## How do I fix CVE-2017-3801?

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

## Is CVE-2017-3801 being exploited?

There is no known exploitation of CVE-2017-3801 in the wild and no public exploit code.

## Other vulnerabilities in Cisco UCS Director versions 6.0.0.0 and 6.0.0.1

- [CVE-2018-0238](https://insights.sbomify.com/CVE-2018-0238/): Auth bypass in Cisco UCS Director (critical 9.9)
- [CVE-2018-0219](https://insights.sbomify.com/CVE-2018-0219/): Cross-site scripting in Cisco UCS Director (medium 6.1)
- [CVE-2017-3868](https://insights.sbomify.com/CVE-2017-3868/): Cross-site scripting in Cisco UCS Director (medium 6.1)
- [CVE-2017-3817](https://insights.sbomify.com/CVE-2017-3817/): Missing authorization in Cisco UCS Director (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3801 and fix it if it is affected.

What it is: CVE-2017-3801 is a high-severity vulnerability in Cisco UCS Director versions 6.0.0.0 and 6.0.0.1, published on 15 Feb 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3801 in the wild and no public exploit code.

Affected product: Cisco UCS Director versions 6.0.0.0 and 6.0.0.1. 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-2017-3801/ (Markdown: https://insights.sbomify.com/CVE-2017-3801/index.md)
```

## Sources

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

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