dbcve.org
MqApplication · Ibm

CVE-2024-25015

HIGH · 7.5 CVSS v3.1 Published 2024-05-01
Fix available
A fix is available. Upgrade to 9.2.0.25 / 9.3.0.17 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 9.2 LTS, 9.3 LTS, and 9.3 CD Internet Pass-Thru could allow a remote user to cause a denial of service by sending HTTP requests that would consume all available resources. IBM X-Force ID: 281278.

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 Internet Pass-Thru (IPT) component contains a denial of service vulnerability where remote attackers can send specially crafted HTTP requests that exhaust all available system resources, causing the service to become unresponsive.

MitigationApply IBM's security patch for CVE-2024-25015 to IBM MQ 9.2 LTS, 9.3 LTS, and 9.3 CD installations, or implement rate limiting and request throttling on Internet Pass-Thru HTTP endpoints as a compensating control until patching is possible.

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.2.0.0, < 9.2.0.25>= 9.3.0, < 9.3.5>= 9.3.0.0, < 9.3.0.17

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. Check if IBM MQ is installed
    Run 'dspmqver' on Linux/Unix or check the installation directory on Windows (typically C:\Program Files\IBM\MQ on Windows or /opt/mqm on Linux/Unix)
    Affected if IBM MQ is not installed - the vulnerability does not apply
  2. Identify the installed IBM MQ version
    Run 'dspmqver -a' or check the version file in the installation directory (INSTALL_DIR/mqversion.txt or similar)
    Affected if The installed version falls within 9.2.0.0 to 9.2.0.24, 9.3.0.0 to 9.3.0.16, or 9.3.1.0 to 9.3.4.x (any version >= 9.3.0 but < 9.3.5)
  3. Determine if Internet Pass-Thru (IPT) is enabled
    Check the IBM MQ configuration for IPT components. On Linux/Unix, examine /var/mqm/mqat.ini or the queue manager's qm.ini file for 'InternetPassThru' or 'IPT' entries. On Windows, check the registry or configuration files under the MQ installation directory.
    Affected if Internet Pass-Thru component is configured and active - the DoS vulnerability requires IPT to be running
  4. Verify HTTP listeners are exposed
    Inspect queue manager configuration for HTTP channel listeners (amqzhace command, or check qm.ini for 'LISTENER' or 'HTTP' entries). Look for TCP listeners on ports typically used by IPT (default ports 1414, 9443, or custom HTTP ports).
    Affected if HTTP-based listeners are configured and reachable from the network - remote attackers need HTTP access to exploit the resource exhaustion flaw

A user is affected if they have IBM MQ version 9.2.0.0-9.2.0.24, 9.3.0.0-9.3.0.16, or 9.3.1.0-9.3.4.x installed AND the Internet Pass-Thru component is enabled with HTTP listeners accessible to remote attackers.

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.2.0.25 / 9.3.0.17 / 9.3.5 or later
Fixed in 9.2.0.259.3.0.179.3.5
Interim mitigation

Apply IBM's security patch for CVE-2024-25015 to IBM MQ 9.2 LTS, 9.3 LTS, and 9.3 CD installations, or implement rate limiting and request throttling on Internet Pass-Thru HTTP endpoints as a compensating control until patching is possible.

Recommended fix High confidence

IBM MQ 9.2.0.25+ (LTS) or 9.3.5+ (LTS) or 9.3.0.17+ (CD)

  1. 1. Identify the current IBM MQ version by running 'dspmqver' or checking the installation directory
  2. 2. Determine which IBM MQ edition (LTS or CD) is installed using 'dmpmqcfg' or the MQ explorer
  3. 3. For IBM MQ 9.2 LTS: Upgrade to version 9.2.0.25 or later by applying the latest fix pack from IBM Fix Central (https://www.ibm.com/support/fixcentral)
  4. 4. For IBM MQ 9.3 LTS: Upgrade to version 9.3.5 or later by applying the latest fix pack from IBM Fix Central
  5. 5. For IBM MQ 9.3 CD: Upgrade to version 9.3.0.17 or later by applying the latest continuous delivery fix pack
  6. 6. After upgrade, verify the Internet Pass-Thru (MQIPT) component is updated by checking the version with 'runmqipt -version'
  7. 7. Test the upgrade in a non-production environment before deploying to production
  8. 8. Backup all queue managers and configuration data before performing the upgrade
Caveat Review IBM MQ 9.2 and 9.3 release notes for any compatibility changes or migration requirements before upgrading

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

Fix this in Mq Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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