# CVE-2019-9730: Privilege escalation in n/a

> A local attacker can escalate privileges to modify the Windows Registry via an unpublished API in the Synaptics Sound Device driver.

- **Severity:** High 8.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/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:** 5 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-93vv-c929-gw49

## What is CVE-2019-9730?

CVE-2019-9730 is a high-severity vulnerability in n/a, published on 5 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect access control in the CxUtilSvc component of the Synaptics Sound Device drivers prior to version 2.29 allows a local attacker to increase access privileges to the Windows Registry via an unpublished API.

## Which versions are affected by CVE-2019-9730?

It affects 1 product.


Products: Synaptics Sound Device.

## How do I fix CVE-2019-9730?

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

## Is CVE-2019-9730 being exploited?

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

Public exploit code:

- Synaptics Audio Driver LPE (github_poc): https://github.com/jthuraisamy/CVE-2019-9730

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9730 and fix it if it is affected.

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

## Sources

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

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