# CVE-2018-0453: Command injection in Cisco FireSIGHT System Software

> An authenticated local attacker with root privileges can execute arbitrary CLI commands on Cisco Firepower devices, leading to configuration changes or file deletion.

- **Severity:** High 8.2 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2018
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-8584-j2xq-qr4w

## What is CVE-2018-0453?

CVE-2018-0453 is a high-severity command injection vulnerability in Cisco Secure Firewall Threat Defense, published on 5 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the Sourcefire tunnel control channel protocol in Cisco Firepower System Software running on Cisco Firepower Threat Defense (FTD) sensors could allow an authenticated, local attacker to execute specific CLI commands with root privileges on the Cisco Firepower Management Center (FMC), or through Cisco FMC on other Firepower sensors and devices that are controlled by the same Cisco FMC. To send the commands, the attacker must have root privileges for at least one affected sensor or the Cisco FMC. The vulnerability exists because the affected software performs insufficient checks for certain CLI commands, if the commands are executed via a Sourcefire tunnel connection. An attacker could exploit this vulnerability by authenticating with root privileges to a Firepower sensor or Cisco FMC, and then sending specific CLI commands to the Cisco FMC or through the Cisco FMC to another Firepower sensor via the Sourcefire tunnel connection. A successful exploit could allow the attacker to modify device configurations or delete files on the device that is running Cisco FMC Software or on any Firepower device that is managed by Cisco FMC.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-264

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

It affects 1 product.


Products: Cisco Secure Firewall Threat Defense.

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

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

## Is CVE-2018-0453 being exploited?

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

## Other vulnerabilities in Cisco Secure Firewall Threat Defense

- [CVE-2024-20412](https://insights.sbomify.com/CVE-2024-20412/): Hardcoded credentials in Cisco Firepower Threat Defense Software (critical 9.3)
- [CVE-2024-20330](https://insights.sbomify.com/CVE-2024-20330/): Memory corruption in Cisco Firepower Threat Defense Software (high 8.6)
- [CVE-2024-20339](https://insights.sbomify.com/CVE-2024-20339/): Cisco Firepower Threat Defense Software for Firepower 2100 Series TLS Denial of Service Vulnerability (high 8.6)
- [CVE-2024-20351](https://insights.sbomify.com/CVE-2024-20351/): Cisco Firepower Threat Defense Software Snort Firewall Denial of Service Vulnerability (high 8.6)
- [CVE-2023-20083](https://insights.sbomify.com/CVE-2023-20083/): Denial of service in Cisco Firepower Threat Defense Software (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-0453 is a high-severity command injection vulnerability in Cisco Secure Firewall Threat Defense, published on 5 Oct 2018. 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-2018-0453 in the wild and no public exploit code.

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

## Sources

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

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