dbcve.org
Mq ApplianceApplication · Ibm

CVE-2025-3631

HIGH · 7.5 CVSS v3.1 Published 2025-07-11
Fix available
A fix is available. Upgrade to 9.4.0.12 / 9.4.3 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
An IBM MQ 9.3 and 9.4 Client connecting to an MQ Queue Manager can cause a SIGSEGV in the AMQRMPPA channel process terminating it.

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

An IBM MQ 9.3 or 9.4 Client connecting to an MQ Queue Manager triggers a memory corruption error in the AMQRMPPA channel process, causing a SIGSEGV (segmentation fault) that terminates the channel process, resulting in denial of service for affected connections.

MitigationApply IBM MQ security fixes or patches when released by IBM. Until a patch is available, implement network segmentation and access controls to limit which clients can connect to 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.2, <= 9.3.5.2>= 9.4.0.0, < 9.4.0.12>= 9.4.0.0, < 9.4.3>= 9.4.1.0, < 9.4.3.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
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. Identify MQ Queue Manager version
    Run 'dspmqver' on the appliance or queue manager system, or check the MQ installation directory for version information
    Affected if Version falls within 9.3.2 to 9.3.5.2, 9.4.0.0 to 9.4.0.11, or 9.4.1.0 to 9.4.2.x ranges
  2. Verify AMQRMPPA channel process is in use
    Check running processes for 'amqrmppa' or review active channel definitions using 'DISPLAY CHANNEL(*) CHLTYPE(SDR)' or 'DISPLAY CHANNEL(*) CHLTYPE(CLNTCONN)' commands via runmqsc
    Affected if AMQRMPPA channels are defined and active for client connections
  3. Confirm client connection listeners are active
    Run 'DISPLAY LISTENER(*)' via runmqsc or check for processes listening on port 1414 (default MQ port)
    Affected if A listener is running that accepts client connections
  4. Review system logs for SIGSEGV events
    Check /var/mqm/errors or system crash logs for 'SIGSEGV' and 'AMQRMPPA' entries indicating recent channel process crashes
    Affected if Recent crash logs show AMQRMPPA segmentation faults occurring

You are affected if your MQ Queue Manager version is within the listed ranges and client connections via AMQRMPPA channels are active, especially if crash logs show related segmentation faults.

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.4.0.12 / 9.4.3 / 9.4.3.0 or later
Fixed in 9.4.0.129.4.39.4.3.0
Interim mitigation

Apply IBM MQ security fixes or patches when released by IBM. Until a patch is available, implement network segmentation and access controls to limit which clients can connect to the queue manager.

Recommended fix Moderate confidence

Upgrade to IBM MQ 9.3.5.3+ (9.3.x) or 9.4.0.12+ (9.4.0.x) or 9.4.3.0+ (9.4.1.x/9.4.2.x) - choose the latest available fix pack in your release branch

  1. 1. Identify the currently installed IBM MQ Appliance version using the 'mqver' command or checking the system dashboard.
  2. 2. Based on the installed version branch, plan the upgrade:
  3. - If running 9.3.x: Upgrade to version 9.3.5.3 or later (9.3.6 LTS if available)
  4. - If running 9.4.0.x: Upgrade to version 9.4.0.12 or later
  5. - If running 9.4.1.x or 9.4.2.x: Upgrade to version 9.4.3.0 or later
  6. 3. Before upgrading, review IBM MQ Appliance upgrade documentation and ensure backup of configuration.
  7. 4. Download the appropriate IBM MQ Appliance fix pack from IBM Fix Central (https://www.ibm.com/support/fixcentral/).
  8. 5. Apply the upgrade during a maintenance window following IBM's standard upgrade procedure for MQ Appliance.
Caveat IBM MQ fix packs are generally cumulative; review release notes for any compatibility notes or deprecated features before upgrading

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

Fix this in Mq Appliance Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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