# CVE-2018-0300: Path traversal in Cisco Firepower 4100 Series Next-Generation Firewall and Firepower 9300 Security Appliance unknown

> Authenticated attackers can exploit path traversal in image uploads to execute arbitrary code with root privileges on Cisco Firepower devices.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-ch88-fg86-h47v

## What is CVE-2018-0300?

CVE-2018-0300 is a high-severity path traversal vulnerability in Cisco Firepower 4100 Series Next-Generation Firewall and Firepower 9300 Security Appliance unknown, published on 21 Jun 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in the process of uploading new application images to Cisco FXOS on the Cisco Firepower 4100 Series Next-Generation Firewall (NGFW) and Firepower 9300 Security Appliance could allow an authenticated, remote attacker using path traversal techniques to create or overwrite arbitrary files on an affected device. The vulnerability is due to insufficient validation during the application image upload process. An attacker could exploit this vulnerability by creating an application image containing malicious code and installing the image on the affected device using the CLI or web-based user interface (web UI). These actions occur prior to signature verification and could allow the attacker to create and execute arbitrary code with root privileges. Note: A missing or invalid signature in the application image will cause the upload process to fail, but does not prevent the exploit. Cisco Bug IDs: CSCvc21901.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Cisco Fxos.

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

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

## Is CVE-2018-0300 being exploited?

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

## Other vulnerabilities in Cisco Firepower 4100 Series Next-Generation Firewall and Firepower 9300 Security Appliance unknown

- [CVE-2020-3171](https://insights.sbomify.com/CVE-2020-3171/): Cisco FXOS and UCS Manager Software Local Management CLI Command Injection Vulnerability (high 7.8)
- [CVE-2023-20016](https://insights.sbomify.com/CVE-2023-20016/): Cisco FXOS Software and UCS Manager Software Configuration Backup Static Key Vulnerability (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-0300 is a high-severity path traversal vulnerability in Cisco Firepower 4100 Series Next-Generation Firewall and Firepower 9300 Security Appliance unknown, published on 21 Jun 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-0300 in the wild and no public exploit code.

Affected product: Cisco Firepower 4100 Series Next-Generation Firewall and Firepower 9300 Security Appliance unknown. 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-0300/ (Markdown: https://insights.sbomify.com/CVE-2018-0300/index.md)
```

## Sources

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

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