CVE-2008-1130
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 · uneditedUnspecified vulnerability in IBM WebSphere MQ 6.0.x before 6.0.2.2 and 5.3 before Fix Pack 14 allows attackers to bypass access restrictions for a queue manager via a SVRCONN (MQ client) 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 · moderate confidenceIBM WebSphere MQ versions 6.0.x before 6.0.2.2 and 5.3 before Fix Pack 14 contain an unspecified vulnerability allowing attackers to bypass access restrictions for a queue manager through SVRCONN (MQ client) channels. This is an access control bypass affecting the client-server connection mechanism in WebSphere MQ.
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= 5.3= 6CVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- None
AV:L/AC:L/Au:N/C:C/I:C/A:N
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.
-
Identify installed WebSphere MQ versionRun 'dspmqver' command on the server or check the installation directory for version files. On Windows, check Add/Remove Programs for IBM WebSphere MQ version. On Linux/Unix, check /opt/mqm or /usr/mqm directories for version information.Affected if Version is 5.3 or 6.0.x without the respective fix packs applied
-
Determine installed fix pack levelRun 'dspmqver -a' to show detailed version and fix pack information, or check the installation for files named like '6.0.2.2' or '5.3.0.14' indicating the fix pack level.Affected if Fix pack is earlier than 6.0.2.2 for version 6.0.x, or earlier than 14 for version 5.3
-
Review SVRCONN channel configurationsUse the MQSC command 'DISPLAY CHANNEL(SVRCONN)' via runmqsc to list all SVRCONN channels configured on the queue manager. Check the CHLDEFMSG and MCAUSER attributes.Affected if SVRCONN channels exist and the system is running an affected version without the security fix
-
Verify MCAUSER setting on SVRCONN channelsRun 'DISPLAY CHANNEL(*) CHLNAME MCAUSER' in runmqsc to see which SVRCONN channels have explicit user mappings set. Default MCAUSER of blank or 'mqm' on an affected version indicates potential exposure.Affected if SVRCONN channels are configured without proper MCAUSER restrictions on a vulnerable version
A system is affected if it runs WebSphere MQ version 5.3 before Fix Pack 14 or version 6.0.x before 6.0.2.2 and has SVRCONN channels configured.
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 Fix Pack 6.0.2.2 or later for version 6.0.x, or Fix Pack 14 or later for version 5.3. Review SVRCONN channel configurations and implement least-privilege access controls pending the patch.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-1130 — 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-2008-1130 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