Authenticated queue crash via crafted message
Published Mar 16, 2020 · Updated Sep 17, 2024
A denial-of-service flaw in IBM MQ allows remote authenticated users to crash a queue manager by sending a malicious message. Error-message processing incorrectly marks the affected queue as damaged when it handles the crafted message. An authenticated messaging user can trigger the condition remotely, causing service interruption until the queue manager is restarted.
Summary
What happened
A denial-of-service flaw in IBM MQ allows remote authenticated users to crash a queue manager by sending a malicious message. Error-message processing incorrectly marks the affected queue as damaged when it handles the crafted message. An authenticated messaging user can trigger the condition remotely, causing service interruption until the queue manager is restarted.
The record
- CVE
- CVE-2019-4656
- Published
- Mar 16, 2020
- Updated
- Sep 17, 2024
- Vendor
- IBM
- Product
- IBM MQ
- Classifications
- T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 16, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=7.1.0.0
- Affected versionversion=7.1.0.1
- Affected versionversion=7.1.0.2
- Affected versionversion=7.1.0.3
- Affected versionversion=7.1.0.4
- Affected versionversion=7.1.0.5
- Affected versionversion=7.1.0.6
- Affected versionversion=7.1.0.7
- Affected versionversion=7.1.0.8
- Affected versionversion=7.1.0.9
- Affected versionversion=7.5.0.0
- Affected versionversion=7.5.0.1
- Affected versionversion=7.5.0.2
- Affected versionversion=7.5.0.3
- Affected versionversion=7.5.0.4
- Affected versionversion=7.5.0.5
- Affected versionversion=7.5.0.6
- Affected versionversion=7.5.0.7
- Affected versionversion=7.5.0.8
- Affected versionversion=7.5.0.9
- Affected versionversion=8.0.0.0
- Affected versionversion=8.0.0.1
- Affected versionversion=8.0.0.10
- Affected versionversion=8.0.0.11
- Affected versionversion=8.0.0.12
- Affected versionversion=8.0.0.13
- Affected versionversion=8.0.0.2
- Affected versionversion=8.0.0.3
- Affected versionversion=8.0.0.4
- Affected versionversion=8.0.0.5
- Affected versionversion=8.0.0.6
- Affected versionversion=8.0.0.7
- Affected versionversion=8.0.0.8
- Affected versionversion=8.0.0.9
- Affected versionversion=9.0.0.0
- Affected versionversion=9.0.0.1
- Affected versionversion=9.0.0.2
- Affected versionversion=9.0.0.3
- Affected versionversion=9.0.0.4
- Affected versionversion=9.0.0.5
- Affected versionversion=9.0.0.6
- Affected versionversion=9.0.0.7
- Affected versionversion=9.0.0.8
- Affected versionversion=9.1
- Affected versionversion=9.1.0.1
- Affected versionversion=9.1.0.2
- Affected versionversion=9.1.0.3
- Affected versionversion=9.1.1
- Affected versionversion=9.1.2
- Affected versionversion=9.1.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo