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

> Remote attackers can execute arbitrary commands via shell metacharacters in the fileDate parameter of vmtadmin.cgi.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vcc8-pv5w-mvqj

## What is CVE-2014-5073?

CVE-2014-5073 is a high-severity command injection vulnerability in n/a, published on 29 Aug 2014. It can be exploited over the network, with no action from the victim.

### Official description

vmtadmin.cgi in VMTurbo Operations Manager before 4.6 build 28657 allows remote attackers to execute arbitrary commands via shell metacharacters in the fileDate parameter in a DOWN call.

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

It affects 1 product.


Products: Vmturbo Operations Manager.

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

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

## Is CVE-2014-5073 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-5073 exists.

Public exploit code:

- VMTurbo Operations Manager vmtadmin.cgi Remote Command Execution (metasploit)
- VMTurbo Operations Manager 4.6 - 'vmtadmin.cgi' Remote Command Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-3806](https://insights.sbomify.com/CVE-2014-3806/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5073 is a high-severity command injection vulnerability in n/a, published on 29 Aug 2014. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-5073 exists.

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-5073/ (Markdown: https://insights.sbomify.com/CVE-2014-5073/index.md)
```

## Sources

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

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