dbcve.org
MqApplication · Ibm

CVE-2024-25016

HIGH · 7.5 CVSS v3.1 Published 2024-03-03
Fix available
A fix is available. Upgrade to 9.0.0.23 / 9.1.0.20 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 and IBM MQ Appliance 9.0, 9.1, 9.2, 9.3 LTS and 9.3 CD could allow a remote unauthenticated attacker to cause a denial of service due to incorrect buffering logic. IBM X-Force ID: 281279.

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 · high confidence

IBM MQ and IBM MQ Appliance versions 9.0 through 9.3 contain incorrect buffering logic that allows a remote unauthenticated attacker to cause a denial of service condition.

MitigationApply IBM's security patches for CVE-2024-25016 to all affected IBM MQ queue managers and appliances. Consider network segmentation to limit exposure to untrusted networks.

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.0.0.0, < 9.0.0.23>= 9.1.0.0, < 9.1.0.20>= 9.2.0, < 9.2.0.22>= 9.3.0, < 9.3.0.16
Mq ApplianceApplication
Affected:>= 9.3.0.0, <= 9.3.5.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Verify IBM MQ installation exists
    Run command 'dspmqver' on Linux/Unix or check Windows Services for 'IBM MQ' service, or inspect installation directory (default: /opt/mqm on Linux)
    Affected if IBM MQ software is installed on the system
  2. Identify product type (Queue Manager vs Appliance)
    For Queue Manager, run 'dspmq' to list queue managers. For Appliance, access the appliance via SSH or web console and run 'version' command
    Affected if Product is either IBM MQ Queue Manager or IBM MQ Appliance
  3. Obtain exact installed version number
    Run 'dspmqver -a' (Queue Manager) or 'version' (Appliance). Look for version string such as 9.3.0.0, 9.2.0.15, etc.
    Affected if Version cannot be determined or is not displayed
  4. Compare version against affected ranges
    Check version against: IBM MQ 9.0.0.0-9.0.0.22, 9.1.0.0-9.1.0.19, 9.2.0-9.2.0.21, 9.3.0-9.3.0.15; IBM MQ Appliance 9.3.0.0-9.3.5.0
    Affected if Installed version falls within any of the affected ranges listed

System is affected if IBM MQ (Queue Manager or Appliance) is installed with a version matching the affected ranges, as the vulnerability is triggered by network requests to exposed listeners.

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
Upgrade available Upgrade to 9.0.0.23 / 9.1.0.20 / 9.2.0.22 or later
Fixed in 9.0.0.239.1.0.209.2.0.22
Interim mitigation

Apply IBM's security patches for CVE-2024-25016 to all affected IBM MQ queue managers and appliances. Consider network segmentation to limit exposure to untrusted networks.

Recommended fix High confidence

IBM MQ 9.0.0.23, 9.1.0.20, 9.2.0.22, or 9.3.0.16 (or latest LTS/CD release); IBM MQ Appliance 9.3.0.16 or later

  1. 1. Identify the currently installed IBM MQ or IBM MQ Appliance version and edition (LTS or CD) using the dspmqver command or Appliance web console.
  2. 2. Determine the appropriate target fix pack based on your current version: for 9.0.x go to 9.0.0.23, for 9.1.x go to 9.1.0.20, for 9.2.x go to 9.2.0.22, for 9.3.x go to 9.3.0.16 or later.
  3. 3. Download the corresponding fix pack from IBM Fix Central (https://www.ibm.com/support/fixcentral) or IBM Passport Advantage.
  4. 4. Review the installation instructions in the IBM MQ Knowledge Center for your specific platform and version.
  5. 5. Schedule a maintenance window and create backups of queue manager data and configuration.
  6. 6. Stop all queue managers and IBM MQ services before applying the fix pack.
  7. 7. Install the fix pack using the appropriate method for your platform (Installation Wizard, console, or response file).
  8. 8. Verify the installation completed successfully and confirm the new version is running using dspmqver.
Caveat Review IBM MQ release notes for migration considerations; some configuration changes or API behavior may differ between major versions

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

Fix this in Mq Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25016 — 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-25016 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