Loading vulnerability…
CVE-2023-20562 is a vulnerability in AMD uProf where insufficient validation of the IOCTL input buffer allows an authenticated user to load an unsigned driver. This flaw exists due to improper input validation in the IOCTL handler, which can be exploited to bypass driver signature enforcement and execute arbitrary code in kernel mode.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a full exploit chain for CVE-2023-20562, targeting the AMD μProf AMDCpuProfiler.sys driver on Windows 10. The exploit is operational and demonstrates local privilege escalation (LPE) by abusing an arbitrary write vulnerability in the driver to overwrite the EPROCESS token, granting SYSTEM privileges. It also implements a BYOVD (Bring Your Own Vulnerable Driver) attack to disable Driver Signature Enforcement (DSE), allowing the loading of an unsigned, potentially malicious driver (Malicious.sys). After disabling security features, the exploit terminates processes related to 360 Total Security antivirus, effectively neutralizing its protections. The codebase is structured as a Visual Studio solution with separate projects for the exploit and the malicious driver. The main entry point is 'exploit/exploit.cpp', which provides two modes: 'LPE' for privilege escalation and 'BYOVD' for disabling security and killing AV processes. The exploit is written in C/C++ and includes embedded shellcode for process injection. Several fingerprintable endpoints are present, including device names, file paths, and process names. The exploit is not part of a framework and is a standalone operational exploit with real-world impact.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.