# CVE-2014-8170: Command injection in n/a

> Authenticated users or local attackers can execute arbitrary commands via semicolon injection in Red Hat Virtualization Node configuration functions.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pw85-7r2r-g8j9

## What is CVE-2014-8170?

CVE-2014-8170 is a high-severity command injection vulnerability in n/a, published on 25 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ovirt_safe_delete_config in ovirtfunctions.py and other unspecified locations in ovirt-node 3.0.0-474-gb852fd7 as packaged in Red Hat Enterprise Virtualization 3 do not properly quote input strings, which allows remote authenticated users and physically proximate attackers to execute arbitrary commands via a ; (semicolon) in an input string.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2014-8170?

It affects 1 product.


Products: Ovirt Ovirt-Node.

## How do I fix CVE-2014-8170?

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

## Is CVE-2014-8170 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8170 and fix it if it is affected.

What it is: CVE-2014-8170 is a high-severity command injection vulnerability in n/a, published on 25 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-8170 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-2014-8170/ (Markdown: https://insights.sbomify.com/CVE-2014-8170/index.md)
```

## Sources

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

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