dbcve.org
MqApplication · Ibm

CVE-2024-54175

MEDIUM · 5.5 CVSS v3.1 Published 2025-02-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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, 9.3 CD, 9.4 LTS, and 9.4 CD could allow a local user to cause a denial of service due to an improper check for unusual or exceptional conditions.

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.3 LTS, 9.3 CD, 9.4 LTS, and 9.4 CD contain a denial of service vulnerability where a local user can trigger a crash due to improper error handling. The vulnerability stems from the software failing to properly check for unusual or exceptional conditions, allowing a locally authenticated user to cause the MQ queue manager to become unavailable.

MitigationApply IBM's security patch for this vulnerability. As a compensating control, restrict local user access to the MQ server to trusted administrators only until the patch can be deployed.

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= 9.4.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/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. Confirm IBM MQ is installed
    Run 'dspmqver' on Linux/Unix or check Windows Services for IBM MQ Queue Manager service
    Affected if IBM MQ software is present on the system
  2. Identify the installed MQ version
    Execute 'dspmqver -a' or check the queue manager properties via 'runmqsc' with DISPLAY QMGR ALL
    Affected if The displayed version falls within 9.3.0-9.3.x or 9.4.0-9.4.x
  3. Determine the release type
    Check if the installation is LTS (Long Term Support) or CD (Continuous Delivery) by reviewing the version string from dspmqver
    Affected if The release is 9.3 LTS, 9.3 CD, 9.4 LTS, or 9.4 CD and version matches 9.3.0 or 9.4.0 through respective minor versions
  4. Verify local user access to MQ
    Review OS-level user permissions to MQ binaries, directories, and queue manager resources using 'mqaut' or OS user/group membership checks
    Affected if Non-administrator local users have access to the MQ queue manager environment

A system is affected if it runs IBM MQ version 9.3.0 through 9.3.x or 9.4.0 through 9.4.x and allows local authenticated users access to the queue manager.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM's security patch for this vulnerability. As a compensating control, restrict local user access to the MQ server to trusted administrators only until the patch can be deployed.

Fix this in Mq Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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