CVE-2012-2328
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 · uneditedinternal/cimxml/sax/NodeFactory.java in Standards-Based Linux Instrumentation for Manageability (SBLIM) Common Information Model (CIM) Client (aka sblim-cim-client2) before 2.1.12 computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via a crafted XML file.
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 confidenceThe NodeFactory.java component in sblim-cim-client2 versions before 2.1.12 uses a hash function without randomization or collision resistance, allowing attackers to craft XML files with predictable hash collisions that cause excessive CPU consumption during parsing.
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<= 2.1.11= 11.4= 12.1= 12.2CVSS 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 sblim-cim-client2 is installedSearch for the sblim-cim-client2 JAR file or package in the system. Common locations include /usr/share/java/, /opt/, or within application lib directories. Use commands like: find / -name '*sblim-cim-client*.jar' 2>/dev/null or check your package manager (rpm -qa | grep sblim-cim-client2 or dpkg -l | grep sblim-cim-client2)Affected if The library or package is found on the system
-
Determine the installed versionIf using the JAR file, examine the manifest file within the JAR (jar tf sblim-cim-client2.jar | grep MANIFEST.MF, then extract and read it) or check the package version via rpm -qi or dpkg -s. Compare the version number to 2.1.12Affected if The installed version is 2.1.11 or earlier, or the version cannot be determined and is suspected to be older
-
Identify applications using this librarySearch application configurations or dependencies that reference sblim-cim-client2. Check WAR files, EAR files, or application scripts that may include this library in their classpath. Look for CIM client usage in Java applicationsAffected if Applications or services depend on and load this library for CIM operations
-
Assess XML input exposureDetermine whether any application using sblim-cim-client2 processes XML from untrusted network sources, external users, or non-authenticated connections. Review the application's network listeners and input validation mechanismsAffected if The library is used to parse XML from untrusted or network-accessible sources without additional safeguards
A system is affected if sblim-cim-client2 version 2.1.11 or earlier is installed and any application using it parses XML from untrusted sources, enabling hash collision attacks that can cause CPU exhaustion.
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 sblim-cim-client2 to version 2.1.12 or later which implements hash randomization; alternatively, restrict XML input sources to trusted parties.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2328 — 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-2328 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