# CVE-2018-0214: Command injection in Cisco Identity Services Engine

> Authenticated local attackers can execute arbitrary OS commands via crafted CLI input in Cisco ISE, bypassing user restrictions.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Mar 2018
- **Updated:** 2 Dec 2024
- **Also known as:** GHSA-2qrx-vr2m-vjfp

## What is CVE-2018-0214?

CVE-2018-0214 is a medium-severity command injection vulnerability in Cisco Identity Services Engine, published on 8 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in certain CLI commands of Cisco Identity Services Engine (ISE) could allow an authenticated, local attacker to execute arbitrary commands on the host operating system with the privileges of the local user, aka Command Injection. These commands should have been restricted from this user. The vulnerability is due to insufficient input validation of CLI command user input. An attacker could exploit this vulnerability by authenticating to the targeted device and issuing a CLI command with crafted user input. A successful exploit could allow the attacker to execute arbitrary commands on the affected system that should be restricted. The attacker would need to have valid user credentials for the device. Cisco Bug IDs: CSCvf49844.

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

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

It affects 1 product.


Products: Cisco Identity Services Engine.

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

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

## Is CVE-2018-0214 being exploited?

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

## Other vulnerabilities in Cisco Identity Services Engine

- [CVE-2026-76460](https://insights.sbomify.com/CVE-2026-76460/): Cisco Identity Services Engine Incorrect Use of Privileged APIs (critical 10.0, exploited in the wild)
- [CVE-2025-20337](https://insights.sbomify.com/CVE-2025-20337/): Cisco Identity Services Engine Injection (critical 10.0, exploited in the wild)
- [CVE-2025-20281](https://insights.sbomify.com/CVE-2025-20281/): Cisco Identity Services Engine Injection (critical 10.0, exploited in the wild)
- [CVE-2026-20130](https://insights.sbomify.com/CVE-2026-20130/): Cisco Identity Services Engine Hardening Release - Improper Neutralization Vulnerabilities (critical 10.0)
- [CVE-2026-20192](https://insights.sbomify.com/CVE-2026-20192/): Cisco Identity Services Engine Hardening Release - Access Control Vulnerabilities (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-0214 is a medium-severity command injection vulnerability in Cisco Identity Services Engine, published on 8 Mar 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-0214 in the wild and no public exploit code.

Affected product: Cisco Identity Services Engine. 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-0214/ (Markdown: https://insights.sbomify.com/CVE-2018-0214/index.md)
```

## Sources

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

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