CVE-2012-3317
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 Message Broker 6.1 before 6.1.0.11, 7.0 before 7.0.0.5, and 8.0 before 8.0.0.2 has incorrect ownership of certain uninstaller Java Runtime Environment (JRE) files, which might allow local users to gain privileges by leveraging access to uid 501 or gid 300.
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 confidenceThis is a local privilege escalation vulnerability in IBM WebSphere Message Broker where uninstaller JRE files have incorrect ownership (uid 501 or gid 300), allowing local users with those identifiers to potentially gain elevated privileges.
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.1= 6.1.0.1= 6.1.0.2= 6.1.0.3= 6.1.0.4= 6.1.0.5= 6.1.0.6= 6.1.0.7= 6.1.0.8= 6.1.0.9= 6.1.0.10= 7.0.CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:N/C:C/I:C/A:C
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 WebSphere Message Broker installation and versionLocate the WebSphere Message Broker installation directory and check the version. Common locations include /opt/ibm/mqsi or /opt/IBM/WebSphereMB. Look for version files or check the product name in the installation directory.Affected if Version is 6.1 (any 6.1.0.x), 7.0, or if the exact version cannot be determined but the product is installed
-
Locate uninstaller JRE filesFind the uninstaller directory within the WebSphere Message Broker installation. On IBM WebSphere products, uninstallers are typically in a subdirectory like 'uninstall' or 'uninstallers' within the main installation directory. Look for JRE files associated with the uninstaller.Affected if Uninstaller JRE files exist in the installation directory
-
Check ownership of uninstaller JRE filesUse the 'ls -la' or 'stat' command on the uninstaller JRE files to inspect their ownership. Specifically look for uid 501 or gid 300 in the ownership fields.Affected if The uninstaller JRE files are owned by uid 501 or gid 300, indicating incorrect permissions that could allow a local user with that UID/GID to modify or execute them for privilege escalation
A system is affected if WebSphere Message Broker version 6.1.x or 7.0.x is installed AND the uninstaller JRE files have uid 501 or gid 300 ownership, allowing local users with those identifiers potential privilege escalation.
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 vendor patches: upgrade to WebSphere Message Broker 6.1.0.11, 7.0.0.5, or 8.0.0.2 or later to correct the file ownership permissions.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3317 — 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-3317 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