# CVE-2014-8750: Race condition in n/a

> Authenticated users can access unintended VNC consoles via a race condition in the VMware driver, potentially exposing sensitive instance data.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2pcw-fgm2-4xh2, RHSA-2014:1689

## What is CVE-2014-8750?

CVE-2014-8750 is a medium-severity vulnerability in n/a, published on 15 Oct 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Race condition in the VMware driver in OpenStack Compute (Nova) before 2014.1.4 and 2014.2 before 2014.2rc1 allows remote authenticated users to access unintended consoles by spawning an instance that triggers the same VNC port to be allocated to two different instances.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openstack-nova` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-2.el6ost |
| `openstack-nova-api` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-2.el6ost |
| `openstack-nova-cells` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-2.el6ost |
| `openstack-nova-cert` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-2.el6ost |
| `openstack-nova-common` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-2.el6ost |
| `openstack-nova-compute` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-2.el6ost |
| `openstack-nova-conductor` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-2.el6ost |
| `openstack-nova-console` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-2.el6ost |
| `openstack-nova-doc` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-2.el6ost |
| `openstack-nova-network` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-2.el6ost |
| `openstack-nova-novncproxy` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-2.el6ost |
| `openstack-nova-objectstore` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-2.el6ost |
| `openstack-nova-scheduler` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-2.el6ost |
| `python-nova` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-2.el6ost |

Products: Openstack Nova.

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

Upgrade to a fixed version.

## Is CVE-2014-8750 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-7214](https://insights.sbomify.com/CVE-2017-7214/): OpenStack Nova logs sensitive context from notification exceptions (critical 9.8)
- [CVE-2017-17051](https://insights.sbomify.com/CVE-2017-17051/): OpenStack Nova DoS by rebuilding the same instance with a new image multiple times (high 8.6)
- [CVE-2020-17376](https://insights.sbomify.com/CVE-2020-17376/): OpenStack Nova Live migration fails to update persistent domain XML (high 8.3)
- [CVE-2017-18191](https://insights.sbomify.com/CVE-2017-18191/): OpenStack Nova Denial of service attack on the compute host (high 7.5)
- [CVE-2015-3280](https://insights.sbomify.com/CVE-2015-3280/): OpenStack Compute (nova) allows remote authenticated users to cause a denial of service (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8750 is a medium-severity vulnerability in n/a, published on 15 Oct 2014. 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-8750 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-8750/ (Markdown: https://insights.sbomify.com/CVE-2014-8750/index.md)
```

## Sources

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

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