dbcve.org
MqApplication · Ibm

CVE-2024-52897

MEDIUM · 6.2 CVSS v3.1 Published 2024-12-19
Fix available
A fix is available. Upgrade to 9.2.0.30 / 9.3.0.26 or later.
See remediation →
67/100
Remediation priority · Elevated
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, 9.3 CD, 9.4 LTS, and 9.4 CD web console could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned.

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

The IBM MQ web console returns detailed technical error messages that could expose sensitive system information, configuration details, or internal paths to remote attackers. This information disclosure through error messages (CWE-209) has a CVSS of 6.2, indicating moderate confidentiality impact.

MitigationConfigure the IBM MQ web console to return generic error messages instead of detailed technical errors, or apply any available IBM security patches for affected versions.

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.30>= 9.3.0, < 9.4.1>= 9.3.0.0, < 9.3.0.26>= 9.4.0.0, < 9.4.0.7

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 installed IBM MQ version
    Run 'dspmqver' or check the queue manager properties via 'runmqsc' with 'DISPLAY QMGR ALL' to determine the exact version number (e.g., 9.2.0.0, 9.3.0.5, 9.4.0.1)
    Affected if The installed version falls within any of these ranges: 9.2.0.0 through 9.2.0.29, 9.3.0.0 through 9.3.0.25, or 9.4.0.0 through 9.4.0.6
  2. Verify web console is enabled
    Check the web console status using 'mqwebstatus.sh' (Linux/Unix) or 'mqwebstatus.bat' (Windows), or query the MQWEB channel via 'runmqsc' with 'DISPLAY CHANNEL(MQWEBADMIN*)'
    Affected if The web console is running and accessible on ports 9443 or 9444 (default HTTPS) or 8080 (default HTTP)
  3. Test error message verbosity
    Trigger an error condition in the web console (e.g., submit an invalid request or manipulate a queue operation) and inspect the HTTP response body for detailed technical information such as stack traces, file paths, internal IP addresses, or configuration details
    Affected if The error response contains stack traces, Java exception details, absolute file paths, or internal system information rather than a generic error message

You are affected if your IBM MQ version is 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 AND the web console is enabled and returns detailed technical error content.

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.30 / 9.3.0.26 / 9.4.0.7 or later
Fixed in 9.2.0.309.3.0.269.4.0.7
Interim mitigation

Configure the IBM MQ web console to return generic error messages instead of detailed technical errors, or apply any available IBM security patches for affected versions.

Recommended fix Moderate confidence

Upgrade to 9.2.0.30 (LTS), 9.3.0.26 (LTS/CD), or 9.4.0.7 (LTS/CD) depending on current branch

  1. 1. Identify the current IBM MQ version by running 'dspmqver' or checking the IBM MQ installation
  2. 2. Determine which IBM MQ edition (LTS or CD) and version is currently installed
  3. 3. For IBM MQ 9.2 LTS: Upgrade to version 9.2.0.30 or later
  4. 4. For IBM MQ 9.3 LTS: Upgrade to version 9.3.0.26 or later
  5. 5. For IBM MQ 9.3 CD: Upgrade to version 9.3.0.26 or later
  6. 6. For IBM MQ 9.4 LTS: Upgrade to version 9.4.0.7 or later
  7. 7. For IBM MQ 9.4 CD: Upgrade to version 9.4.0.7 or later
  8. 8. Obtain the appropriate fix pack from IBM Fix Central (https://www.ibm.com/support/fixcentral/)
Caveat Check IBM MQ upgrade notes for potential compatibility considerations between major versions

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

Fix this in Mq Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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