# CVE-2019-12491: Command injection in n/a

> An attacker with control of one server can execute arbitrary root commands on other servers in the OnApp cloud environment.

- **Severity:** Medium 6.6 (`CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4hwf-q27j-2mmh

## What is CVE-2019-12491?

CVE-2019-12491 is a medium-severity command injection vulnerability in n/a, published on 19 Jun 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

OnApp before 5.0.0-88, 5.5.0-93, and 6.0.0-196 allows an attacker to run arbitrary commands with root privileges on servers managed by OnApp for XEN/KVM hypervisors. To exploit the vulnerability an attacker has to have control of a single server on a given cloud (e.g. by renting one). From the source server, the attacker can craft any command and trigger the OnApp platform to execute that command with root privileges on a target server.

## Which versions are affected by CVE-2019-12491?

It affects 1 product.


Products: Onapp Onapp.

## How do I fix CVE-2019-12491?

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

## Is CVE-2019-12491 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12491 and fix it if it is affected.

What it is: CVE-2019-12491 is a medium-severity command injection vulnerability in n/a, published on 19 Jun 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12491 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-2019-12491/ (Markdown: https://insights.sbomify.com/CVE-2019-12491/index.md)
```

## Sources

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

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