CVE-2017-1236
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 WebSphere MQ 9.0.2 could allow an authenticated user to potentially cause a denial of service by saving an incorrect channel status inquiry. IBM X-Force ID: 124354
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 WebSphere MQ 9.0.2 contains a denial of service vulnerability where an authenticated user can trigger a crash or service disruption by saving an incorrect channel status inquiry. The vulnerability stems from improper validation or handling of channel status inquiry data, allowing a specifically crafted request to cause the MQ queue manager 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.2CVSS 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.0/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.
-
Verify the installed IBM WebSphere MQ versionRun the dspmqver command or check the installation directory for version information. On Linux/Unix, use 'dspmqver -a'; on Windows, check via the IBM MQ Explorer or run 'dspmqver' in the installation bin directory.Affected if The installed version is exactly 9.0.2 (the only affected version listed). Versions before or after 9.0.2 are not affected by this specific CVE.
-
Confirm the queue manager is running and accessibleUse the runmqsc command to connect to the queue manager and run 'display qmgr' to verify its status. Alternatively, use 'dspmq' to list queue managers and their current state.Affected if The queue manager is running and accessible, making it available to receive channel status inquiry requests from authenticated users.
-
Identify users with channel administration privilegesRun 'display authinfo' or 'display channelauth' commands in runmqsc to review which users or groups have authority to administer channels. Also check mqsc scripts for 'set channelauth' statements.Affected if There are authenticated users granted channel administration or channel status inquiry privileges, as the CVE requires an authenticated user to trigger the vulnerability.
-
Check for recent channel status inquiry activity or abnormal queue manager behaviorReview MQ error logs (typically in /var/mqm/log or the installation log directory) for channel status inquiry commands and any recent issues. Look for 'AMQxxxx' error messages related to channel operations.Affected if There are logged channel status inquiry operations from authenticated users, or the queue manager has experienced unexplained restarts or unavailability.
A user is affected if they are running exactly IBM WebSphere MQ version 9.0.2 AND have authenticated users with channel administration privileges who can submit channel status inquiry requests.
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 dataApply IBM's relevant patch or upgrade to a fixed version. Additionally, restrict channel administration privileges to only necessary authenticated users and monitor for abnormal channel status inquiry patterns.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1236 — 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-2017-1236 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