# CVE-2019-16650: Race condition in n/a

> An attacker can hijack virtual media sessions via a race condition in Supermicro BMCs, gaining unauthorized control over virtual USB devices.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vjvg-9vgw-x699

## What is CVE-2019-16650?

CVE-2019-16650 is a critical vulnerability in n/a, published on 21 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On Supermicro X10 and X11 products, a client's access privileges may be transferred to a different client that later has the same socket file descriptor number. In opportunistic circumstances, an attacker can simply connect to the virtual media service, and then connect virtual USB devices to the server managed by the BMC.

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

It affects 263 products.


Products: Supermicro A1sa2-2750f Firmware, Supermicro A1sai-2550f Firmware, Supermicro A1sai-2750f Firmware, Supermicro A1sam-2550f Firmware, Supermicro A1sam-2750f Firmware, Supermicro A1sri-2358f Firmware, Supermicro A1sri-2558f Firmware, Supermicro A1sri-2758f Firmware, Supermicro A1srm-2558f Firmware, Supermicro A1srm-2758f Firmware, Supermicro A1srm-Ln5f-2358 Firmware, Supermicro A1srm-Ln7f-2358 Firmware, Supermicro A1srm-Ln7f-2758 Firmware, Supermicro B10drc-N Firmware, Supermicro B10drc Firmware, Supermicro B10drg-Ibf2 Firmware, Supermicro B10drg-Ibf Firmware, Supermicro B10drg-Tp Firmware, Supermicro B10dri-N Firmware, Supermicro B10dri Firmware and 243 more.

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

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

## Is CVE-2019-16650 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16649](https://insights.sbomify.com/CVE-2019-16649/): Weak cryptography in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16650 is a critical vulnerability in n/a, published on 21 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-16650 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-16650/ (Markdown: https://insights.sbomify.com/CVE-2019-16650/index.md)
```

## Sources

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

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