# CVE-2018-15405: Missing authorization in Cisco Unified Computing System Director

> An authenticated attacker can view sensitive information belonging to other users due to improper authorization checks in the web interface.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2018
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-rwrr-92p6-jxrh

## What is CVE-2018-15405?

CVE-2018-15405 is a medium-severity missing authorization vulnerability in Cisco Unified Computing System Director, published on 5 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the web interface for specific feature sets of Cisco Integrated Management Controller (IMC) Supervisor and Cisco UCS Director could allow an authenticated, remote attacker to access sensitive information. The vulnerability is due to an authorization check that does not properly include the access level of the web interface user. An attacker who has valid application credentials could exploit this vulnerability by sending a crafted HTTP request to the web interface. A successful exploit could allow the attacker to view sensitive information that belongs to other users. The attacker could then use this information to conduct additional reconnaissance attacks.

Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2018-15405?

It affects 1 product.


Products: Cisco Ucs Director.

## How do I fix CVE-2018-15405?

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

## Is CVE-2018-15405 being exploited?

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

## Other vulnerabilities in Cisco Unified Computing System Director

- [CVE-2020-3239](https://insights.sbomify.com/CVE-2020-3239/): Multiple Vulnerabilities in Cisco UCS Director and Cisco UCS Director Express for Big Data (critical 9.8)
- [CVE-2020-3240](https://insights.sbomify.com/CVE-2020-3240/): Multiple Vulnerabilities in Cisco UCS Director and Cisco UCS Director Express for Big Data (critical 9.8)
- [CVE-2020-3243](https://insights.sbomify.com/CVE-2020-3243/): Multiple Vulnerabilities in Cisco UCS Director and Cisco UCS Director Express for Big Data (critical 9.8)
- [CVE-2020-3247](https://insights.sbomify.com/CVE-2020-3247/): Multiple Vulnerabilities in Cisco UCS Director and Cisco UCS Director Express for Big Data (critical 9.8)
- [CVE-2020-3248](https://insights.sbomify.com/CVE-2020-3248/): Multiple Vulnerabilities in Cisco UCS Director and Cisco UCS Director Express for Big Data (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-15405 and fix it if it is affected.

What it is: CVE-2018-15405 is a medium-severity missing authorization vulnerability in Cisco Unified Computing System Director, published on 5 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-15405 in the wild and no public exploit code.

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-2018-15405/ (Markdown: https://insights.sbomify.com/CVE-2018-15405/index.md)
```

## Sources

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

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