KB5029312: Windows Server 2012 R2 Security Update (August 2023)
A crafted MSMQ packet can give an attacker SYSTEM-level code execution on any Windows Server with MSMQ installed.
An attacker who can reach TCP 1801 can send a single crafted packet and execute code as SYSTEM. The companion CVE-2023-36910 shares the same MSMQ attack surface — patch both together.
MSMQ listens on TCP 1801 when installed. A flaw in how MSMQ validates incoming message structures lets a crafted packet corrupt memory in the MSMQ service process and execute code. This is one of two related MSMQ RCEs (with CVE-2023-36910) in the August 2023 patch cycle.
Probably yes if any of these apply:
Affected OS versions
An attacker scans a corporate network for TCP 1801, finds the servers, and triggers the MSMQ flaw on each unpatched host. Because MSMQ exploit development is amortised across the QueueJumper-and-after series of CVEs, working code is widely available.
Manual download
For air-gapped servers or out-of-band deployment. Microsoft Update Catalog returns every OS-version variant of this update.
↗ Microsoft Update CatalogKB5029312Manual remediation steps
Check whether MSMQ is installed and exposed
Get-WindowsFeature -Name MSMQ* | Where-Object Installed
Get-NetTCPConnection -LocalPort 1801 -State Listen -ErrorAction SilentlyContinue
If MSMQ is not needed, removing the feature is the strongest mitigation.
Prerequisites
Estimated time
20–40 minutes per server (download + install + reboot)
Reboot required
Yes — install the cumulative update and reboot the server before the fix is active.
Steps
1. Confirm the server is missing the patch
Get-HotFix -Id KB5029312 -ErrorAction SilentlyContinue
2. Install the update — pick one channel
Windows Update / WSUS (preferred):
UsoClient ScanInstallWait
Manual download (offline / air-gapped):
3. Reboot
Restart-Computer -Force
Verification
Get-HotFix -Id KB5029312
[System.Environment]::OSVersion.Version
Rollback
wusa.exe /uninstall /kb:5029312 /quiet /norestart
Notes
No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.