Windows Message Queuing Client (MSMQC) Information Disclosure
The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Windows_10_1507 | Microsoft | * | 10.0.10240.20402 (excluding) |
| Windows_10_1607 | Microsoft | * | 10.0.14393.6614 (excluding) |
| Windows_10_1809 | Microsoft | * | 10.0.17763.5329 (excluding) |
| Windows_10_21h2 | Microsoft | * | 10.0.19044.3930 (excluding) |
| Windows_10_22h2 | Microsoft | * | 10.0.19045.3930 (excluding) |
| Windows_11_21h2 | Microsoft | * | 10.0.22000.2713 (excluding) |
| Windows_11_22h2 | Microsoft | * | 10.0.22621.3007 (excluding) |
| Windows_11_23h2 | Microsoft | * | 10.0.22631.3007 (excluding) |
| Windows_server_2008 | Microsoft | –sp2 (including) | –sp2 (including) |
| Windows_server_2012 | Microsoft | - (including) | - (including) |
| Windows_server_2012 | Microsoft | r2 (including) | r2 (including) |
| Windows_server_2016 | Microsoft | - (including) | - (including) |
| Windows_server_2019 | Microsoft | - (including) | - (including) |
| Windows_server_2022 | Microsoft | - (including) | - (including) |
An attacker can supply a pointer for memory locations that the product is not expecting. If the pointer is dereferenced for a write operation, the attack might allow modification of critical state variables, cause a crash, or execute code. If the dereferencing operation is for a read, then the attack might allow reading of sensitive data, cause a crash, or set a variable to an unexpected value (since the value will be read from an unexpected memory location). There are several variants of this weakness, including but not necessarily limited to: