# CVE-2017-9769: Privilege escalation in n/a

> A local attacker can exploit a flaw in the Razer Synapse driver to open handles to arbitrary processes, leading to privilege escalation.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h552-jrvp-gg25

## What is CVE-2017-9769?

CVE-2017-9769 is a critical vulnerability in n/a, published on 2 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A specially crafted IOCTL can be issued to the rzpnk.sys driver in Razer Synapse 2.20.15.1104 that is forwarded to ZwOpenProcess allowing a handle to be opened to an arbitrary process.

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

It affects 1 product.


Products: Razer Synapse.

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

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

## Is CVE-2017-9769 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-9769 exists.

Public exploit code:

- A specially crafted IOCTL can be issued to the rzpnk.sys driver in Razer Synapse 2.20.15.1104 that is forwarded to ZwOpenProcess allowing a handle to be opened to an arbitrary process. (github_poc): https://github.com/kkent030315/CVE-2017-9769
- Razer Synapse rzpnk.sys ZwOpenProcess (metasploit)
- Razer Synapse 2.20.15.1104 - rzpnk.sys ZwOpenProcess (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-11652](https://insights.sbomify.com/CVE-2017-11652/): Privilege escalation in n/a (high 8.4)
- [CVE-2025-9869](https://insights.sbomify.com/CVE-2025-9869/): Razer Synapse 3 Macro Module Link Following Local Privilege Escalation Vulnerability (high 7.8)
- [CVE-2025-9870](https://insights.sbomify.com/CVE-2025-9870/): Razer Synapse 3 RazerPhilipsHueUninstall Link Following Local Privilege Escalation Vulnerability (high 7.8)
- [CVE-2025-9871](https://insights.sbomify.com/CVE-2025-9871/): Razer Synapse 3 Chroma Connect Link Following Local Privilege Escalation Vulnerability (high 7.8)
- [CVE-2022-47631](https://insights.sbomify.com/CVE-2022-47631/): Race condition in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9769 is a critical vulnerability in n/a, published on 2 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-9769 exists.

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-9769/ (Markdown: https://insights.sbomify.com/CVE-2017-9769/index.md)
```

## Sources

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

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