# CVE-2018-10709: Privilege escalation in n/a

> Local attackers can exploit exposed driver functionality to read/write CR registers, leading to privilege escalation and arbitrary code execution.

- **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:** 30 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v8wr-25mj-7jf2

## What is CVE-2018-10709?

CVE-2018-10709 is a high-severity vulnerability in n/a, published on 30 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.210, F-Stream before v3.0.210, and RestartToUEFI before v1.0.6.2 expose functionality to read and write CR register values. This could be leveraged in a number of ways to ultimately run code with elevated privileges.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2018-10709?

It affects 4 products.


Products: Asrock A-Tuning, Asrock F-Stream, Asrock Restart to Uefi, Asrock Rgbled.

## How do I fix CVE-2018-10709?

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

## Is CVE-2018-10709 being exploited?

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

Public exploit code:

- ASRock Drivers - Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-10711](https://insights.sbomify.com/CVE-2018-10711/): Privilege escalation in n/a (high 7.8)
- [CVE-2018-10712](https://insights.sbomify.com/CVE-2018-10712/): Privilege escalation in n/a (high 7.8)
- [CVE-2018-10710](https://insights.sbomify.com/CVE-2018-10710/): Privilege escalation in n/a (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10709 and fix it if it is affected.

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

## Sources

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

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