Loading vulnerability…
A kernel pool overflow vulnerability exists in the hitmanpro37.sys driver used by Sophos SurfRight HitmanPro prior to version 3.7.20 Build 286. The vulnerability can be triggered by a malformed IOCTL call, allowing a local attacker to overflow a kernel pool buffer. This flaw is present in the driver included with HitmanPro.Alert and Sophos Clean as well.
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 operational local privilege escalation exploits targeting CVE-2017-6008, a kernel pool buffer overflow vulnerability in the HitmanPro (hitmanpro37.sys) driver on Windows. The structure includes three main C++ exploit files: - Win10/src/CVE-2017-6008_Win10_Exploit.cpp: Main exploit for Windows 10, leveraging an out-of-bounds read to leak the pool cookie and then performing a quota process pointer overwrite to escalate privileges. It injects shellcode into a SYSTEM process (winlogon.exe) to spawn a SYSTEM shell. - Win10/src/CVE-2017-7441_Win10_LeakCookie.cpp: Helper tool to leak the pool cookie required for the Windows 10 exploit. - Win7/src/CVE-2017-6008_Win7_Exploit.cpp: Exploit for Windows 7, using a similar kernel pool overflow technique for privilege escalation. All exploits interact with the vulnerable driver via the device path \\.\Hitman Pro 37 and use custom pool spraying techniques (via an external PoolSprayer library) to reliably trigger the vulnerability. The exploits are operational, providing a SYSTEM shell upon success, but require local access and a vulnerable driver version. The README provides detailed background, references, and caveats regarding Windows version compatibility.
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.