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

> Authenticated attackers can execute arbitrary OS commands via Virtual Media feature, enabling persistent backdoors on Supermicro IPMI systems.

- **Severity:** High 8.8 (`CVSS:3.1/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:** 8 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8rgw-25fw-5m5f

## What is CVE-2019-19642?

CVE-2019-19642 is a high-severity command injection vulnerability in n/a, published on 8 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On SuperMicro X8STi-F motherboards with IPMI firmware 2.06 and BIOS 02.68, the Virtual Media feature allows OS Command Injection by authenticated attackers who can send HTTP requests to the IPMI IP address. This requires a POST to /rpc/setvmdrive.asp with shell metacharacters in ShareHost or ShareName. The attacker can achieve a persistent backdoor.

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

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

It affects 2 products.


Products: Supermicro X8sti-F Bios, Supermicro X8sti-F Firmware.

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

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

## Is CVE-2019-19642 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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