# CVE-2020-15368: Privilege escalation in n/a

> A local attacker can exploit improper access restrictions in the ASRock RGB Driver to trigger a system crash or escalate privileges.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 29 Jun 2020
- **Updated:** 28 May 2026
- **Also known as:** GHSA-7387-h76h-9m29

## What is CVE-2020-15368?

CVE-2020-15368 is a medium-severity vulnerability in n/a, published on 29 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

AsrDrv103.sys in the ASRock RGB Driver does not properly restrict access from user space, as demonstrated by triggering a triple fault via a request to zero CR3.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2020-15368?

It affects 1 product.


Products: Asrock Rgb Driver Firmware.

## How do I fix CVE-2020-15368?

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

## Is CVE-2020-15368 being exploited?

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

Public exploit code:

- CVE-2020-15368, aka "How to exploit a vulnerable driver" (github_poc): https://github.com/stong/CVE-2020-15368
- arbitrary code execution with CVE-2020-15368 (github_poc): https://github.com/R7flex/asrockploit
- Reverse engineering research of ASRock AsrDrv103.sys (CVE-2020-15368), covering its driver interface, encrypted request protocol, and privileged hardware access primitives. (github_poc): https://github.com/egorrsp/CVE-2020-15368-AsrDrv103-research

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15368 and fix it if it is affected.

What it is: CVE-2020-15368 is a medium-severity vulnerability in n/a, published on 29 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-15368 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-2020-15368/ (Markdown: https://insights.sbomify.com/CVE-2020-15368/index.md)
```

## Sources

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

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