Loading vulnerability…
An elevation of privilege vulnerability in Microsoft Message Queuing (MSMQ). The issue affects the MSMQ component and is classified by Microsoft as an Important severity vulnerability. Specific technical details about the vulnerable code path or function are not available in the provided information.
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 single C++ proof-of-concept exploit (mqac-ioctl.cpp) targeting CVE-2023-21537, a vulnerability in Microsoft Message Queuing (MSMQ) on Windows. The exploit opens a local MSMQ private queue using the format name 'DIRECT=OS:.\Private$\myQueue', allocates and manipulates memory buffers, and spawns two threads: one issues repeated NtDeviceIoControlFile calls with a crafted IOCTL code to the MSMQ queue handle, while the other rapidly changes a length value in the output buffer. This is designed to trigger a race condition or memory corruption in the MSMQ driver, demonstrating the vulnerability. The repository includes Visual Studio project files for building the exploit. No remote network endpoints are present; the attack is local and targets the MSMQ service via direct IOCTL manipulation.
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.
2 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.