dbcve.org
Spss StatisticsApplication · Ibm

CVE-2015-8530

MEDIUM · 6.5 CVSS v3.0 Published 2016-05-14
Fix available
A fix is available. Upgrade to 20.0.0.2 / 21.0.0.2 or later.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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
Stack-based buffer overflow in the Initialize function in an ActiveX control in IBM SPSS Statistics 19 and 20 before 20.0.0.2-IF0008, 21 before 21.0.0.2-IF0010, 22 before 22.0.0.2-IF0011, 23 before 23.0.0.3-IF0001, and 24 before 24.0.0.0-IF0003 allows remote authenticated users to execute arbitrary code via a long argument.

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

Stack-based buffer overflow in the Initialize function of an ActiveX control in IBM SPSS Statistics allows authenticated remote users to execute arbitrary code by providing an overly long argument. This affects versions 19 through 24 before specific interim fixes were released.

MitigationApply the vendor-supplied interim fixes (IF) for each affected version: 20.0.0.2-IF0008, 21.0.0.2-IF0010, 22.0.0.2-IF0011, 23.0.0.3-IF0001, and 24.0.0.0-IF0003. If patching is not immediately feasible, consider disabling the ActiveX control or restricting authenticated access to trusted users only.

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 StatisticsApplication
Affected:>= 19.0.0.0, <= 19.0.0.2>= 20.0.0.0, < 20.0.0.2>= 21.0.0.0, < 21.0.0.2>= 22.0.0.0, < 22.0.0.2>= 23.0.0.0, < 23.0.0.3= 24.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
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

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 Statistics is installed
    Check for the presence of IBM SPSS Statistics installation directory, typically in Program Files\IBM\SPSS\Statistics\ or Program Files (x86)\IBM\SPSS\Statistics\, or look for the application in Add/Remove Programs (Programs and Features)
    Affected if The application is not installed or not present on the system
  2. Determine the installed version of IBM SPSS Statistics
    Open the installed IBM SPSS Statistics application and go to Help > About IBM SPSS Statistics, or check the version in Add/Remove Programs. The version will display as a four-part number (e.g., 20.0.0.0, 22.0.0.1)
    Affected if The version falls within the affected ranges: 19.0.0.0-19.0.0.2, 20.0.0.0-20.0.0.1, 21.0.0.0-21.0.0.1, 22.0.0.0-22.0.0.1, 23.0.0.0-23.0.0.2, or 24.0.0.0
  3. Confirm the ActiveX control is registered and available
    Look for the SPSS Statistics ActiveX control DLL (typically StatsBA or similar ActiveX component) in the installation directory, or check Windows Registry under HKLM\SOFTWARE\Classes\TypeLib for SPSS Statistics ActiveX entries
    Affected if The ActiveX control is registered and available for use in Internet Explorer or other ActiveX containers
  4. Check if interim fixes have been applied
    Within the application, go to Help > About and look for the fix pack version notation (e.g., IF0008, IF0010), or check the installation directory for fix pack documentation. Compare against the fixed versions: 20.0.0.2-IF0008, 21.0.0.2-IF0010, 22.0.0.2-IF0011, 23.0.0.3-IF0001, or 24.0.0.0-IF0003
    Affected if No interim fix is present, meaning the version remains vulnerable

The environment is affected if IBM SPSS Statistics version 19.0.0.0 through 19.0.0.2, 20.0.0.0 through 20.0.0.1, 21.0.0.0 through 21.0.0.1, 22.0.0.0 through 22.0.0.1, 23.0.0.0 through 23.0.0.2, or 24.0.0.0 is installed WITHOUT the corresponding interim fix (IF) applied, and the ActiveX control is enabled.

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.

From vendor data
Upgrade available Upgrade to 20.0.0.2 / 21.0.0.2 / 22.0.0.2 or later
Fixed in 20.0.0.221.0.0.222.0.0.2
Interim mitigation

Apply the vendor-supplied interim fixes (IF) for each affected version: 20.0.0.2-IF0008, 21.0.0.2-IF0010, 22.0.0.2-IF0011, 23.0.0.3-IF0001, and 24.0.0.0-IF0003. If patching is not immediately feasible, consider disabling the ActiveX control or restricting authenticated access to trusted users only.

Fix this in Spss Statistics Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

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