# CVE-2017-15303: Memory corruption in n/a

> Local attackers can exploit an arbitrary memory write in the CPU-Z kernel driver to escalate privileges and execute code.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-92jj-g6qw-xrrw

## What is CVE-2017-15303?

CVE-2017-15303 is a high-severity memory corruption vulnerability in n/a, published on 16 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In CPUID CPU-Z before 1.43, there is an arbitrary memory write that results directly in elevation of privileges, because any program running on the local machine (while CPU-Z is running) can issue an ioctl 0x9C402430 call to the kernel-mode driver (e.g., cpuz141_x64.sys for version 1.41).

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2017-15303?

It affects 1 product.


Products: Cpuid Cpu-Z.

## How do I fix CVE-2017-15303?

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

## Is CVE-2017-15303 being exploited?

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

Public exploit code:

- Multi-purpose proof-of-concept tool based on CPU-Z CVE-2017-15303 (github_poc): https://github.com/hfiref0x/Stryker

## Other vulnerabilities in n/a

- [CVE-2017-15302](https://insights.sbomify.com/CVE-2017-15302/): Missing authorization in n/a (high 7.8)
- [CVE-2025-65264](https://insights.sbomify.com/CVE-2025-65264/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15303 and fix it if it is affected.

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

## Sources

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

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