Security Appscan SourceApplication · Ibm

CVE-2012-2159

MEDIUM · 5.8 CVSS v2.0 Published 2012-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
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
Open redirect vulnerability in IBM Eclipse Help System (IEHS), as used in IBM Security AppScan Source 7.x and 8.x before 8.6 and IBM SPSS Data Collection Developer Library 6.0 and 6.0.1, allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified 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

Open redirect vulnerability in IBM Eclipse Help System (IEHS) allows remote attackers to redirect users to arbitrary external websites via unspecified vectors, facilitating phishing attacks. The vulnerability affects IBM Security AppScan Source versions 7.x and 8.x before 8.6, and IBM SPSS Data Collection Developer Library versions 6.0 and 6.0.1.

MitigationUpdate IBM Security AppScan Source to version 8.6 or later, and IBM SPSS Data Collection Developer Library to patched versions that address the open redirect in the Eclipse Help System component.

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
Security Appscan SourceApplication
Affected:= 7.0= 8.0= 8.0.0.1= 8.0.0.2= 8.5= 8.5.0.1
Spss Data CollectionApplication
Affected:= 6.0= 6.0.1

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
Partial
Integrity
Partial
Availability
None

AV:N/AC:M/Au:N/C:P/I:P/A:N

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. Check IBM Security AppScan Source version
    Locate the IBM Security AppScan Source installation directory and check the version information, typically found in an about or version file within the installation folder, or check the program properties in the Windows registry under the IBM AppScan entry
    Affected if The installed version is 7.0, 8.0, 8.0.0.1, 8.0.0.2, 8.5, or 8.5.0.1
  2. Check IBM SPSS Data Collection Developer Library version
    Locate the IBM SPSS Data Collection installation and check the version of the Developer Library component, typically found in the product documentation or the installation manifest
    Affected if The installed version is 6.0 or 6.0.1
  3. Identify if Eclipse Help System component is present
    Search for the IBM Eclipse Help System (IEHS) files in the installation directory, typically found under a help or IEHS subdirectory within the product installation folder
    Affected if The IEHS component files exist in the product installation directory
  4. Determine if help system is web-accessible
    Check if the help system is configured to run as a web service or is accessible via HTTP/HTTPS, which would expose the open redirect vector
    Affected if The help system web interface is accessible to users or external attackers

You are affected if you have IBM Security AppScan Source versions 7.x through 8.5.0.1 or IBM SPSS Data Collection Developer Library versions 6.0-6.0.1 installed with the Eclipse Help System component present and 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update IBM Security AppScan Source to version 8.6 or later, and IBM SPSS Data Collection Developer Library to patched versions that address the open redirect in the Eclipse Help System component.

Fix this in Security Appscan Source 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-2012-2159 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-2159 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