IBM MQ could allow an authenticated attacker to cause a denial of service or potentially execute arbitrary code due to a heap buffer overflow when processing MQPUT or MQPUT1 operations with malformed message handle properties.
Weakness
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Mq_operator | Ibm | 2.0.0 (including) | 2.0.29 (including) |
| Mq_operator | Ibm | 3.2.0 (including) | 3.2.29 (including) |
| Mq_operator | Ibm | 3.3.0 (including) | 3.3.0 (including) |
| Mq_operator | Ibm | 3.4.0 (including) | 3.4.0 (including) |
| Mq_operator | Ibm | 3.4.1 (including) | 3.4.1 (including) |
| Mq_operator | Ibm | 3.5.0 (including) | 3.5.0 (including) |
| Mq_operator | Ibm | 3.5.1 (including) | 3.5.1 (including) |
| Mq_operator | Ibm | 3.5.2 (including) | 3.5.2 (including) |
| Mq_operator | Ibm | 3.5.3 (including) | 3.5.3 (including) |
| Mq_operator | Ibm | 3.6.0 (including) | 3.6.0 (including) |
| Mq_operator | Ibm | 3.6.1 (including) | 3.6.1 (including) |
| Mq_operator | Ibm | 3.6.2 (including) | 3.6.2 (including) |
| Mq_operator | Ibm | 3.6.3 (including) | 3.6.3 (including) |
| Mq_operator | Ibm | 3.6.4 (including) | 3.6.4 (including) |
| Mq_operator | Ibm | 3.7.0 (including) | 3.7.0 (including) |
| Mq_operator | Ibm | 3.7.1 (including) | 3.7.1 (including) |
| Mq_operator | Ibm | 3.7.2 (including) | 3.7.2 (including) |
| Mq_operator | Ibm | 3.8.0 (including) | 3.8.0 (including) |
| Mq_operator | Ibm | 3.8.1 (including) | 3.8.1 (including) |
| Mq_operator | Ibm | 3.9.0 (including) | 3.9.0 (including) |
| Mq_operator | Ibm | 3.9.1 (including) | 3.9.1 (including) |
| Mq_operator | Ibm | 3.9.2 (including) | 3.9.2 (including) |
| Mq_operator | Ibm | 4.0.0 (including) | 4.0.0 (including) |
| Mq_operator | Ibm | 4.0.1 (including) | 4.0.1 (including) |
| Mq_operator | Ibm | 4.0.2 (including) | 4.0.2 (including) |
| Mq_operator | Ibm | 4.0.3 (including) | 4.0.3 (including) |
| Mq_operator | Ibm | 4.0.4 (including) | 4.0.4 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.1.0-r1 (including) | 9.4.1.0-r1 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.1.0-r2 (including) | 9.4.1.0-r2 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.1.1-r1 (including) | 9.4.1.1-r1 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.2.0-r1 (including) | 9.4.2.0-r1 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.2.0-r2 (including) | 9.4.2.0-r2 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.2.1-r1 (including) | 9.4.2.1-r1 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.2.1-r2 (including) | 9.4.2.1-r2 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.3.0-r1 (including) | 9.4.3.0-r1 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.3.0-r2 (including) | 9.4.3.0-r2 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.3.1-r1 (including) | 9.4.3.1-r1 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.3.1-r2 (including) | 9.4.3.1-r2 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.3.1-r3 (including) | 9.4.3.1-r3 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.4.0-r1 (including) | 9.4.4.0-r1 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.4.0-r2 (including) | 9.4.4.0-r2 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.4.0-r3 (including) | 9.4.4.0-r3 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.4.0-r4 (including) | 9.4.4.0-r4 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.4.1-r1 (including) | 9.4.4.1-r1 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.5.0-r1 (including) | 9.4.5.0-r1 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.5.0-r2 (including) | 9.4.5.0-r2 (including) |
| Supplied_mq_advanced_container_images | Ibm | 9.4.5.1-r1 (including) | 9.4.5.1-r1 (including) |
| Supplied_mq_advanced_container_images | Ibm | 10.0.0.0-r1 (including) | 10.0.0.0-r1 (including) |
| Supplied_mq_advanced_container_images | Ibm | 10.0.0.0-r2 (including) | 10.0.0.0-r2 (including) |
| Supplied_mq_advanced_container_images | Ibm | 10.0.0.0-r3 (including) | 10.0.0.0-r3 (including) |
| Supplied_mq_advanced_container_images | Ibm | 10.0.0.0-r4 (including) | 10.0.0.0-r4 (including) |
| Supplied_mq_advanced_container_images | Ibm | 10.0.0.5-r1 (including) | 10.0.0.5-r1 (including) |
Potential Mitigations
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
- D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
- Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
- For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].