CVE-2012-2199
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 · uneditedThe server message channel agent in the queue manager in the server in IBM WebSphere MQ 7.0.1 before 7.0.1.9, 7.1, and 7.5 on Solaris allows remote attackers to cause a denial of service (invalid address alignment exception and daemon crash) via vectors involving a multiplexed channel.
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 confidenceDenial of service vulnerability in IBM WebSphere MQ server message channel agent on Solaris. Remote attackers can trigger an invalid address alignment exception via malformed requests on multiplexed channels, causing the MQ daemon to 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= 7.0.1.0= 7.0.1.1= 7.0.1.2= 7.0.1.3= 7.0.1.4= 7.0.1.5= 7.0.1.6= 7.0.1.7= 7.0.1.8= 7.1= 7.5CVSS 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
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Verify the operating system is SolarisRun 'uname -a' or 'cat /etc/release' to confirm the OS. This vulnerability only affects IBM WebSphere MQ on Solaris, not on other platforms.Affected if The system is running Solaris and the MQ version falls within the affected range.
-
Determine the installed IBM WebSphere MQ versionRun the command 'dspmqver' as the mqm user, or check the version directory under /opt/mqm. Alternatively, use 'runmqsc' and query the queue manager for version information.Affected if The installed version is 7.0.1.0 through 7.0.1.8, 7.1, or 7.5.
-
Identify if multiplexed channels are configuredUse 'runmqsc' to connect to the queue manager and run 'DISPLAY CHANNEL(*)' to list all channel definitions. Look for channels with 'MCATYPE(MULTIPLEX)' or check channel configuration files for multiplexed channel definitions.Affected if Multiplexed channels are defined and active on the queue manager.
-
Check if channel listeners are exposed to networkReview the queue manager's listener configuration using 'DISPLAY LISTENER(*) ALL' in runmqsc. Verify network exposure by checking firewall rules or TCP wrapper settings that allow external access to channel ports (default 1414).Affected if Channel listeners are reachable from untrusted networks, increasing exposure to remote exploit attempts.
A system is affected if it is running IBM WebSphere MQ version 7.0.1.0-7.0.1.8, 7.1, or 7.5 on Solaris with multiplexed channels enabled and network-accessible channel 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 dataApply IBM WebSphere MQ patches (7.0.1.9+, 7.1.x fix, or 7.5.x fix) per IBM's official fix guidance. If immediate patching is not possible, restrict network access to the queue manager's channel listeners.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2199 — 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-2012-2199 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