Loading vulnerability…
CVE-2024-36424 is a local denial-of-service vulnerability in K7RKScan.sys, a driver component of K7 Ultimate Security before version 17.0.2019. The issue is caused by a NULL pointer dereference in the driver, which can be triggered by a local user. Successful exploitation causes the vulnerable system to crash and produce a blue screen of death (BSOD). Based on the provided information, no further details about the specific vulnerable function or code path are currently available.
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 (1 hidden).
This repository contains a proof-of-concept (PoC) exploit for CVE-2024-36424, a local privilege vulnerability in K7 Ultimate Security (versions prior to 17.0.2019) on Windows. The exploit is implemented in a single C++ file (K7-PoC.cpp), which opens a handle to the K7RKScan.sys driver device (\\.\DosK7RKScnDrv) and sends a DeviceIoControl request with IOCTL 0x222010 and a null input buffer. This triggers a null pointer dereference in the driver, resulting in a denial of service (system crash/BSOD). The README.md provides detailed usage instructions, affected product/version information, and references. The exploit requires local access and the vulnerable driver to be loaded. No remote or network attack vector is present. The repository is structured simply, with one exploit code file and a README containing technical and advisory details.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.