dbcve.org
MqApplication · Ibm

CVE-2024-31912

HIGH · 8.8 CVSS v3.1 Published 2024-06-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM MQ 9.3 LTS and 9.3 CD could allow an authenticated user to escalate their privileges under certain configurations due to incorrect privilege assignment. IBM X-Force ID: 289894.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

IBM MQ 9.3 LTS and 9.3 CD contains a privilege escalation vulnerability where an authenticated user can obtain elevated privileges due to incorrect privilege assignment in certain configurations. This allows users to perform actions beyond their intended authorization level.

MitigationReview IBM MQ authorization configurations and apply vendor patches when available. Ensure least-privilege principles are followed in queue manager access controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MqApplication
Affected:= 9.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM MQ installation and version
    Run 'dspmqver' or check /opt/mqm directory for version files. On Windows, check Program Files/IBM/MQ. On Linux/Unix, check /opt/mqm
    Affected if Installed version is exactly 9.3.0
  2. Confirm queue manager is running
    Run 'dspmq' or 'runmqsc -q QMGRNAME' to list active queue managers. The vulnerability requires an active queue manager to exploit
    Affected if A queue manager is running on version 9.3.0
  3. Review authorization configuration
    Use 'runmqsc QMGRNAME' and run 'DISPLAY AUTHREC' to view authorization records. Check for any records with elevated privileges (AUTHOPT) assigned to non-admin users
    Affected if Authorization records exist that grant elevated permissions beyond the user's intended authorization level
  4. Check for improper privilege assignments
    Review output of 'DISPLAY AUTHREC PROFILE' for any queue manager, queue, or topic objects where PRIVS or AUTHOPT settings grant more privilege than expected for authenticated users
    Affected if User authorization records show privileges beyond what was explicitly configured for their role

Your environment is affected if IBM MQ version 9.3.0 is installed and running with authorization configurations that allow authenticated users to gain privileges beyond their assigned authorization level.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review IBM MQ authorization configurations and apply vendor patches when available. Ensure least-privilege principles are followed in queue manager access controls.

Recommended fix Moderate confidence

IBM MQ 9.3.0.1 (or later fix pack)

  1. 1. Identify the current IBM MQ version by running 'dspmqver' command or checking the installation details
  2. 2. Download IBM MQ 9.3.0.1 or later fix pack from IBM Fix Central (https://www.ibm.com/support/fixcentral/)
  3. 3. Review IBM MQ upgrade documentation for your platform (Linux, Windows, AIX, etc.)
  4. 4. Stop all IBM MQ processes and queue managers before applying the upgrade
  5. 5. Apply the fix pack following IBM's standard installation procedure for your platform
  6. 6. Restart queue managers and verify the upgrade using 'dspmqver'
  7. 7. Test that the privilege escalation vulnerability is no longer exploitable in your environment
Caveat Review IBM MQ 9.3 fix pack release notes for any compatibility changes or deprecated features before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mq Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31912 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-31912 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data