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

> A local attacker can trigger an out-of-bounds read in the Razer Synapse driver via a crafted IOCTL, potentially causing a crash or leaking memory.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 2 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xhrx-96p4-r9ww

## What is CVE-2017-9770?

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

### Official description

A specially crafted IOCTL can be issued to the rzpnk.sys driver in Razer Synapse that can cause an out of bounds read operation to occur due to a field within the IOCTL data being used as a length.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Razerzone Razer Synapse.

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

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

## Is CVE-2017-9770 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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