Authenticated privilege escalation via incorrect privilege assignment
Published Jun 28, 2024 · Updated Aug 2, 2024
Privilege escalation in IBM MQ 9.3 LTS and 9.3 CD allows remote authenticated users to obtain elevated server privileges. The affected Server component assigns privileges incorrectly under certain configurations; IBM has not disclosed the responsible code path, privilege boundary, or assignment logic. An existing low-privileged account and the affected configuration are required, and successful exploitation increases that account's authority over MQ server operations.
Summary
What happened
Privilege escalation in IBM MQ 9.3 LTS and 9.3 CD allows remote authenticated users to obtain elevated server privileges. The affected Server component assigns privileges incorrectly under certain configurations; IBM has not disclosed the responsible code path, privilege boundary, or assignment logic. An existing low-privileged account and the affected configuration are required, and successful exploitation increases that account's authority over MQ server operations.
The record
- CVE
- CVE-2024-31912
- Published
- Jun 28, 2024
- Updated
- Aug 2, 2024
- Vendor
- IBM
- Product
- IBM MQ
- Classifications
- CWE-266, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 28, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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 LTS and 9.3 CD
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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