CVE-2019-4656
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 · uneditedIBM MQ and IBM MQ Appliance 7.1, 7.5, 8.0, 9.0 LTS, 9.1 LTS, and 9.1 CD is vulnerable to a denial of service attack that would allow an authenticated user to crash the queue and require a restart due to an error processing error messages. IBM X-Force ID: 170967.
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 confidenceIBM MQ and IBM MQ Appliance versions 7.1, 7.5, 8.0, 9.0 LTS, 9.1 LTS, and 9.1 CD contain a denial of service vulnerability where an authenticated user can trigger a crash of the queue manager by sending specially crafted error messages, requiring a restart to recover.
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>= 8.0.0.0, < 8.0.0.14>= 9.0.0.0, <= 9.0.0.9>= 9.1.0, < 9.1.4>= 9.1.0.0, < 9.1.0.4>= 8.0.0.0, < 8.0.0.14>= 7.1.0.0, <= 7.5.0.9CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine IBM MQ installed versionRun 'dspmqver -a' on Linux/Unix or check the queue manager properties in IBM MQ Explorer on Windows. On Windows, also check the version via the IBM MQ Services control panel or 'mqversion' command if available.Affected if The displayed version falls within any of these ranges: 8.0.0.0 to 8.0.0.13, 9.0.0.0 to 9.0.0.9, 9.1.0 to 9.1.3, 9.1.0.0 to 9.1.0.3, or 7.1.0.0 to 7.5.0.9 for WebSphere MQ.
-
Confirm product typeIdentify whether the installation is IBM MQ (server), IBM MQ Appliance, or IBM WebSphere MQ. Use 'dspmqver' output which shows product name and platform, or check the appliance model if hardware appliance.Affected if Product is IBM MQ Appliance with version 8.0.0.0 to 8.0.0.13.
-
Verify queue manager accessibilityCheck if queue manager is running using 'dspmq' command. Verify administrative or user access permissions exist by checking channel definitions and connection permissions in the queue manager configuration.Affected if Queue manager is active and user has authenticated access to submit commands or messages to the queue manager.
Your environment is affected if the installed IBM MQ, IBM MQ Appliance, or WebSphere MQ version matches the affected ranges AND an authenticated user can submit commands or messages to the queue manager.
Generated from the published advisory. Verify against your own configuration.
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 data8.0.0.149.1.0.49.1.4
Apply the appropriate IBM MQ security patch or upgrade to a supported version. Restrict queue manager administrative access to trusted personnel only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4656 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-4656 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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