Loading vulnerability…
A stack-based buffer overflow exists in the kernel mode driver kwatch3 of KINGSOFT Internet Security 9 Plus Version 2010.06.23.247. The vulnerability is triggered by improper handling of crafted inputs, allowing an attacker to overflow a stack buffer in the driver.
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 local privilege escalation exploit targeting the Kingsoft Antivirus KWatch Driver (KWatch3.sys) version 2009.3.17.77, as described in CVE-2022-25949. The exploit is implemented in C++ (single main file: src/exploit_kwatch3/exploit_kwatch3.cpp) and is designed to run on Windows systems (notably Windows 7 SP1). The exploit works by opening a handle to the vulnerable driver (\\.\kwatch3), sending a crafted IOCTL request with exploit data, and executing custom shellcode that swaps the current process token with the SYSTEM process token. Upon successful exploitation, it launches a SYSTEM-level command shell (cmd.exe), providing the attacker with full system privileges. The repository includes standard project files for Visual Studio, a README with background and usage notes, and no detection or fake code. The attack vector is local, requiring the attacker to execute code on the target system with access to the vulnerable driver.
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.