dbcve.org
Spss SamplepowerApplication · Ibm

CVE-2013-0593

HIGH · 9.3 CVSS v2.0 Published 2013-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Unspecified vulnerability in the olch2x32 ActiveX control in IBM SPSS SamplePower 3.0 before 3.0-IM-S3SAMPC-WIN32-FP001 allows remote attackers to execute arbitrary code via unknown vectors.

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 confidence

A critical vulnerability exists in the olch2x32 ActiveX control component of IBM SPSS SamplePower 3.0 (versions prior to 3.0-IM-S3SAMPC-WIN32-FP001). The vulnerability allows remote attackers to execute arbitrary code on affected systems through unspecified vectors, indicating likely memory corruption or unsafe method invocation within the ActiveX control.

MitigationApply the vendor-supplied patch (3.0-IM-S3SAMPC-WIN32-FP001 or later). As an interim control, disable the olch2x32 ActiveX control in Internet Explorer or use the Kill Bit to block instantiation. Identify and remediate all systems running vulnerable SPSS SamplePower versions.

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
Spss SamplepowerApplication
Affected:= 3.0.0.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify IBM SPSS SamplePower 3.0 is installed
    Check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\IBM\SPSSSamplePower or HKEY_CURRENT_USER\SOFTWARE\IBM\SPSSSamplePower for the product entry, or look for the program in Add/Remove Programs
    Affected if The software is present on the system
  2. Determine the installed version of SPSS SamplePower
    Read the Version value from the registry key found above, or right-click the application executable in Program Files and view Properties > Details for the File Version
    Affected if The version is 3.0.0.0 or any version earlier than 3.0-IM-S3SAMPC-WIN32-FP001
  3. Confirm the olch2x32 ActiveX control is registered
    Check the Windows registry under HKEY_CLASSES_ROOT\olch2x32 or search for CLSID {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} associated with olch2x32 in the registry. The ActiveX DLL typically resides in the SPSS SamplePower installation directory
    Affected if The ActiveX control CLSID is present in the registry, indicating the control is installed and can be instantiated by Internet Explorer
  4. Check if the ActiveX kill bit is set (mitigation present)
    Search the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units for the olch2x32 CLSID and verify if the value "Enabled" is set to 0, or check HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Ext\PreApproved for the CLSID
    Affected if The kill bit is NOT set, meaning the ActiveX control can still be loaded by Internet Explorer

A system is affected if IBM SPSS SamplePower 3.0 is installed with version 3.0.0.0 or any version prior to 3.0-IM-S3SAMPC-WIN32-FP001, and the olch2x32 ActiveX control is registered and not blocked by a kill bit.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch (3.0-IM-S3SAMPC-WIN32-FP001 or later). As an interim control, disable the olch2x32 ActiveX control in Internet Explorer or use the Kill Bit to block instantiation. Identify and remediate all systems running vulnerable SPSS SamplePower versions.

Recommended fix Moderate confidence

3.0-IM-S3SAMPC-WIN32-FP001

  1. Obtain IBM SPSS SamplePower 3.0 Fix Pack 001 (3.0-IM-S3SAMPC-WIN32-FP001) from the official IBM support website or through your IBM account
  2. Back up your existing IBM SPSS SamplePower 3.0 installation and any associated data files
  3. Close all running instances of IBM SPSS SamplePower
  4. Run the fix pack installer (3.0-IM-S3SAMPC-WIN32-FP001) with administrative privileges
  5. Follow the on-screen installation prompts to complete the update
  6. Verify the installation was successful by checking the updated version number

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spss Samplepower Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0593 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0593 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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