Loading vulnerability…
CVE-2024-30804 is a vulnerability in the DeviceIoControl component of ASUS Fan_Xpert prior to version 10013. The flaw allows an attacker to execute arbitrary code by sending specially crafted IOCTL requests to the vulnerable component. This likely results from insufficient validation of user-supplied data in IOCTL handlers, enabling privilege escalation or code execution in the context of the service.
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 is a proof-of-concept (PoC) exploit for a local privilege escalation vulnerability in the ASUS AsInsHelp64.sys driver (CVE-2024-30804), affecting ASUS Fan Xpert software versions prior to 10013 on Windows 10/11 x64. The exploit is implemented in C++ (main.cpp) and is designed to be built as a Windows console application. It abuses an IOCTL exposed by the driver that allows arbitrary physical memory mapping, enabling the attacker to overwrite kernel memory structures without proper permission checks. The exploit requires the user to retrieve certain kernel addresses (EPROCESS, CR3, and SYSTEM token) using WinDbg, which are then input into the tool. The tool locates the current process in the kernel's process list, calculates the physical address of its token, and overwrites it with the SYSTEM token value, effectively granting SYSTEM privileges. Upon success, it spawns a SYSTEM-level command prompt. The repository contains standard project files for a Visual Studio C++ project, with the main exploit logic in main.cpp. The only fingerprintable endpoint is the device file \\.\AsInsHelp, which is the interface to the vulnerable driver. The exploit is operational and demonstrates a real privilege escalation, but requires manual steps and is not fully weaponized.
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.