dbcve.org
Mq ApplianceApplication · Ibm

CVE-2024-25048

HIGH · 7.5 CVSS v3.1 Published 2024-04-27
Fix available
A fix is available. Upgrade to 9.3.0.17 / 9.3.5 or later.
See remediation →
81/100
Remediation priority · High
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 Appliance 9.3 CD and LTS are vulnerable to a heap-based buffer overflow, caused by improper bounds checking. A remote authenticated attacker could overflow a buffer and execute arbitrary code on the system or cause the server to crash. IBM X-Force ID: 283137.

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 Appliance versions 9.3 CD and LTS contain a heap-based buffer overflow vulnerability due to improper bounds checking. A remote authenticated attacker can overflow a heap buffer, potentially leading to arbitrary code execution or denial of service by crashing the server.

MitigationApply the vendor-supplied patch for IBM MQ Appliance 9.3 CD and LTS. Prior to production deployment, test the update in a non-production environment to verify functionality and schedule during a maintenance window due to the critical nature of the queue manager.

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
Mq ApplianceApplication
Affected:>= 9.3.0.0, < 9.3.0.17>= 9.3.0.0, < 9.3.5

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Confirm you are running IBM MQ Appliance
    Check the product type - this vulnerability affects only IBM MQ Appliance, not IBM MQ Server or Client. Verify through appliance console or run 'DSPMQVER' if available, looking for 'Appliance' in the output.
    Affected if The product is IBM MQ Appliance (different from IBM MQ server/client)
  2. Determine the installed IBM MQ Appliance version
    Access the appliance console or use the command line to run the version display command (typically 'version' or through mqsc 'DISPLAY QMGR'). Look for the version string (e.g., 9.3.0.x).
    Affected if Version is 9.3.0.0 through 9.3.0.16, or any version below 9.3.5.0 on the LTS track
  3. Verify the queue manager is running
    Check if a queue manager is active on the appliance using 'dspmq' or through the appliance interface. The vulnerability requires an authenticated connection to exploit.
    Affected if A queue manager is running and accepting network connections
  4. Check for network-exposed listeners
    Review listener configurations using 'DISPLAY LISTENER(*)' via mqsc. Determine if the listener port (typically 1414) is accessible from network rather than localhost only.
    Affected if A listener is configured and reachable from untrusted networks

You are affected if you run IBM MQ Appliance versions 9.3.0.0 through 9.3.0.16, or 9.3.x versions below 9.3.5, with an active queue manager and accessible network listener.

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.3.0.17 / 9.3.5 or later
Fixed in 9.3.0.179.3.5
Interim mitigation

Apply the vendor-supplied patch for IBM MQ Appliance 9.3 CD and LTS. Prior to production deployment, test the update in a non-production environment to verify functionality and schedule during a maintenance window due to the critical nature of the queue manager.

Recommended fix High confidence

IBM MQ Appliance 9.3.5 (CD) or 9.3.0.17 (LTS)

  1. 1. Identify the current IBM MQ Appliance version using the command: `show version` or through the web console
  2. 2. Determine if the deployment is using the Continuous Delivery (CD) or Long Term Support (LTS) release train
  3. 3. For CD releases: Plan upgrade to version 9.3.5 or later
  4. 4. For LTS releases: Plan upgrade to version 9.3.0.17 or later
  5. 5. Download the appropriate fix from IBM Fix Central (https://www.ibm.com/support/fixcentral/) or through your IBM entitlement
  6. 6. Review IBM MQ Appliance upgrade documentation for the specific upgrade procedure
  7. 7. Perform the upgrade following IBM's standard upgrade process for MQ Appliance
  8. 8. Verify the upgrade was successful by checking the version with `show version`
Caveat Check IBM MQ Appliance 9.3 release notes for any known compatibility issues or behavioral changes between versions

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

Fix this in Mq Appliance Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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