CVE-2011-0310
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 · uneditedBuffer overflow in IBM WebSphere MQ 7.0 before 7.0.1.4 allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via a crafted header field in a message.
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 confidenceBuffer overflow vulnerability in IBM WebSphere MQ 7.0 (versions before 7.0.1.4) allows remote attackers to execute arbitrary code or cause a denial of service by sending specially crafted header fields in MQ messages. The vulnerability stems from insufficient bounds checking when processing message headers.
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= 7.0= 7.0.0.1= 7.0.0.2= 7.0.1.0= 7.0.1.1= 7.0.1.2= 7.0.1.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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/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 the command 'dspmqver' on the MQ server or check the installation directory for version information. On Windows, check 'Program Files\IBM\WebSphere MQ\bin\amqiclen.txt' or similar version files.Affected if The installed version is 7.0, 7.0.0.1, 7.0.0.2, 7.0.1.0, 7.0.1.1, 7.0.1.2, or 7.0.1.3 (any version before 7.0.1.4).
-
Verify if Queue Manager is runningRun 'dspmq' or 'runmqsc -q' to list running queue managers. Use 'endmqm -i <qm_name>' to stop if needed.Affected if A Queue Manager is active and processing messages, as the vulnerability triggers when specially crafted header fields in MQ messages are processed.
-
Check MQ listener status and network exposureRun 'runmqsc <qm_name>' then enter 'DISPLAY LISTENER(*)' to see configured listeners. Check if listeners are bound to external network interfaces (0.0.0.0 or public IP) rather than localhost (127.0.0.1).Affected if An external listener is active on a public or accessible network interface, allowing remote attackers to send malicious messages.
-
Inspect MQ service configurationCheck the MQ service configuration file (mq.ini or queue manager ini file) for listener definitions and port bindings. On Unix, check /var/mqm/mq.ini; on Windows, check the registry or installation directory.Affected if The configuration shows listeners accepting connections on accessible network ports without network-level restrictions.
You are affected if IBM WebSphere MQ version 7.0.x (before 7.0.1.4) is installed AND a Queue Manager with an exposed listener is running to process incoming MQ messages.
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 dataUpgrade IBM WebSphere MQ to version 7.0.1.4 or later to obtain the security patch. If immediate upgrade is not feasible, restrict network access to MQ listeners and implement input validation on message ingress points.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0310 — 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-0310 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