Loading vulnerability…
The HWiNFO AMD64 Kernel driver (version 8.98 and lower) contains a vulnerability where an unprivileged user can send specially crafted IOCTL requests to the driver via the HWiNFO32 symbolic device name. If the input or output buffer pointers are NULL or contain invalid data, the driver fails to properly validate these pointers, leading to a NULL or invalid pointer dereference in kernel mode. This results in a Windows kernel panic (Blue Screen of Death). The vulnerability specifically affects IOCTL codes higher than 0x85FE2600.
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 proof-of-concept (POC) exploit for CVE-2018-8060 and CVE-2018-8061, targeting the HWiNFO AMD64 Kernel driver (version 8.98 and lower) on Windows. The main exploit is implemented in 'main.c', which is a generic IOCTL dispatcher. It allows a user to specify a device name, IOCTL code, and input data file. The tool opens a handle to the specified device (commonly '\\.\HWiNFO32'), reads the input data from a file, and sends it to the driver using DeviceIoControl. The output is displayed as a hex dump. The exploit can be used to trigger a kernel panic (BSOD) by sending malformed IOCTLs (CVE-2018-8060) or to read physical memory by crafting specific input data (CVE-2018-8061). The repository structure is simple, with a single C source file, a README explaining the vulnerabilities and usage, and standard license and gitignore files. No network or remote attack vectors are present; exploitation requires local access.
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.