dbcve.org
Spss SamplepowerApplication · Ibm

CVE-2013-6724

HIGH · 9.3 CVSS v2.0 Published 2014-02-01
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 vsflex8l ActiveX control in IBM SPSS SamplePower 3.0.1 before FP1 IF1 allows remote attackers to execute arbitrary code via a crafted ComboList property value.

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 confidence

A critical vulnerability exists in the vsflex8l ActiveX control used by IBM SPSS SamplePower 3.0.1 (before FP1 IF1). Attackers can achieve remote code execution by providing a specially crafted value to the ComboList property, likely triggering a buffer overflow or similar memory corruption in the ActiveX control.

MitigationApply vendor patch FP1 IF1 or later to IBM SPSS SamplePower to update the vulnerable vsflex8l ActiveX control, or disable the ActiveX control in Internet Explorer as a compensating control.

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.1.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. Confirm IBM SPSS SamplePower installation
    Look for the program in the Windows Add/Remove Programs list, or check typical installation directories like C:\Program Files\IBM\SPSS SamplePower or C:\Program Files (x86)\IBM\SPSS SamplePower
    Affected if IBM SPSS SamplePower is installed on the system
  2. Determine installed version of IBM SPSS SamplePower
    Check the program version via Help > About in the application, or look for version information in the program's executable properties (right-click SamplePower.exe > Properties > Details)
    Affected if The installed version is 3.0.1.0 and does not have FP1 IF1 patch applied
  3. Check if the vsflex8l ActiveX control is registered
    Open Windows Registry Editor and search for the CLSID {C0A80C04-7C44-11D2-97C5-0050E5626C91} (vsflex8l control) under HKEY_CLASSES_ROOT\CLSID, or use regsvr32 to query the control if found in the system
    Affected if The vsflex8l ActiveX control is registered on the system and matches the vulnerable version
  4. Verify patch level (FP1 IF1)
    Check IBM fix pack documentation or the application's About dialog for patch level indication; look for references to FP1 IF1 in installed files or IBM support documentation
    Affected if No FP1 IF1 patch is applied to the 3.0.1.0 installation

The system is affected if IBM SPSS SamplePower version 3.0.1.0 is installed without the FP1 IF1 patch and the vsflex8l ActiveX control is present on the system.

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 vendor patch FP1 IF1 or later to IBM SPSS SamplePower to update the vulnerable vsflex8l ActiveX control, or disable the ActiveX control in Internet Explorer as a compensating control.

Recommended fix Moderate confidence

IBM SPSS SamplePower 3.0.1 FP1 IF1 (Fix Pack 1 Interim Fix 1)

  1. Identify the current installed version of IBM SPSS SamplePower 3.0.1
  2. Contact IBM support or visit the official IBM support portal to obtain Fix Pack 1 Interim Fix 1 (FP1 IF1) for SPSS SamplePower 3.0.1
  3. Apply FP1 IF1 to the affected installation following IBM's standard patch installation procedures
  4. Verify the installed version reflects FP1 IF1 or later after applying the fix

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

Fix this in Spss Samplepower Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-6724 — 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-6724 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