dbcve.org
Mq ApplianceApplication · Ibm

CVE-2024-51470

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-18
Fix available
A fix is available. Upgrade to 8.1.0.26 / 9.1.0.26 or later.
See remediation →
71/100
Remediation priority · Elevated
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.1 LTS, 9.2 LTS, 9.3 LTS, 9.3 CD, 9.4 LTS, 9.4 CD, IBM MQ Appliance 9.3 LTS, 9.3 CD, 9.4 LTS, and IBM MQ for HPE NonStop 8.1.0 through 8.1.0.25 could allow an authenticated user to cause a denial-of-service due to messages with improperly set values.

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 versions 9.1 LTS through 9.4 CD and MQ Appliance versions 9.3-9.4 LTS/CD contain a denial-of-service vulnerability where authenticated users can send messages with improperly set values, causing the queue manager to become unavailable. The vulnerability stems from insufficient validation of message properties or header fields.

MitigationApply IBM's security patch for CVE-2024-51470 when released. Until then, restrict queue manager access to trusted users only and monitor for abnormal queue manager restarts or failures.

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.1.0.0, < 9.1.0.26>= 9.2.0.0, < 9.2.0.30>= 9.3.0.0, < 9.3.0.26>= 9.4.0.0, < 9.4.0.7
Mq For Hpe NonstopApplication
Affected:>= 8.1.0, < 8.1.0.26

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 IBM MQ version on Windows or Linux
    Run 'dspmqver' command or check /opt/mqm/bin/dspmqver on Linux, or inspect Windows registry at HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion
    Affected if version is 9.1.x < 9.1.0.26, 9.2.x < 9.2.0.30, 9.3.x < 9.3.0.26, or 9.4.x < 9.4.0.7
  2. Check IBM MQ Appliance version
    Log into the appliance CLI and run 'show version' or check the web console for the firmware version
    Affected if version is 9.1.0.0-9.1.0.25, 9.2.0.0-9.2.0.29, 9.3.0.0-9.3.0.25, or 9.4.0.0-9.4.0.6
  3. Check IBM MQ for HPE Nonstop version
    Inspect the installation directory or run the version command specific to the Nonstop platform
    Affected if version is 8.1.0 through 8.1.0.25
  4. Verify queue manager accessibility
    Review user authorities using 'display authrec' MQSC command or MQ Explorer user security settings to determine if untrusted or external users have PUT or INQ privileges on queues
    Affected if untrusted or external authenticated users have queue access privileges
  5. Check for queue manager failures
    Review queue manager logs (AMQERR01.LOG) for unexpected terminations or look for event log entries indicating queue manager restarts
    Affected if queue manager has experienced unexpected restarts or failures without clear cause

Your environment is affected if you run any affected IBM MQ or MQ Appliance version AND have untrusted authenticated users with queue access, especially if you observe unexplained queue manager failures.

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 8.1.0.26 / 9.1.0.26 / 9.2.0.30 or later
Fixed in 8.1.0.269.1.0.269.2.0.30
Interim mitigation

Apply IBM's security patch for CVE-2024-51470 when released. Until then, restrict queue manager access to trusted users only and monitor for abnormal queue manager restarts or failures.

Recommended fix High confidence

IBM MQ Appliance 9.1.0.26, 9.2.0.30, 9.3.0.26, or 9.4.0.7; IBM MQ for HPE NonStop 8.1.0.26

  1. Identify the specific IBM MQ product and version currently installed using IBM MQ commands or appliance CLI
  2. For IBM MQ Appliance: Determine which LTS or CD version line is in use (9.1, 9.2, 9.3, or 9.4)
  3. For IBM MQ for HPE NonStop: Note the current 8.1.0.x version
  4. Download the appropriate fixed version from IBM Fix Central or IBM Passport Advantage: 9.1.0.26, 9.2.0.30, 9.3.0.26, 9.4.0.7 for Appliance; 8.1.0.26 for HPE NonStop
  5. Follow IBM's standard upgrade procedure for the specific product: for Appliance use the firmware update process via web GUI or CLI; for HPE NonStop follow the platform-specific upgrade instructions
  6. After upgrade, verify the new version is running and test that IBM MQ functions normally
  7. Monitor IBM MQ for any issues and review system logs to confirm the DoS vulnerability is remediated
Caveat Upgrade follows standard IBM MQ version maintenance procedures; ensure compatibility with existing queue manager configurations and applications

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

Fix this in Mq Appliance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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