# CVE-2018-0148: Cross-site request forgery in Cisco UCS Director and Cisco Integrated Management Controller Supervisor

> Unauthenticated remote attackers can perform arbitrary actions on Cisco UCS Director via CSRF by tricking users into clicking malicious links.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Feb 2018
- **Updated:** 2 Dec 2024
- **Also known as:** GHSA-84jm-frjh-4hjv

## What is CVE-2018-0148?

CVE-2018-0148 is a high-severity vulnerability in Cisco UCS Director and Cisco Integrated Management Controller Supervisor, published on 22 Feb 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the web-based management interface of Cisco UCS Director Software and Cisco Integrated Management Controller (IMC) Supervisor Software could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack and perform arbitrary actions on an affected system. The vulnerability is due to insufficient CSRF protection by the web-based management interface of the affected software. An attacker could exploit this vulnerability by persuading a user of the affected interface to click a malicious link. A successful exploit could allow the attacker to perform arbitrary actions, via the user's web browser and with the user's privileges, on an affected system. Cisco Bug IDs: CSCvf71929.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Cisco Ucs Director.

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

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

## Is CVE-2018-0148 being exploited?

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

## Other vulnerabilities in Cisco UCS Director and Cisco Integrated Management Controller Supervisor

- [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-0148 and fix it if it is affected.

What it is: CVE-2018-0148 is a high-severity vulnerability in Cisco UCS Director and Cisco Integrated Management Controller Supervisor, published on 22 Feb 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-0148 in the wild and no public exploit code.

Affected product: Cisco UCS Director and Cisco Integrated Management Controller Supervisor. 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-0148/ (Markdown: https://insights.sbomify.com/CVE-2018-0148/index.md)
```

## Sources

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

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