CVE-2025-21230 Overview
CVE-2025-21230 is a denial of service vulnerability in Microsoft Message Queuing (MSMQ). The flaw affects a broad range of Windows desktop and server releases, from Windows 10 1507 through Windows 11 24H2 and Windows Server 2008 through Windows Server 2025. An unauthenticated attacker can send specially crafted network traffic to a host running the MSMQ service and exhaust its availability. The vulnerability is tracked under [CWE-20: Improper Input Validation] and was published to the NVD on January 14, 2025.
Critical Impact
A remote, unauthenticated attacker can disrupt the availability of MSMQ on affected Windows systems by sending malformed messages over the network, with no user interaction required.
Affected Products
- Microsoft Windows 10 (1507, 1607, 1809, 21H2, 22H2)
- Microsoft Windows 11 (22H2, 23H2, 24H2)
- Microsoft Windows Server 2008, 2012, 2016, 2019, 2022, 2022 23H2, and 2025
Discovery Timeline
- 2025-01-14 - CVE-2025-21230 published to NVD
- 2025-01-14 - Microsoft published advisory Microsoft CVE-2025-21230 Update
- 2025-01-27 - Last updated in NVD database
Technical Details for CVE-2025-21230
Vulnerability Analysis
Microsoft Message Queuing (MSMQ) is a Windows component that enables applications to communicate asynchronously through message queues. The service listens on TCP port 1801 by default and is exposed whenever the optional MSMQ feature is enabled. CVE-2025-21230 is an availability-only flaw, meaning successful exploitation impacts service availability but does not disclose data or grant code execution. The vulnerability is classified under [CWE-20], indicating improper input validation in how MSMQ parses incoming messages or protocol frames. An EPSS score of 1.314% places this issue in the 80th percentile for likelihood of exploitation activity within the next 30 days.
Root Cause
The root cause is improper validation of attacker-controlled input processed by the MSMQ service. Microsoft has not released structural details, but [CWE-20] in network services typically signals missing length checks, malformed field handling, or unchecked state transitions that crash the service process. Because MSMQ runs as a system service, a crash terminates queue processing for all dependent applications on the host.
Attack Vector
The attack vector is network-based and requires no privileges or user interaction. An attacker reaches the target by sending crafted packets to the MSMQ listener on TCP 1801, or over the related ports used for multicast and session management. Any Windows host with the Message Queuing feature enabled and reachable from the attacker is a viable target. Internet-exposed MSMQ endpoints and flat internal networks increase the exposure footprint significantly.
No public proof-of-concept exploit or in-the-wild exploitation has been documented for CVE-2025-21230. Microsoft's advisory should be consulted for protocol-level technical details.
Detection Methods for CVE-2025-21230
Indicators of Compromise
- Unexpected termination or repeated crashes of the mqsvc.exe process on Windows hosts.
- Windows Service Control Manager events showing the Message Queuing service stopping unexpectedly.
- Spikes of inbound traffic to TCP port 1801 from untrusted or external sources.
- Application errors from MSMQ-dependent services reporting queue unavailability.
Detection Strategies
- Monitor Windows Event Log for Service Control Manager events 7031 and 7034 referencing the MSMQ service.
- Alert on mqsvc.exe crash events in Application Error logs (Event ID 1000) and Windows Error Reporting (Event ID 1001).
- Inspect network flow telemetry for anomalous volume or malformed payloads directed at TCP 1801.
Monitoring Recommendations
- Inventory all Windows hosts with the Message Queuing feature enabled and verify whether MSMQ listeners should be reachable.
- Track patch state for the January 2025 Microsoft security update across all affected Windows desktop and server SKUs.
- Correlate MSMQ service restarts with concurrent inbound network connections to identify exploitation attempts.
How to Mitigate CVE-2025-21230
Immediate Actions Required
- Apply the January 2025 Microsoft security updates referenced in the Microsoft CVE-2025-21230 advisory to all affected Windows builds.
- Identify systems with the Message Queuing Windows feature enabled and disable it where the service is not required.
- Restrict inbound access to TCP 1801 at the host firewall and perimeter to trusted application servers only.
Patch Information
Microsoft released security updates addressing CVE-2025-21230 on January 14, 2025, for all supported Windows desktop and server versions listed in the affected products. The official update guidance is available at the Microsoft Security Response Center advisory. Administrators should validate that the cumulative update for their specific build is installed and that mqsvc.exe has been restarted post-patch.
Workarounds
- Disable the Message Queuing Windows optional feature on hosts that do not require MSMQ functionality.
- Block TCP port 1801 (and related MSMQ ports 2101, 2103, 2105, and UDP 3527) at network boundaries.
- Apply Windows Firewall rules to limit MSMQ inbound connections to known application peers.
# Verify and disable the MSMQ feature on Windows where not required
Get-WindowsOptionalFeature -Online -FeatureName MSMQ-Server
Disable-WindowsOptionalFeature -Online -FeatureName MSMQ-Server -NoRestart
# Restrict inbound MSMQ traffic to trusted hosts only
New-NetFirewallRule -DisplayName "Block-MSMQ-1801-Inbound" `
-Direction Inbound -Protocol TCP -LocalPort 1801 -Action Block
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
