CVE-2019-4762
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 9.0 and 9.1 is vulnerable to a denial of service attack due to an error in the Channel processing function. IBM X-Force ID: 173625.
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 versions 9.0 and 9.1 contain a vulnerability in the Channel processing function that allows an unauthenticated attacker to trigger a denial of service condition. The issue stems from an error in how the Channel processing function handles certain inputs, causing the MQ service to become unavailable.
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>= 9.0.0.0, < 9.0.0.9>= 9.1.0, < 9.1.5>= 9.1.0.0, < 9.1.0.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check IBM MQ installed versionRun the command 'dspmqver' on the system where IBM MQ is installed. This displays version information including version, release, modification, and fix pack level.Affected if The installed version falls within 9.0.0.0 through 9.0.0.8, or 9.1.0.0 through 9.1.0.2, or 9.1.0 through 9.1.4.
-
Verify MQ channel listeners are configuredRun 'runmqsc -m QMNAM' and use the command 'DISPLAY LISTENER(*) STATUS' to list all channel listeners and their status. Alternatively, check /var/mqm/listener.xml or use the MQ Explorer GUI.Affected if Any channel listener (especially SVRCONN type) is in running status and accessible over the network.
-
Check network exposure of channel portsReview your firewall rules and run 'netstat -an | grep LISTEN' to identify ports where MQ listeners are bound (default ports 1414, 1415, 1416, 1417 or custom ports). Determine if these ports are exposed to untrusted networks.Affected if Channel listener ports are reachable from untrusted or external networks without proper network segmentation.
-
Review channel definitions for unauthenticated accessRun 'runmqsc -m QMNAM' and use 'DISPLAY CHANNEL(*) CHLTYPE' to list all channel definitions. Check for channels with 'MCAUSER(*)blank or generic' that may allow unauthenticated connections.Affected if Channels are configured to accept connections without requiring specific user authentication (blank or generic MCAUSER).
You are affected if your IBM MQ version is 9.0.0.0-9.0.0.8, 9.1.0.0-9.1.0.2, or 9.1.0-9.1.4 AND channel listeners are accessible over the network, since the vulnerability is triggered through the Channel processing function accessible via network listeners.
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 data9.0.0.99.1.0.39.1.5
Apply IBM security patches for IBM MQ 9.0 and 9.1 as provided in IBM's security bulletin. If immediate patching is not possible, restrict network access to MQ channel listeners and implement additional monitoring for anomalous channel activity.
- Consultation3.0 h
- Implementation3.0 h
- Testing3.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4762 — 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-4762 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