dbcve.org
Spss Analytical Decision ManagementApplication · Ibm

CVE-2013-5369

HIGH · 9.3 CVSS v2.0 Published 2013-09-16
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
IBM SPSS Analytical Decision Management 6.1 before IF1, 6.2 before IF1, and 7.0 before FP1 IF6 might allow remote attackers to execute arbitrary code by deploying and accessing a service.

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

The vulnerability allows remote attackers to execute arbitrary code by deploying and accessing a service within IBM SPSS Analytical Decision Management. The issue appears to stem from insufficient validation or controls on the service deployment mechanism, potentially enabling injection of malicious code. This is a critical RCE vulnerability affecting multiple version branches (6.1, 6.2, 7.0) before their respective interim fix releases.

MitigationApply the vendor-supplied interim fixes (IF1 for versions 6.1 and 6.2, FP1 IF6 for version 7.0) to address the vulnerability. Until patches are applied, restrict network access to the SPSS Analytical Decision Management service and monitor for unauthorized service deployments.

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 Analytical Decision ManagementApplication
Affected:= 6.1.0.0= 6.2.0.0= 7.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. Confirm IBM SPSS Analytical Decision Management installation
    Look for the application in your system by checking for the installation directory (commonly under Program Files/IBM), or query running processes for 'SPSS' or 'ADM' related executables, or check installed programs list
    Affected if The software is present on the system
  2. Identify installed version
    Check the product version through the application's About dialog, installation logs, or version information in the installation directory. Compare your version against the affected ranges: 6.1.0.0, 6.2.0.0, and 7.0.0.0 before their respective interim fixes
    Affected if Your installed version matches 6.1.0.0, 6.2.0.0, or 7.0.0.0 without the IF1 (for 6.1/6.2) or FP1 IF6 (for 7.0) interim fixes applied
  3. Assess service deployment interface exposure
    Determine if the web-based service deployment interface is accessible by checking whether the application ports (typically 8080 or 8443 for web UI) are listening and exposed to network. Review firewall and access control configurations
    Affected if The service deployment interface is accessible from the network without proper authentication controls
  4. Audit for unauthorized service deployments
    Review the application configuration or deployment logs for any unexpected or recently created services, particularly any services that were not explicitly deployed by your administrators. Check the deployed services directory or configuration store
    Affected if Unexpected services exist in the application that were not intentionally deployed by authorized administrators
  5. Verify interim fix status
    Check whether the interim fixes (IF1 for versions 6.1/6.2, FP1 IF6 for version 7.0) have been applied by reviewing the application's fix pack level or patch history
    Affected if The interim fixes have NOT been applied to your installation

You are affected if IBM SPSS Analytical Decision Management versions 6.1.0.0, 6.2.0.0, or 7.0.0.0 are installed without the respective interim fixes applied and the service deployment interface is network-accessible.

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 interim fixes (IF1 for versions 6.1 and 6.2, FP1 IF6 for version 7.0) to address the vulnerability. Until patches are applied, restrict network access to the SPSS Analytical Decision Management service and monitor for unauthorized service deployments.

Recommended fix Moderate confidence

Apply the appropriate IBM interim fix (IF1 for 6.1.x and 6.2.x; FP1 IF6 for 7.0.x)

  1. 1. Identify the exact installed version of IBM SPSS Analytical Decision Management (6.1.x, 6.2.x, or 7.0.x)
  2. 2. For version 6.1.x: Apply Interim Fix 1 (IF1) to remediate the vulnerability
  3. 3. For version 6.2.x: Apply Interim Fix 1 (IF1) to remediate the vulnerability
  4. 4. For version 7.0.x: Apply Fix Pack 1 Interim Fix 6 (FP1 IF6) to remediate the vulnerability
  5. 5. Obtain the appropriate interim fix from IBM Fix Central (https://www.ibm.com/support/fixcentral) using the product name and version
  6. 6. Follow IBM's standard interim fix installation procedure for SPSS Analytical Decision Management
  7. 7. After applying the fix, verify the installation and test that the service functions correctly
  8. 8. Restart any affected services as required by the fix installation
Caveat Standard IBM interim fix application; review fix readme for any specific requirements or service restarts

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

Fix this in Spss Analytical Decision Management Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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