dbcve.org
MqApplication · Ibm

CVE-2023-45177

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-20
Fix available
A fix is available. Upgrade to 9.0.0.21 / 9.1.0.18 or later.
See remediation →
59/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.0 LTS, 9.1 LTS, 9.2 LTS, 9.3 LTS and 9.3 CD is vulnerable to a denial-of-service attack due to an error within the MQ clustering logic. IBM X-Force ID: 268066.

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 versions 9.0 LTS, 9.1 LTS, 9.2 LTS, 9.3 LTS and 9.3 CD contain a denial-of-service vulnerability stemming from an error in the MQ clustering logic. An unauthenticated remote attacker could exploit this flaw to cause a DoS condition affecting the clustering functionality.

MitigationApply the IBM security patch for CVE-2023-45177 to all affected IBM MQ installations. In clustered environments, plan maintenance windows to apply patches to all queue managers in the cluster and verify clustering functionality after patching.

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.21>= 9.1.0.0, < 9.1.0.18>= 9.2.0.0, < 9.2.0.20>= 9.3.0, < 9.3.4>= 9.3.0.0, <= 9.3.0.10

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

CVSS:3.1/AV:N/AC:H/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. Determine installed IBM MQ version
    Run 'dspmqver' command on the queue manager host, or check the version via the MQ Explorer GUI under Queue Manager Properties, or query the qmgr.ini file for version information
    Affected if The version falls within any of these ranges: 9.0.0.0 through 9.0.0.20, 9.1.0.0 through 9.1.0.17, 9.2.0.0 through 9.2.0.19, 9.3.0 through 9.3.3, or 9.3.0.0 through 9.3.0.10
  2. Verify clustering is configured
    Check for cluster objects using 'DISPLAY CLUSTER' MQSC command, or inspect qmgr.ini for cluster definitions, or look for CLUSSDR and CLUSRCVR channel definitions via 'DISPLAY CHANNEL(*) TYPE(CLUSSDR)' and 'DISPLAY CHANNEL(*) TYPE(CLUSRCVR)'
    Affected if The queue manager is a member of any cluster (full repository, partial repository, or cluster sender/receiver channel is defined)
  3. Confirm cluster channels are active
    Run 'DISPLAY CHSTATUS(*) TYPE(CLUSRCVR)' and 'DISPLAY CHSTATUS(*) TYPE(CLUSSDR)' to check the status of cluster channels, or check if cluster receiver channels are in BINDING or RUNNING state
    Affected if Cluster channels are in a RUNNING or BINDING state, indicating the cluster is active and accessible

You are affected if your IBM MQ version is within the affected ranges AND clustering functionality is enabled on your 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.

dbcve · scoped
Upgrade available Upgrade to 9.0.0.21 / 9.1.0.18 / 9.2.0.20 or later
Fixed in 9.0.0.219.1.0.189.2.0.20
Interim mitigation

Apply the IBM security patch for CVE-2023-45177 to all affected IBM MQ installations. In clustered environments, plan maintenance windows to apply patches to all queue managers in the cluster and verify clustering functionality after patching.

Recommended fix High confidence

Upgrade to IBM MQ 9.0.0.21 (LTS), 9.1.0.18 (LTS), 9.2.0.20 (LTS), or 9.3.4 (LTS/CD) depending on your release line

  1. 1. Identify the current IBM MQ version by running 'dspmqver' or checking the installation directory
  2. 2. Determine which LTS or CD release line is in use (9.0.x, 9.1.x, 9.2.x, or 9.3.x)
  3. 3. Plan maintenance window for the upgrade, as queue managers will require restart
  4. 4. Back up all IBM MQ configuration data, including queue manager definitions, channel definitions, and ini files
  5. 5. Download the appropriate fix pack from IBM Fix Central (search for APAR IT42667)
  6. 6. Stop all queue managers gracefully using 'endmqm -w <qmgrname>' for each queue manager
  7. 7. Stop all IBM MQ services and listeners
  8. 8. Install the upgrade following IBM installation documentation for your platform (Windows, Linux, AIX, etc.)
Caveat Standard IBM MQ patch upgrades typically preserve configuration; however, always review IBM's release notes for any compatibility notes between your current and target version

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

Fix this in Mq Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA1.0 h
13.0 hours of engineering $2,260
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,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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