CVE-2022-3699 is a local privilege escalation vulnerability affecting Lenovo HardwareScanPlugin prior to version 1.3.1.2 and Lenovo Diagnostics prior to version 4.45. The provided content states that the issue could allow a local user to execute code with elevated privileges. Supporting context also ties the issue to the Lenovo Diagnostics Driver for Windows 10 and later, including the kernel driver LenovoDiagnosticsDriver.sys, which is listed as vulnerable in BYOVD-related provider catalogs. Based on the available information, the flaw is in Lenovo's diagnostics component/driver and enables elevation from a local context to higher privileges, but the specific vulnerable function or IOCTL handler is not identified in the provided material.
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.
3 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module targeting CVE-2022-3699, a local privilege escalation vulnerability in the Lenovo Diagnostics Driver for Windows. The exploit abuses incorrect access control in the driver, allowing a low-privileged user to issue IOCTLs for arbitrary memory read/write, ultimately enabling code execution as SYSTEM. The module is written in Ruby and is structured as a standard Metasploit local exploit, requiring a Meterpreter session on a compatible Windows system with the vulnerable driver present. The exploit checks for the presence of the driver (\\.\LenovoDiagnosticsDriver) and ensures the target Windows version is supported. Upon exploitation, it injects a payload (typically a Meterpreter shell) via a reflective DLL, granting elevated privileges. The repository is operational and ready for use within the Metasploit framework.
This repository is an operational exploit for CVE-2022-3699, targeting the LenovoDiagnosticsDriver (ldiagd.sys) on Windows systems. The exploit is implemented in C++ and is structured as a Visual Studio project. The main exploit logic resides in the 'LenovoMemoryMgr' class, which provides methods to interact with the vulnerable driver via IOCTLs, allowing arbitrary physical and virtual memory reads/writes and kernel function invocation. The exploit demonstrates kernel code execution by allocating kernel pool memory using ExAllocatePoolWithTag. It also includes logic to inject and execute custom shellcode in kernel space. The entry point is 'main.cpp', which initializes the exploit, locates kernel exports, and performs the kernel function call. The repository includes utility code for parsing PDB files and resolving kernel structure offsets. The primary attack vector is local, requiring the attacker to execute code on the target system with access to the vulnerable driver. Notable endpoints include the device path '\\.\LenovoDiagnosticsDriver', the driver file 'ldiagd.sys', and the Microsoft symbol server URL for PDB downloads.
This repository contains a working local privilege escalation exploit for CVE-2022-3699, targeting the Lenovo Diagnostics Driver on Windows. The exploit is implemented in C++ and consists of a Visual Studio solution with the main logic in 'LenovoMemoryMgr.cpp', 'LenovoMemoryMgr.h', and 'Source.cpp'. The exploit leverages insufficient access control in the driver, allowing unprivileged users to issue IOCTLs for arbitrary physical and virtual memory read/write operations. The code locates the EPROCESS structures for the current and SYSTEM processes, reads the SYSTEM process token, and overwrites the current process token, effectively granting SYSTEM privileges. The exploit then spawns a SYSTEM shell (cmd.exe). The device endpoint used is '\\.\LenovoDiagnosticsDriver'. The exploit requires the vulnerable driver to be present and accessible, and was tested on Windows 11 21H2 with HVCI disabled. The repository is well-structured for building with Visual Studio and provides a clear demonstration of the vulnerability's impact.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.