# CVE-2016-5605: Unspecified vulnerability in the Oracle VM VirtualBox component before 5.1.4 in Oracle Virtualization allows remote attackers to affect conf


- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 25 Oct 2016
- **Updated:** 10 Oct 2024
- **Also known as:** GHSA-h5vc-c65p-cgj9

## What is CVE-2016-5605?

CVE-2016-5605 is a critical vulnerability in Oracle Vm Virtualbox, published on 25 Oct 2016. 

### Official description

Unspecified vulnerability in the Oracle VM VirtualBox component before 5.1.4 in Oracle Virtualization allows remote attackers to affect confidentiality and integrity via vectors related to VRDE.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-5605?

It affects 1 product.


Products: Oracle Vm Virtualbox.

## How do I fix CVE-2016-5605?

Upgrade to a fixed version.

## Is CVE-2016-5605 being exploited?

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

## Other vulnerabilities in Oracle Vm Virtualbox

- [CVE-2018-3294](https://insights.sbomify.com/CVE-2018-3294/): Privilege escalation in VM VirtualBox (critical 9.0)
- [CVE-2024-21112](https://insights.sbomify.com/CVE-2024-21112/): Privilege escalation in VM VirtualBox (high 8.8)
- [CVE-2024-21113](https://insights.sbomify.com/CVE-2024-21113/): Privilege escalation in VM VirtualBox (high 8.8)
- [CVE-2024-21114](https://insights.sbomify.com/CVE-2024-21114/): Privilege escalation in VM VirtualBox (high 8.8)
- [CVE-2024-21115](https://insights.sbomify.com/CVE-2024-21115/): Privilege escalation in VM VirtualBox (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5605 and fix it if it is affected.

What it is: CVE-2016-5605 is a critical vulnerability in Oracle Vm Virtualbox, published on 25 Oct 2016. 
Exploitation: There is no known exploitation of CVE-2016-5605 in the wild and no public exploit code.

Affected product: Oracle Vm Virtualbox. 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-2016-5605/ (Markdown: https://insights.sbomify.com/CVE-2016-5605/index.md)
```

## Sources

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

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