CVE-2012-0190
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 the Render method in the ExportHTML.ocx ActiveX control in ExportHTML.dll in IBM SPSS Dimensions 5.5 and SPSS Data Collection 5.6, 6.0, and 6.0.1 allows remote attackers to execute arbitrary code via a crafted HTML document.
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 confidenceVulnerability in the Render method of ExportHTML.ocx ActiveX control in IBM SPSS Dimensions 5.5 and SPSS Data Collection 5.6/6.0/6.0.1 allows remote arbitrary code execution via crafted HTML documents. The unspecified flaw in the Render method can be triggered when a user visits a malicious webpage, leading to complete system compromise.
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.6= 6.0= 6.0.1= 5.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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/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.
-
Locate ExportHTML.ocx on the systemSearch for ExportHTML.ocx in typical installation directories: C:\Program Files\IBM\SPSS Dimensions\5.5\, C:\Program Files\IBM\SPSS Data Collection\5.6\, C:\Program Files\IBM\SPSS Data Collection\6.0\, or C:\Program Files\IBM\SPSS Data Collection\6.0.1\. Also check C:\Windows\System32\ for any registered copies.Affected if ExportHTML.ocx file is found on the system
-
Check SPSS Data Collection versionOpen Add or Remove Programs (appwiz.cpl) or check the program files directory for IBM SPSS Data Collection and note the exact version number installed.Affected if Version installed equals 5.6, 6.0, or 6.0.1
-
Check SPSS Dimensions versionOpen Add or Remove Programs (appwiz.cpl) or check the program files directory for IBM SPSS Dimensions and note the exact version number installed.Affected if Version installed equals 5.5
-
Verify ActiveX control registrationOpen Windows Registry and search for ExportHTML.ocx under HKEY_CLASSES_ROOT\CLSID or run regsvr32 /s ExportHTML.ocx to check if it is registered. Also check Internet Explorer Add-ons for ExportHTML ActiveX control.Affected if The ExportHTML.ocx ActiveX control is registered and enabled in Internet Explorer
A system is affected if IBM SPSS Data Collection 5.6/6.0/6.0.1 or IBM SPSS Dimensions 5.5 is installed AND the ExportHTML.ocx ActiveX control is present and registered on the system.
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 dataDisable the ExportHTML.ocx ActiveX control via Internet Explorer security settings or remove the affected ExportHTML.dll component. Consider using the Kill Bit for the CLSID or deploying virtualization/sandboxing for legacy systems. Upgrade to supported SPSS versions if available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0190 — 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-0190 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