Service crash via improper memory allocation
Published Sep 7, 2024 · Updated Oct 31, 2024
Improper memory allocation in the IBM MQ Server component in IBM MQ 9.3 CD and 9.4 LTS/CD allows local users to crash the service. IBM identifies the failure as a segmentation fault caused by improper memory allocation but does not disclose the responsible function or attacker-controlled input. Local access is required, and successful exploitation interrupts the affected IBM MQ Server process without reported data disclosure or modification.
Summary
What happened
Improper memory allocation in the IBM MQ Server component in IBM MQ 9.3 CD and 9.4 LTS/CD allows local users to crash the service. IBM identifies the failure as a segmentation fault caused by improper memory allocation but does not disclose the responsible function or attacker-controlled input. Local access is required, and successful exploitation interrupts the affected IBM MQ Server process without reported data disclosure or modification.
The record
- CVE
- CVE-2024-40680
- Published
- Sep 7, 2024
- Updated
- Oct 31, 2024
- Vendor
- IBM
- Product
- IBM MQ
- Classifications
- CWE-770, CWE-789, T1489
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 7, 2024CVE publishedPublication date reported by the CVE source.
- Oct 31, 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=9.3 CD, 9.4 LTS, 9.4 CD
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