Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2020-15368: Unrestricted privileged IOCTL access in ASRock RGB Driver

Published Jun 29, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.5Medium · v3.1
EPSS1.4%72nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Asrock
IdentifiersCVE-2020-15368CWE-782

CVE-2020-15368 is an access-control vulnerability in the ASRock RGB Driver that exposes privileged operations to user-space callers through inadequately protected IOCTL commands. Exploitation can permit arbitrary physical-memory writes and execution of attacker-controlled code in the Windows kernel. A demonstrated request that sets the CR3 register to zero triggers a processor triple fault. Related ASRock IO driver builds distributed with ASRock Motherboard Utility versions 3.0.498 and earlier are also associated with the vulnerability and used by kernel-access tooling.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise Windows kernel integrity through arbitrary physical-memory writes and malicious kernel-mode code execution. The vulnerability has been used to load unsigned drivers, enabling deployment of kernel-level implants. Privileged register manipulation can also trigger a triple fault and disrupt the affected system.

Mitigation

If you can’t patch tonight, do this now.

Block known-vulnerable ASRock drivers from loading across endpoints. Harden management systems with Device Guard and Hypervisor Code Integrity, enforce least privilege, and restrict unnecessary software installation. Monitor driver-load telemetry for unexpected ASRock drivers and investigate suspicious loads, validating driver versions and signatures. Test these controls for operational compatibility before deployment.

Remediation

Patch, then assume compromise.

Update or remove vulnerable ASRock driver packages and utilities that install the affected AsrDrv*.sys family, including ASRock Motherboard Utility versions 3.0.498 and below referenced in the content. Replace them with vendor-fixed builds if available. Prevent loading of known vulnerable hashes and filenames through enterprise driver block rules and application control. If the software is not required, uninstall the associated ASRock utilities and delete the vulnerable driver from systems.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2020-15368This repository provides a full exploit and proof-of-concept for CVE-2020-15368, a vulnerability in the Asrock repackaged RWEverything driver (AsrDrv104) for Windows. The exploit consists of two main components: a custom kernel driver (MyDriver1) and a user-mode exploit (exploit.cpp). The exploit leverages the vulnerable driver's IOCTL interface, which is protected by weak encryption, to achieve arbitrary kernel memory read/write and ultimately execute arbitrary code in kernel mode. The exploit works by scanning physical memory for the driver's code, patching it to redirect execution to custom shellcode, and then restoring the original code to avoid system instability. The payload spawns a new kernel thread, allowing for privilege escalation and further kernel-level actions. The repository is structured as a Visual Studio solution with separate projects for the exploit and the custom driver. The main entry point is 'exploit/exploit.cpp', which orchestrates the attack. The exploit targets local Windows systems with the vulnerable driver installed and requires administrative privileges to interact with the device. No network endpoints are involved; all attack vectors are local. The exploit is operational and provides a working privilege escalation method for affected systems.stong · Disclosed Jun 29, 2021 · c++ · localOperationalasrockploitThis repository contains a local privilege escalation exploit for CVE-2020-15368, targeting the vulnerable ASRock AsrDrv107 driver on Windows. The exploit is implemented in C++ and consists of two main components: a user-mode launcher (AsrockPloit) and a custom kernel-mode payload (DummyDriver). The exploit works by opening a handle to the vulnerable driver (\\.\GlobalRoot\Device\AsrDrv107), crafting and encrypting IOCTL commands to read/write physical memory and control registers, and ultimately mapping and executing a custom driver (DummyDriver) in kernel space. The exploit also interacts with the Beep device (\\.\GlobalRoot\Device\Beep) to facilitate code injection. The repository includes code for parsing PDB symbols to resolve kernel function addresses, and uses a compile-time string encryption library for obfuscation. The exploit provides full kernel code execution, allowing for arbitrary actions at the highest privilege level. The structure is typical for a Windows kernel exploit: project files for Visual Studio, headers for driver communication and cryptography, and main logic in entry.cpp files for both user and kernel components.R7flex · Disclosed Aug 10, 2024 · c++ · localOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AsrockRgb Driver Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2020-15368 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2020-15368 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2020-15368?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2020-15368, the earliest disclosed Jun 29, 2021.
Is there a patch for CVE-2020-15368?
Update or remove vulnerable ASRock driver packages and utilities that install the affected AsrDrv*.sys family, including ASRock Motherboard Utility versions 3.0.498 and below referenced in the content. Replace them with vendor-fixed builds if available.
What products are affected by CVE-2020-15368?
Asrock Rgb Driver Firmware.
How severe is CVE-2020-15368?
CVE-2020-15368 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 1.4% (72nd percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware4Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.