# CVE-2013-5493: Command injection in n/a

> Local attackers can bypass access restrictions in the diagnostic module to execute arbitrary commands on Cisco VXC 6000 devices.

- **Severity:** Medium 6.8 (`AV:L/AC:L/Au:S/C:C/I:C/A:C`)
- **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:** 13 Sep 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f4mr-hxmj-wqjr

## What is CVE-2013-5493?

CVE-2013-5493 is a medium-severity command injection vulnerability in n/a, published on 13 Sep 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The diagnostic module in the firmware on Cisco Virtualization Experience Client 6000 devices allows local users to bypass intended access restrictions and execute arbitrary commands via unspecified vectors, aka Bug ID CSCug68407.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2013-5493?

It affects 2 products.


Products: Cisco Virtualization Experience Client 6000, Cisco Virtualization Experience Client 6000 Series Firmware.

## How do I fix CVE-2013-5493?

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

## Is CVE-2013-5493 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-3408](https://insights.sbomify.com/CVE-2013-3408/): Privilege escalation in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5493 and fix it if it is affected.

What it is: CVE-2013-5493 is a medium-severity command injection vulnerability in n/a, published on 13 Sep 2013. 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-2013-5493 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-2013-5493/ (Markdown: https://insights.sbomify.com/CVE-2013-5493/index.md)
```

## Sources

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

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