CVE-2023-21554 — Microsoft Message Queuing (MSMQ) Remote Code Execution Vulnerability
Executive Summary
None
Overview
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
EPSS Score
Affected Products
| Product | KB Article | Severity | Impact | Restart Required |
|---|---|---|---|---|
| Windows 10 for 32-bit Systems | 5025234 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 for x64-based Systems | 5025234 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1607 for 32-bit Systems | 5025228 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1607 for x64-based Systems | 5025228 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1809 for 32-bit Systems | 5025229 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1809 for ARM64-based Systems | 5025229 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1809 for x64-based Systems | 5025229 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 20H2 for 32-bit Systems | 5025221 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 20H2 for ARM64-based Systems | 5025221 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 21H2 for 32-bit Systems | 5025221 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 21H2 for ARM64-based Systems | 5025221 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 21H2 for x64-based Systems | 5025221 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 22H2 for 32-bit Systems | 5025221 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 22H2 for ARM64-based Systems | 5025221 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 22H2 for x64-based Systems | 5025221 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 11 version 21H2 for ARM64-based Systems | 5025224 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 11 version 21H2 for x64-based Systems | 5025224 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 11 Version 22H2 for ARM64-based Systems | 5025239 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 11 Version 22H2 for x64-based Systems | 5025239 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows Server 2008 for 32-bit Systems Service Pack 2 5025271 (Monthly Rollup) 5025273 (Security Only) Critical Remote Code Execution 5023755 Base: 9.8 Temporal: 8.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.22015 Yes 5025271 5025273 Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) 5025271 (Monthly Rollup) 5025273 (Security Only) Critical Remote Code Execution 5023755 Base: 9.8 Temporal: 8.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.22015 Yes 5025271 5025273 Windows Server 2008 for x64-based Systems Service Pack 2 5025271 (Monthly Rollup) 5025273 (Security Only) Critical Remote Code Execution 5023755 Base: 9.8 Temporal: 8.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.22015 Yes 5025271 5025273 Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) 5025271 (Monthly Rollup) 5025273 (Security Only) Critical Remote Code Execution 5023755 Base: 9.8 Temporal: 8.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.22015 Yes 5025271 5025273 Windows Server 2008 R2 for x64-based Systems Service Pack 1 5025279 (Monthly Rollup) 5025277 (Security Only) Critical Remote Code Execution 5023769 Base: 9.8 Temporal: 8.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.1.7601.26466 Yes 5025279 5025277 Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) 5025279 (Monthly Rollup) 5025277 (Security Only) Critical Remote Code Execution 5023769 Base: 9.8 Temporal: 8.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.1.7601.26466 Yes 5025279 5025277 Windows Server 2012 5025287 (Monthly Rollup) 5025272 (Security Only) Critical Remote Code Execution 5023769 Base: 9.8 Temporal: 8.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.2.9200.24216 Yes None Windows Server 2012 (Server Core installation) 5025287 (Monthly Rollup) 5025272 (Security Only) Critical Remote Code Execution 5023769 Base: 9.8 Temporal: 8.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.2.9200.24216 Yes None Windows Server 2012 R2 5025285 (Monthly Rollup) 5025288 (Security Only) Critical Remote Code Execution 5023765 Base: 9.8 Temporal: 8.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.3.9600.20919 Yes None Windows Server 2012 R2 (Server Core installation) 5025285 (Monthly Rollup) 5025288 (Security Only) Critical Remote Code Execution 5023765 Base: 9.8 Temporal: 8.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.3.9600.20919 Yes None Windows Server 2016 | 5025228 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows Server 2016 (Server Core installation) | 5025228 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows Server 2019 | 5025229 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows Server 2019 (Server Core installation) | 5025229 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows Server 2022 | 5025230 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows Server 2022 (Server Core installation) | 5025230 (Security Update) |
Critical | Remote Code Execution | Yes |
Patches
| Article | Type | Restart |
|---|---|---|
5025234 |
Security Update | Yes |
5025228 |
Security Update | Yes |
5025229 |
Security Update | Yes |
5025221 |
Security Update | Yes |
5025224 |
Security Update | Yes |
5025239 |
Security Update | Yes |
5025230 |
Security Update | Yes |
Patch Diff
Patch diff 10.0.22621.963 -> 10.0.22621.1555 (MSMQ; safe section-pointer helpers across all header types)
| Function | Address | Change | Note |
|---|---|---|---|
KERNEL32.DLL::AcquireSRWLockExclusive |
EXTERNAL:0000011d -> EXTERNAL:00000113 |
refcount, address, calling | similarity 1.0 |
newstr |
1800a0d48 -> 1800a3208 |
length, address | similarity 1.0 |
wil_details_GetNtDllModuleHandle |
18005b828 -> 1800401c0 |
refcount, address, calling | similarity 1.0 |
CUserHeader::SectionIsValid |
18008426c -> 1800865f8 |
code, length, address, called | similarity 0.8 |
CDebugSection::SectionIsValid |
1800836d4 -> 1800858f0 |
code, length, address, called | similarity 0.43 |
CBaseMqfHeader::SectionIsValid |
1800834c0 -> 1800856a4 |
code, length, address, called | similarity 0.43 |
CXactHeader::SectionIsValid |
1800846c4 -> 180086a88 |
code, length, address, called | similarity 0.4 |
CMessageTransport::ReceiveResponseFailed |
1800a75b0 -> 1800a9a70 |
refcount, address | similarity 1.0 |
wil::details::`dynamic_initializer_for_'g_header_init_InitializeStagingHeaderInternalApi'' |
180002680 -> 1800023f0 |
code, length, address | similarity 0.9 |
wil::details::StringCchPrintfA |
1800595c0 -> 18003e5f8 |
code, length, address, called | similarity 0.38 |
CPropertyHeader::SectionIsValid |
180083d74 -> 1800860a0 |
code, length, address, called | similarity 0.54 |
__GSHandlerCheck |
180004f48 -> 180004f98 |
refcount, address | similarity 1.0 |
_guard_xfg_dispatch_icall_nop |
1800df980 -> 1800e1e40 |
refcount, address, calling | similarity 0.89 |
atexit |
1800048ac -> 1800048fc |
refcount, address, calling | similarity 1.0 |
wil::details::unique_storage<wil::details::resource_policy<_TP_TIMER*___ptr64,void_(__cdecl*)(_TP_TIMER*___ptr64),&public:_static_void___cdecl_wil::details::DestroyThreadPoolTimer<struct_wil::details::SystemThreadPoolMethods,0>::Destroy(struct__TP_TIMER*___ptr64),wistd::integral_constant<unsigned___int64,0>,_TP_TIMER*___ptr64,_TP_TIMER*___ptr64,0,std::nullptr_t>_>::reset |
18005b4a8 -> 18003f9b0 |
refcount, address, calling | similarity 1.0 |
__CxxFrameHandler4 |
180004744 -> 180004794 |
refcount, address | similarity 0.86 |
CQmPacket::CQmPacket |
1800377d8 -> 1800380ac |
code, length, address, called | similarity 0.31 |
GetSafeDataAndAdvancePointer<unsigned_long> |
180037328 -> 18003752c |
refcount, address, calling | similarity 1.0 |
wil::ProcessShutdownInProgress |
180056650 -> 18003c9d0 |
refcount, address, calling | similarity 1.0 |
CMsgDeadletterHeader::SectionIsValid |
180083a0c -> 180085cf0 |
code, length, address, called | similarity 0.41 |
KERNEL32.DLL::CreateThreadpoolTimer |
EXTERNAL:0000012a -> EXTERNAL:00000120 |
refcount, address, calling | similarity 1.0 |
CSSlNegotiation::Complete_ReadHandShakeResponse |
1800c8c30 -> 1800cb0f0 |
refcount, address | similarity 1.0 |
wistd::unique_ptr<void,wil::process_heap_deleter>::reset |
18005b484 -> 18003f98c |
refcount, address, calling | similarity 1.0 |
CUserHeader::QueueSize |
18003901c -> 18003cbe4 |
code, length, address, calling, called | similarity 0.76 |
CMsgGroupHeader::SectionIsValid |
180083b28 -> 180085e30 |
code, length, address, called | similarity 0.41 |
wil::details_abi::heap_buffer::push_back |
18005b1e0 -> 18003f884 |
refcount, address, calling | similarity 1.0 |
wil::details::EnsureCoalescedTimer_SetTimer |
180051c98 -> 18003a090 |
refcount, address, calling | similarity 1.0 |
StringCchVPrintfW |
18005963c -> 18003e644 |
code, length, address, called | similarity 0.39 |
ReportAndThrow |
180039154 -> 18003d930 |
refcount, address, calling | similarity 0.95 |
wil_details_GetKernelBaseModuleHandle |
18005b7f0 -> 180040188 |
refcount, address, calling | similarity 1.0 |
StringCchCopyA |
180049ecc -> 18003e5c0 |
code, refcount, length, address, called | similarity 0.42 |
KERNEL32.DLL::GetProcAddress |
EXTERNAL:00000109 -> EXTERNAL:00000110 |
refcount, address, calling | similarity 1.0 |
CSecurityHeader::SectionIsValid |
180083ec8 -> 180086224 |
code, length, address, called | similarity 0.77 |
wil::details::unique_storage<wil::details::resource_policy<_RTL_SRWLOCK*___ptr64,void_(__cdecl*)(_RTL_SRWLOCK*___ptr64),&void___cdecl_ReleaseSRWLockExclusive(struct__RTL_SRWLOCK*___ptr64),wistd::integral_constant<unsigned___int64,1>,_RTL_SRWLOCK*___ptr64,_RTL_SRWLOCK*___ptr64,0,std::nullptr_t>_>::~unique_storage<wil::details::resource_policy<_RTL_SRWLOCK*___ptr64,void_(__cdecl*)(_RTL_SRWLOCK*___ptr64),&void___cdecl_ReleaseSRWLockExclusive(struct__RTL_SRWLOCK*___ptr64),wistd::integral_constant<unsigned___int64,1>,_RTL_SRWLOCK*___ptr64,_RTL_SRWLOCK*___ptr64,0,std::nullptr_t>_> |
18004fb04 -> 18003908c |
refcount, address, calling | similarity 1.0 |
wil::details::unique_storage<wil::details::resource_policy<_TP_TIMER*___ptr64,void_(__cdecl*)(_TP_TIMER*___ptr64),&public:_static_void___cdecl_wil::details::DestroyThreadPoolTimer<struct_wil::details::SystemThreadPoolMethods,0>::Destroy(struct__TP_TIMER*___ptr64),wistd::integral_constant<unsigned___int64,0>,_TP_TIMER*___ptr64,_TP_TIMER*___ptr64,0,std::nullptr_t>_>::~unique_storage<wil::details::resource_policy<_TP_TIMER*___ptr64,void_(__cdecl*)(_TP_TIMER*___ptr64),&public:_static_void___cdecl_wil::details::DestroyThreadPoolTimer<struct_wil::details::SystemThreadPoolMethods,0>::Destroy(struct__TP_TIMER*___ptr64),wistd::integral_constant<unsigned___int64,0>,_TP_TIMER*___ptr64,_TP_TIMER*___ptr64,0,std::nullptr_t>_> |
18004fb54 -> 1800390dc |
refcount, address, calling | similarity 1.0 |
__GSHandlerCheck_EH4 |
1800df880 -> 1800e1d40 |
refcount, address | similarity 1.0 |
__security_check_cookie |
180004760 -> 1800047b0 |
refcount, address, calling | similarity 1.0 |
Root Cause Analysis
Root Cause Analysis — CVE-2023-21554
Summary
| Field | Value |
|---|---|
| CVE | CVE-2023-21554 (QueueJumper) |
| Binary | MQQM.dll (Microsoft Message Queuing Queue Manager) |
| Component | CQmPacket::CQmPacket — MSMQ packet constructor |
| Bug Class | Out-of-Bounds Write (CWE-787) |
| Impact | Remote Code Execution (unauthenticated) |
| CVSS 3.1 | 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) |
| Exploited ITW | No |
| Patch | April 2023 Patch Tuesday (KB5025239 Win11 22H2) |
BinDiff Summary
Versions Compared
- Pre-patch: MQQM.dll 10.0.22621.963 (March 2023)
- Post-patch: MQQM.dll 10.0.22621.1555 (April 2023)
Changed Functions
BinDiff revealed multiple functions with similarity < 1.00:
| Function | Change Type | Description |
|---|---|---|
CQmPacket::CQmPacket |
Code (8 feature-flag checks) | 8 instances of GetNextSectionPtrSafe replacing unsafe pointer arithmetic |
GetNextSectionPtrSafe |
New function | Validates calculated next-section pointer against packet length |
CEodHeader::GetNextSectionSafe |
New function | Safe variant for EodHeader section boundary |
CBaseHeader::SectionIsValid |
Code (validation added) | Additional section boundary checks |
| Feature flag functions | New | MSRC76146_MSMQ_OOBRWFixes flag check functions |
Feature Flag Discovery
The patched binary contains symbols referencing MSRC case numbers as feature flags:
MSRC76146_MSMQ_OOBRWFixes
MSRC76146_MSMQ_KernelVariants
When enabled, the patched code path executes. When disabled, the original vulnerable code runs. This reveals that the fix uses Windows Feature Store toggles.
Vulnerability Overview
MQQM.dll is the core user-space component of the MSMQ service, loaded by mqsvc.exe.
It accepts data via TCP port 1801 using WSARecv. The CQmPacket::CQmPacket constructor
parses incoming MSMQ messages by iterating through a chain of section headers. Each section
specifies its own size, and the next section’s location is computed by adding this size to
the current pointer. If the declared size is larger than the actual data, the calculated
pointer goes out of bounds.
Root Cause — Insufficient Section Size Validation
The Vulnerable Code (pre-patch)
In CQmPacket::CQmPacket, section pointers are computed by simple addition:
// Pre-patch: Unsafe pointer arithmetic
// pEodHeader points to the current EodHeader section
// The total section size is computed from header fields
ULONG eodSize = pEodHeader->field_0x00 + pEodHeader->field_0x04 + 0xF;
PVOID pNextSection = (BYTE*)pEodHeader + eodSize;
// No check that pNextSection is still within the packet buffer!
This pattern repeats for multiple section types: EodHeader, SRMPEnvelopeHeader, SoapHeader, and others. Each uses user-controlled size fields to compute the next section pointer.
The Patch (post-patch)
// Post-patch: Safe pointer computation
if (MSRC76146_MSMQ_OOBRWFixes_enabled) {
pNextSection = CEodHeader::GetNextSectionSafe(pEodHeader, packetLength);
if (pNextSection == NULL) {
// Section extends beyond packet boundary — reject
goto error;
}
} else {
// Legacy unsafe path
pNextSection = (BYTE*)pEodHeader + eodSize;
}
The new GetNextSectionPtrSafe function:
PVOID GetNextSectionPtrSafe(PVOID currentSection, ULONG sectionSize, ULONG packetLength) {
PVOID nextPtr = (BYTE*)currentSection + sectionSize;
if (nextPtr > packetEndPtr || nextPtr < currentSection) { // overflow check
return NULL; // Out of bounds — reject
}
return nextPtr;
}
The Out-of-Bounds Write
After iterating through all sections, CQmPacket::CQmPacket appends an
OnDiskExtensionHeader at the computed end-of-message pointer. If any section’s
size was malformed, this pointer points beyond the packet buffer:
// At computed end-of-message (may be OOB)
pEndOfMessage->field_0x00 = 0x0000000C; // Address + 0x00
pEndOfMessage->field_0x02 = 0x00000000; // Address + 0x02
pEndOfMessage->field_0x12 = 0; // Address + 0x12
pEndOfMessage->field_0x1A = 0; // Address + 0x1A
pEndOfMessage->field_0x0E = 0x00000094; // Address + 0x0E
pEndOfMessage->field_0x22 = 0; // Address + 0x22
pEndOfMessage->field_0x62 = 0; // Address + 0x62
memcpy(pEndOfMessage + 0xA6, &taAddress, addrLen+8); // TA_ADDRESS with client IP
MSMQ Message Format
BaseHeader (entry point)
┌──────────────────────────┐
│ VersionNumber (2 bytes) │ Must be 0x10
│ Reserved (2 bytes) │
│ Flags (4 bytes) │ Bit field controlling section presence
│ Signature (4 bytes) │ 0x4C494F52 ("LIOR")
│ PacketSize (4 bytes) │ Total message size
│ TimeToReachQueue (4 bytes)│
└──────────────────────────┘
Message Section Chain
BaseHeader → UserHeader → [SecurityHeader] → [PropertyHeader]
→ [DebugSection] → [SRMPEnvelopeHeader] → [CompoundMessageHeader]
→ [EodHeader] → [EodAckHeader] → [SoapHeader]
→ OnDiskExtensionHeader (appended at end)
Each section’s presence is controlled by flags in the BaseHeader and UserHeader. The vulnerability allows any section with user-controlled size to push the end-of-message pointer beyond the packet buffer.
EodHeader (trigger example)
┌──────────────────────────┐
│ field_0x00 (4 bytes) │ Size component 1 (attacker-controlled)
│ field_0x04 (4 bytes) │ Size component 2 (attacker-controlled)
│ ... (0x0F total minimum) │
└──────────────────────────┘
Total section size = field_0x00 + field_0x04 + 0x0F
The EodHeader flag bit is described as “reserved” in Microsoft documentation.
Memory Management
Packet Buffer Allocation
QmAcAllocatePacket → NtDeviceIoControl → mqac.sys
└── Allocates buffer from mapped view of .mq file
(C:\Windows\System32\msmq\storage\*.mq)
Each .mq file can hold up to 4MB
Multiple queues share the same file
Key implications for exploitation:
- Buffers are in file-mapped memory, NOT in process heap
- No heap objects to corrupt directly (unlike typical heap-based OOB)
- Heap grooming requires sending many messages to force adjacent heap allocations
- Requires queue send access (usually requires an open queue on the target)
OOB Write Contents
The attacker has limited control over the written values:
| Offset | Value Written | Controllable? |
|---|---|---|
| +0x00 | 0x0000000C | No (constant) |
| +0x02 | 0x00000000 | No (zero) |
| +0x0E | 0x00000094 | No (constant) |
| +0x12 | 0x0000000000000000 | No (zero) |
| +0x1A | 0x0000000000000000 | No (zero) |
| +0x22 | 0x0000 | No (zero) |
| +0x62 | 0x0000 | No (zero) |
| +0xA6 | TA_ADDRESS (client IP) | Partially (source IP) |
The write offset from the buffer base IS fully controllable (via section size fields).
Kernel Variants (mqac.sys)
Feature flag MSRC76146_MSMQ_KernelVariants in mqac.sys indicates analogous bugs in:
CPacketBuffer::MsgDeadletterHeader/MsgDeadletterHeaderSafeCPacketBuffer::MsgOnDiskExtensionHeader/MsgOnDiskExtensionHeaderSafe
These parse the same MSMQ packet sections for dead-letter queue forwarding and acknowledgement messages. The kernel driver operates on the same .mq file mapping, not kernel pool, limiting kernel exploitation utility.
Remote Patch Detection
An unpatched server can be detected remotely:
- Send MSMQ message with HTTP flag set in UserHeader
- Set SRMPEnvelopeHeader DataLength to a value that overflows when multiplied by 2
(e.g.,
DataLength * 2wraps to equal actual data size) - Patched: Integer overflow detected → exception → no response
- Unpatched: Overflow not detected → message processed → response sent
This allows safe remote scanning without triggering the OOB write.
Detection
YARA — Exploit Artifacts
rule CVE_2023_21554_QueueJumper_Exploit
{
meta:
description = "Detects tools exploiting CVE-2023-21554 MSMQ QueueJumper"
cve = "CVE-2023-21554"
author = "OnlyFm252"
strings:
$sig_lior = { 4C 49 4F 52 }
$port_1801 = { 09 07 }
$s_msmq = "MSMQ" ascii wide nocase
$s_mqsvc = "mqsvc" ascii wide nocase
$s_mqqm = "mqqm" ascii wide nocase
$s_queue = "QueueJumper" ascii wide nocase
$s_eod = "EodHeader" ascii wide
$s_srmp = "SRMPEnvelope" ascii wide
$hex_packet = { 10 00 00 00 ?? ?? ?? ?? 52 4F 49 4C }
condition:
uint16(0) == 0x5A4D and
(
($sig_lior and ($s_msmq or $s_mqsvc or $s_mqqm)) or
($hex_packet and filesize < 1MB) or
($s_queue)
)
}
Sigma — MSMQ Service Exploitation Attempt
title: CVE-2023-21554 MSMQ QueueJumper RCE Attempt
id: b2c3d4e5-f6a7-8901-bcde-f01234567890
status: experimental
description: >
Detects potential exploitation of CVE-2023-21554 via unusual MSMQ
service behavior including crashes or abnormal network connections.
author: OnlyFm252
date: 2026/07/26
references:
- https://www.ibm.com/think/x-force/msmq-queuejumper-rce-vulnerability-technical-analysis
- https://research.checkpoint.com/2023/queuejumper-critical-unauthorized-rce-vulnerability-in-msmq-service/
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-21554
logsource:
product: windows
category: network_connection
detection:
selection:
DestinationPort: 1801
Initiated: 'true'
filter_legitimate:
Image|endswith:
- '\mqsvc.exe'
- '\mmc.exe'
condition: selection and not filter_legitimate
level: medium
tags:
- attack.initial_access
- attack.t1190
- cve.2023.21554
Sigma — MSMQ Service Crash
title: CVE-2023-21554 MSMQ Service Crash Detection
id: c3d4e5f6-a7b8-9012-cdef-012345678901
status: experimental
description: Detects MSMQ service crashes that may indicate exploitation attempts.
author: OnlyFm252
date: 2026/07/26
logsource:
product: windows
service: system
detection:
selection:
Provider_Name: 'Service Control Manager'
EventID: 7034
param1|contains: 'Message Queuing'
condition: selection
level: high
tags:
- attack.initial_access
- attack.t1190
- cve.2023.21554
Sysmon Configuration
<Sysmon schemaversion="4.90">
<EventFiltering>
<!-- Event 3: Detect inbound connections to MSMQ port 1801 -->
<NetworkConnect onmatch="include">
<DestinationPort condition="is">1801</DestinationPort>
</NetworkConnect>
<!-- Event 1: Detect mqsvc.exe child processes (post-exploitation) -->
<ProcessCreate onmatch="include">
<ParentImage condition="end with">\mqsvc.exe</ParentImage>
</ProcessCreate>
<!-- Event 11: Detect .mq file creation (message storage) -->
<FileCreate onmatch="include">
<TargetFilename condition="contains">\msmq\storage\</TargetFilename>
<TargetFilename condition="end with">.mq</TargetFilename>
</FileCreate>
<!-- Event 7: Detect MQQM.dll loading -->
<ImageLoad onmatch="include">
<ImageLoaded condition="end with">\mqqm.dll</ImageLoaded>
</ImageLoad>
</EventFiltering>
</Sysmon>
References
Attack Path
MSMQ section pointers computed by unchecked addition - a crafted packet walks the parser out of the buffer
Derived from the patch delta: the checks added by the vendor identify which fields crossed a trust boundary unvalidated. Reachability and privilege are taken from the call chain in the RCA report.
Exploits & PoC
5 public PoCsUnverified third-party code
Public proof-of-concept repositories aggregated from PoC-in-GitHub. They are not reviewed and may be incomplete, non-functional, or malicious — inspect the code before running anything.
| Repository | Stars | Published | Description |
|---|---|---|---|
| zoemurmure/CVE-2023-21554-PoC | 59 | 2023-05-18 | CVE-2023-21554 Windows MessageQueuing PoC,分析见 https://www.zoemurmure.top/posts/cve_2023_21554/ |
| 3tternp/CVE-2023-21554 | 28 | 2023-08-17 | |
| leongxudong/MSMQ-Vulnerability | 5 | 2025-03-31 | Documentation and PoC for CVE-2023-21554 MSMQ Vulnerability |
| shootweb/CVE-2023-21554 | 2 | 2025-10-09 | CVE-2023-21554 PoC |
| Rahul-Thakur7/CVE-2023-21554 | 0 | 2024-12-16 |
Detection Rules
Detection availableCommunity detection & vulnerability-scanning rules aggregated from Sigma and Nuclei templates. Validate and tune to your environment before deploying.
Sigma rules 3
Acknowledgments
Haifei Li with Check Point Research
Wayne Low of Fortinet's FortiGuard Lab