# CVE-2018-0365: Cross-site request forgery in Cisco Firepower Management Center unknown

> Unauthenticated remote attackers can perform arbitrary actions on Cisco Firepower Management Center 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:** 21 Jun 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-hcc8-28g7-82jh

## What is CVE-2018-0365?

CVE-2018-0365 is a high-severity vulnerability in Cisco Secure Firewall Management Center, published on 21 Jun 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 Firepower Management Center could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack and perform arbitrary actions on an affected device. The vulnerability is due to insufficient CSRF protections for the web-based management interface of the affected device. An attacker could exploit this vulnerability by persuading a user of the interface to follow a malicious link. A successful exploit could allow the attacker to perform arbitrary actions on the targeted device via a web browser and with the privileges of the user. Cisco Bug IDs: CSCvb19750.

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

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

It affects 32 products.


Products: Cisco Amp 7150 Firmware, Cisco Amp 8150 Firmware, Cisco Firepower Appliance 7010 Firmware, Cisco Firepower Appliance 7020 Firmware, Cisco Firepower Appliance 7030 Firmware, Cisco Firepower Appliance 7050 Firmware, Cisco Firepower Appliance 7110 Firmware, Cisco Firepower Appliance 7115 Firmware, Cisco Firepower Appliance 7120 Firmware, Cisco Firepower Appliance 7125 Firmware, Cisco Firepower Appliance 8120 Firmware, Cisco Firepower Appliance 8130 Firmware, Cisco Firepower Appliance 8140 Firmware, Cisco Firepower Appliance 8250 Firmware, Cisco Firepower Appliance 8260 Firmware, Cisco Firepower Appliance 8270 Firmware, Cisco Firepower Appliance 8290 Firmware, Cisco Firepower Appliance 8350 Firmware, Cisco Firepower Appliance 8360 Firmware, Cisco Firepower Appliance 8370 Firmware and 12 more.

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

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

## Is CVE-2018-0365 being exploited?

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

## Other vulnerabilities in Cisco Secure Firewall Management Center

- [CVE-2019-15268](https://insights.sbomify.com/CVE-2019-15268/): Cisco Firepower Management Center Multiple Cross-Site Scripting Vulnerabilities (medium 4.8)
- [CVE-2019-15269](https://insights.sbomify.com/CVE-2019-15269/): Cisco Firepower Management Center Multiple Cross-Site Scripting Vulnerabilities (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-0365 is a high-severity vulnerability in Cisco Secure Firewall Management Center, published on 21 Jun 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-0365 in the wild and no public exploit code.

Affected product: Cisco Secure Firewall Management Center. 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-0365/ (Markdown: https://insights.sbomify.com/CVE-2018-0365/index.md)
```

## Sources

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

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