CVE-2019-4560
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 9.1 CD, 9.1 LTS, 9.0 LTS, and 8.0 is vulnerable to a denial of service attack caused by channels processing poorly formatted messages. IBM X-Force ID: 166357.
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 channels contain a denial of service vulnerability when processing poorly formatted messages. An attacker can send malformed messages through MQ channels to cause the channel to become unresponsive or terminate, disrupting message flow between queue managers.
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.13>= 9.0.0.0, < 9.0.0.8>= 9.1.0.0, < 9.1.0.4>= 9.1.1, < 9.1.4CVSS 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.
-
Identify IBM MQ Appliance versionRun 'display version' command on the appliance console or check the IBM MQ version via mqsc command 'DISPLAY QMGR VERSION' or check /opt/mqm/installation/kbi/VERSION file if accessibleAffected if The installed version falls within: 8.0.0.0-8.0.0.12, 9.0.0.0-9.0.0.7, 9.1.0.0-9.1.0.3, or 9.1.1-9.1.3
-
Confirm MQ channels are configuredRun mqsc command 'DISPLAY CHANNEL(*)' to list all channel definitions, or check channel configuration files in /var/mqm/channels/ directoryAffected if Any defined channels exist and are active, as the vulnerability affects message processing through MQ channels
-
Verify channel listener statusRun 'DISPLAY LISTENER(*)' via mqsc or check if port 1414 (default MQ listener) is open via 'netstat -an | grep 1414'Affected if A listener is running and accepting connections, as malformed messages must be sent through an accessible channel endpoint
-
Check network exposure of MQ portsReview firewall rules or network ACLs controlling access to MQ listener ports (commonly 1414, 1415, 1416, 1417). Use 'netstat -an' or firewall-cmd/iptables to list open ports and their source restrictionsAffected if MQ listener ports are accessible from untrusted networks, as the attack requires sending malformed messages to the channel
You are affected if your IBM MQ Appliance version is within the vulnerable ranges AND MQ channels with an accessible listener are in use, allowing untrusted sources to send messages to the channel.
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.139.0.0.89.1.0.4
Apply the appropriate IBM MQ security patch (PTF) for the affected version (8.0, 9.0 LTS, or 9.1 LTS/CD). If immediate patching is not possible, implement network-level access controls to restrict untrusted sources from sending messages to MQ channels.
- Consultation2.0 h
- Implementation4.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4560 — 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-4560 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