CVE-2011-0314
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 · uneditedHeap-based buffer overflow in IBM WebSphere MQ 6.0 before 6.0.2.11 and 7.0 before 7.0.1.5 allows remote authenticated users to execute arbitrary code or cause a denial of service (queue manager crash) by inserting an invalid message into the queue.
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 confidenceHeap-based buffer overflow in IBM WebSphere MQ versions 6.0 before 6.0.2.11 and 7.0 before 7.0.1.5 allows remote authenticated users to inject invalid messages into a queue, triggering overflow that can lead to arbitrary code execution or queue manager crash.
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= 6.0= 6.0.1.0= 6.0.1.1= 6.0.2.0= 6.0.2.1= 6.0.2.2= 6.0.2.3= 6.0.2.4= 6.0.2.5= 6.0.2.6= 6.0.2.7= 6.0.2.8CVSS 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
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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 installed IBM WebSphere MQ versionRun 'dspmqver' on UNIX/Linux or check Program Files\IBM\WebSphere MQ on Windows to retrieve the version number and build level of the installationAffected if The installed version is 6.0.x (any patch level) or falls within 6.0.1.0 through 6.0.2.8, or is 7.0.x before 7.0.1.5
-
Identify active queue managersRun 'dspmq -m ALL' or 'runmqsc -q' to list all queue managers currently running on the systemAffected if Any queue manager is running a vulnerable version of WebSphere MQ as identified in step 1
-
Verify if remote queue access is enabledCheck the queue manager's channel configuration using 'DISPLAY CHANNEL(*) CHLTYPE(CLNTCONN)' in runmqsc, or examine the listener configuration for TCP/IP ports (default 1414) that accept remote connectionsAffected if Remote listeners are active and accepting client connections, as the flaw is exploitable by remote authenticated users
-
Review user permissions on queuesUse 'DISPLAY Q('queue_name')' in runmqsc to view queue permissions, and check for any non-trusted or unverified user authorities with put or get access to queuesAffected if Queues grant put or get permissions to users who are not explicitly trusted, which would allow the attack vector to succeed
You are affected if a queue manager is running WebSphere MQ version 6.0 through 6.0.2.8 or 7.0 before 7.0.1.5, and that queue manager accepts remote authenticated connections or has queues accessible to untrusted users.
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 WebSphere MQ patches 6.0.2.11 or 7.0.1.5 and later. If immediate patching is not feasible, restrict queue access to only trusted authenticated users and monitor for anomalous queue activity.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0314 — 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-2011-0314 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