CVE-2023-36874 is a local elevation-of-privilege vulnerability in the Microsoft Windows Error Reporting (WER) service. The flaw was exploited in the wild as a zero-day. Available reporting indicates the issue is tied to the way privileged WER code can be induced to follow attacker-controlled path redirection through a fake root drive mapping during process creation. In observed exploit chains, an attacker with local code execution or interactive access manipulates per-session device mappings and symbolic-link-based path redirection so that privileged WER operations resolve files from an attacker-controlled location rather than the legitimate system root. The vulnerable execution path has been described as involving the IWerReport COM interface and SubmitReport, which ultimately reaches WER logic that launches a process via CreateProcess in the context of the privileged WER service. By tricking that process creation flow into following the fake root, the attacker can cause execution of unauthorized code with elevated rights.
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.
5 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit module (Ruby file) that exploits CVE-2023-36874, a local privilege escalation vulnerability in Microsoft Windows Error Reporting. The exploit abuses the way Windows locates the error report parser by manipulating directory structures and placing a malicious executable (payload) in a crafted path, causing it to be executed as SYSTEM. The module is highly weaponized, allowing the user to select a payload (such as a reverse shell or meterpreter), which is uploaded and executed with SYSTEM privileges. The exploit requires a session on the target (meterpreter, shell, or powershell) and is primarily intended for Windows 10 22H2, though it may work on other versions. The code handles all steps: creating directories, uploading crafted error reports and payloads, and executing the exploit. The main fingerprintable endpoints are the file paths used for the error report and payload placement. The repository is structured as a single Metasploit exploit module, with all logic contained in one Ruby file.
This repository is a proof-of-concept (PoC) exploit for CVE-2023-36874, a Windows privilege escalation vulnerability. The exploit is written in C++ and consists of two main components: 1. The main exploit (main.cpp) manipulates Windows Error Reporting (WER) infrastructure by creating directories, files, and symbolic links in the Windows object namespace. It leverages COM interfaces and native Windows APIs to create a crafted WER report and symbolic links, redirecting system operations to attacker-controlled locations (notably C:\test and C:\ProgramData). 2. The payload (wermgr/main.cpp) is a separate executable that, when run as SYSTEM (due to the exploit), creates a new local user 'admin' with a preset password and adds it to the Administrators group, effectively granting full system access to the attacker. The README provides setup instructions, requiring the attacker to place a malicious wermgr.exe in C:\test\system32 and run the compiled PoC. The exploit targets Windows 10 (tested on build 19045.2006) and demonstrates a local privilege escalation scenario. No network endpoints are involved; all actions are performed locally via file system and Windows object namespace manipulation. The repository includes header files (def.h, resource.h) for COM and resource definitions, and a resource file for embedding the WER report. The exploit is operational, providing a working privilege escalation path on vulnerable systems.
This repository contains a proof-of-concept (PoC) exploit for CVE-2023-36874, a vulnerability in the Windows Error Reporting (WER) component on Microsoft Windows. The main file, PoC.cpp, is a C++ program that demonstrates how to interact with WER's COM interfaces to trigger the vulnerability. The exploit initializes COM, creates and uses several WER-related COM interfaces (IErcLuaSupport, IWerStoreFactory, IWerStore, IWerReport), and follows a sequence of method calls to enumerate, load, and submit a crafted error report (the report name is a placeholder and should be replaced with a real target report). The README.md provides a detailed step-by-step explanation of the exploit process and reiterates that the code is for educational purposes only. No network or remote endpoints are involved; the exploit is purely local and targets the Windows platform. The repository is structured simply, with one code file and a README, and is intended as a PoC rather than a weaponized or operational exploit.
This repository provides a mature, operational Cobalt Strike Beacon Object File (BOF) exploit for CVE-2023-36874, a local privilege escalation vulnerability in the Windows Error Reporting (WER) service. The exploit is implemented as a Cobalt Strike script (wer_lpe.cna) and a compiled BOF (from src/main.cpp), allowing an attacker with code execution on a vulnerable Windows 10/11 (21H1-22H2) system to upload and execute an arbitrary EXE as SYSTEM. The exploit works by creating a specially crafted directory and Report.wer file in the WER ReportArchive, then triggering the vulnerability to run the payload with elevated privileges. The code includes OPSEC features such as randomized directory names and automatic cleanup of dropped files and directories. The exploit is not effective against users with local admin rights and is not a UAC bypass. The repository is structured with source code (src/), a Cobalt Strike script (dist/wer_lpe.cna), and build instructions (makefile).
This repository contains a proof-of-concept exploit for CVE-2023-36874, targeting Microsoft Windows. The main file, poc.cpp, demonstrates a local privilege escalation technique by manipulating the Windows Error Reporting (WER) system. The exploit creates a controlled directory structure and files, sets up a symbolic link to redirect the C: drive to a user-controlled path, and uses COM interfaces to trigger WER operations. The goal is to have WER execute a controlled binary (wermgr.exe) from the attacker's directory, potentially leading to privilege escalation. The repository consists of a README and a single C++ proof-of-concept file, with no external dependencies or framework usage. The exploit is a local attack and does not involve network endpoints.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An elevation of privilege vulnerability in the Windows Error Reporting Service that could allow a local attacker to gain administrator privileges.
A specific Windows vulnerability tracked as CVE-2023-36874, discussed here in the context of detection content for suspected exploitation activity (notably file-creation artifacts such as a fake wermgr.exe).
A local privilege escalation vulnerability in Microsoft Windows, allowing attackers to gain elevated privileges on a compromised system.
Windows Error Reporting (WER) local elevation of privilege where WER’s process creation can be coerced into executing from a user-writable fake root (device map / DOS device modification), leading to SYSTEM execution.
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.