# CVE-2015-4186: Command injection in n/a

> Local attackers with administrative access can execute arbitrary OS commands via crafted input in the diagnostics subsystem of Cisco VXC Client devices.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 17 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xffw-rwp4-xcg6

## What is CVE-2015-4186?

CVE-2015-4186 is a high-severity command injection vulnerability in n/a, published on 17 Jun 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The diagnostics subsystem in the administrative web interface on Cisco Virtualization Experience (aka VXC) Client 6215 devices with firmware 11.2(27.4) allows local users to gain privileges for OS command execution via a crafted option value, aka Bug ID CSCug54412.

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

## Which versions are affected by CVE-2015-4186?

It affects 1 product.


Products: Cisco Virtualization Experience Client 6000 Series Firmware.

## How do I fix CVE-2015-4186?

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

## Is CVE-2015-4186 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4186 and fix it if it is affected.

What it is: CVE-2015-4186 is a high-severity command injection vulnerability in n/a, published on 17 Jun 2015. 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-2015-4186 in the wild and no public exploit code.

Affected product: n/a. 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-2015-4186/ (Markdown: https://insights.sbomify.com/CVE-2015-4186/index.md)
```

## Sources

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

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