# CVE-2015-6923: Privilege escalation in n/a

> Local attackers can exploit the ndvbs module to write to arbitrary physical memory and escalate privileges to root.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2c42-4jvc-gq6p

## What is CVE-2015-6923?

CVE-2015-6923 is a high-severity vulnerability in n/a, published on 21 Sep 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The ndvbs module in VBox Communications Satellite Express Protocol 2.3.17.3 allows local users to write to arbitrary physical memory locations and gain privileges via a 0x00000ffd ioctl call.

## Which versions are affected by CVE-2015-6923?

It affects 1 product.


Products: Vboxcomm Satellite Express Protocol.

## How do I fix CVE-2015-6923?

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

## Is CVE-2015-6923 being exploited?

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

Public exploit code:

- VBox Satellite Express 2.3.17.3 - Arbitrary Write (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6923 and fix it if it is affected.

What it is: CVE-2015-6923 is a high-severity vulnerability in n/a, published on 21 Sep 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6923 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-2015-6923/ (Markdown: https://insights.sbomify.com/CVE-2015-6923/index.md)
```

## Sources

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

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