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

> Local attackers can escalate privileges by sending crafted IOCTL calls to the Silicon Integrated Systems Windows XP display driver.

- **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:** 16 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6437-r6f2-89jm

## What is CVE-2015-5465?

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

### Official description

Silicon Integrated Systems WindowsXP Display Manager (aka VGA Driver Manager and VGA Display Manager) 6.14.10.3930 allows local users to gain privileges via a crafted (1) 0x96002400 or (2) 0x96002404 IOCTL call.

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

It affects 1 product.


Products: Sis Windows Vga Display Manager.

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

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

## Is CVE-2015-5465 being exploited?

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

Public exploit code:

- SiS Windows VGA Display Manager 6.14.10.3930 - Write-What-Where (PoC) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-5465 is a high-severity vulnerability in n/a, published on 16 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-5465 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-5465/ (Markdown: https://insights.sbomify.com/CVE-2015-5465/index.md)
```

## Sources

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

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