IBM MQ up to 9.1.2 Cluster resource consumption

Summaryinfo

A vulnerability was found in IBM MQ up to 9.1.2. It has been rated as problematic. This affects an unknown part of the component Cluster. Performing a manipulation results in resource consumption. This vulnerability is known as CVE-2019-4141. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in IBM MQ up to 9.1.2. It has been classified as problematic. This affects an unknown function of the component Cluster. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is:

IBM MQ 7.1.0.0 - 7.1.0.9, 7.5.0.0 - 7.5.0.9, 8.0.0.0 - 8.0.0.11, 9.0.0.0 - 9.0.0.6, 9.1.0.0 - 9.1.0.2, and 9.1.1 - 9.1.2 is vulnerable to a denial of service attack caused by a memory leak in the clustering code. IBM X-Force ID: 158337.

The weakness was published 09/27/2019 (Website). The advisory is shared at exchange.xforce.ibmcloud.com. This vulnerability is uniquely identified as CVE-2019-4141 since 01/03/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. The successful exploitation requires a authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/28/2023). It is expected to see the exploit prices for this product increasing in the near future.MITRE ATT&CK project uses the attack technique T1499 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• IBM

Name

• MQ

Version

• 7.1.0.0
• 7.1.0.1
• 7.1.0.2
• 7.1.0.3
• 7.1.0.4
• 7.1.0.5
• 7.1.0.6
• 7.1.0.7
• 7.1.0.8
• 7.1.0.9
• 7.5.0.0
• 7.5.0.1
• 7.5.0.2
• 7.5.0.3
• 7.5.0.4
• 7.5.0.5
• 7.5.0.6
• 7.5.0.7
• 7.5.0.8
• 7.5.0.9
• 8.0.0.0
• 8.0.0.1
• 8.0.0.2
• 8.0.0.3
• 8.0.0.4
• 8.0.0.5
• 8.0.0.6
• 8.0.0.7
• 8.0.0.8
• 8.0.0.9
• 8.0.0.10
• 8.0.0.11
• 9.0.0.0
• 9.0.0.1
• 9.0.0.2
• 9.0.0.3
• 9.0.0.4
• 9.0.0.5
• 9.0.0.6
• 9.1.0
• 9.1.0.0
• 9.1.0.1
• 9.1.0.2
• 9.1.1
• 9.1.2

License

• commercial

Website

• Vendor: https://www.ibm.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion