dbcve.org
Rgb Driver FirmwareOperating system · Asrock

CVE-2020-15368

MEDIUM · 5.5 CVSS v3.1 Published 2020-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The ASRock RGB LED driver (AsrDrv103.sys) fails to validate that IOCTL requests originate from privileged code, allowing unprivileged user-space applications to issue kernel-mode operations that can zero the CR3 control register. CR3 controls memory paging structures; zeroing it causes the CPU to lose its memory mapping, triggering a triple fault and system crash. This is an insecure direct object reference / improper access control vulnerability in a kernel-mode driver.

MitigationApply any available driver update from ASRock that implements proper access control checks on IOCTL requests. If no update is available, remove the driver or use application whitelisting to restrict which processes can communicate with the driver.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rgb Driver FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if the ASRock RGB LED driver is installed
    Search for AsrDrv103.sys in the Windows\System32\drivers folder, or query the Windows driver database using 'driverquery /v | findstr -i asrock' or 'sc query asrled'
    Affected if The file AsrDrv103.sys exists on the system or the driver appears in driver listings
  2. Verify the driver is currently loaded and running
    Run 'sc query asrled' or check Device Manager under 'System devices' for ASRock RGB LED entries, or use 'driverquery /v' to list loaded drivers
    Affected if The driver shows a STATE of RUNNING or is listed as an active kernel driver
  3. Confirm the driver handles are accessible to unprivileged users
    Use Sysinternals Process Explorer or Run 'accesschk.exe -kv c:\Windows\System32\drivers\AsrDrv103.sys' (if available) to check file permissions, or verify that any user in the 'Users' group can send IOCTL requests to the device
    Affected if Non-admin users have write or execute access to the driver device object (\Device\AsrLed or similar) or the driver file lacks restrictive ACLs
  4. Check for unsigned or older driver versions
    Right-click AsrDrv103.sys, go to Properties > Digital Signatures tab, or run 'sigcheck.exe -a AsrDrv103.sys' to inspect the version and signature
    Affected if The driver is unsigned, has a version that has not been patched, or shows no evidence of recent security updates from ASRock
  5. Verify no application whitelisting is blocking driver communication
    Review Windows Defender Application Control (WDAC) policies, AppLocker rules, or third-party endpoint protection policies to see if AsrDrv103.sys communication is restricted
    Affected if There are no enforcement policies preventing unprivileged processes from communicating with the driver

If the ASRock RGB LED driver (AsrDrv103.sys) is installed and running with default permissions, the system is vulnerable because unprivileged users can issue privileged IOCTL operations to the driver.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply any available driver update from ASRock that implements proper access control checks on IOCTL requests. If no update is available, remove the driver or use application whitelisting to restrict which processes can communicate with the driver.

Fix this in Rgb Driver Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-15368 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-15368 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data