Loading vulnerability…
An elevation of privilege vulnerability affecting Sysinternals Sysmon for Windows was addressed by Microsoft in May 2023. The available information identifies the issue as a local privilege escalation flaw in Sysmon, but does not provide technical detail about the vulnerable code path, root cause, or exploitation mechanism. Sysmon is a Windows system monitoring component used to generate detailed telemetry for process creation, network connections, driver loading, and related forensic events. Successful exploitation would allow an attacker to elevate privileges on a vulnerable Windows system.
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 is a Proof-of-Concept (PoC) exploit for CVE-2023-29343, an arbitrary file write vulnerability in Microsoft Sysmon version 14.14 on Windows. The exploit is implemented in C++ and consists of a Visual Studio project with supporting C, header, and IDL files. The main exploit logic is in 'SysmonEoP/main.cpp'. The exploit abuses Windows service tracing and the RasMan service to create a directory owned by SYSTEM but writable by a low-privileged user. It then manipulates file system objects (including creating junctions and symbolic links) and registry keys to trick Sysmon into writing or deleting files in attacker-controlled locations. The exploit ultimately writes a DLL (wow64log.dll) to C:\windows\system32 as SYSTEM, which could be used for privilege escalation via code execution. The exploit is only effective on Sysmon 14.14 and Windows systems prior to the April patch for CVE-2023-28222. The repository includes all necessary code to build and run the PoC, with detailed steps and references in the README. The attack vector is local privilege escalation, and several fingerprintable file paths and a registry key are involved in the exploitation process.
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.