dbcve.org
Tivoli Access Manager For E BusinessApplication · Ibm

CVE-2017-1489

MEDIUM · 6.1 CVSS v3.0 Published 2017-08-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Security Access Manager 6.1, 7.0, 8.0, and 9.0 e-community configurations may be affected by a redirect vulnerability. ECSSO Master Authentication can redirect to a server not participating in an e-community domain. IBM X-Force ID: 128687.

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

IBM Security Access Manager versions 6.1 through 9.0 contain an open redirect vulnerability in the ECSSO (Enterprise Custom SSO) Master Authentication component. When e-community configurations are in use, the authentication system can be coerced into redirecting users to servers that are not part of the trusted e-community domain. This allows attackers to craft malicious links that appear to come from the legitimate authentication portal but redirect to external malicious sites.

MitigationApply the vendor patch or upgrade to a supported version of IBM Security Access Manager. Additionally, review and restrict e-community domain configuration to explicitly whitelist only trusted participating servers for redirect destinations.

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
Tivoli Access Manager For E BusinessApplication
Affected:= 6.1.0= 6.1.0.1= 6.1.0.2= 6.1.0.3= 6.1.0.4= 6.1.0.5= 6.1.0.6= 6.1.0.7= 6.1.0.8= 6.1.0.9= 6.1.0.10= 6.1.0.11
Security Access Manager For Web SoftwareApplication
Affected:= 7.0= 7.0.0.1= 7.0.0.2= 7.0.0.3= 7.0.0.4= 7.0.0.5= 7.0.0.6= 7.0.0.7= 7.0.0.8= 7.0.0.9= 7.0.0.10= 7.0.0.11
Security Access Manager For Web ApplianceApplication
Affected:= 7.0= 7.0.0.1= 7.0.0.2= 7.0.0.3= 7.0.0.4= 7.0.0.5= 7.0.0.6= 7.0.0.7= 7.0.0.8= 7.0.0.9= 7.0.0.10= 7.0.0.11
Security Access Manager For WebApplication
Affected:= 8.0= 8.0.0.0= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.0.0.4= 8.0.0.5= 8.0.0.22= 8.0.0.31= 8.0.1.0= 8.0.1.1= 8.0.1.2
Security Access Manager For MobileApplication
Affected:= 8.0= 8.0.0.0= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.0.0.4= 8.0.0.5= 8.0.0.22= 8.0.0.31= 8.0.1.0= 8.0.1.1= 8.0.1.2
Security Access ManagerApplication
Affected:= 9.0.0.0= 9.0.0.1= 9.0.1.0= 9.0.2.0= 9.0.2.1= 9.0.3.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Identify the installed IBM Security Access Manager version
    Locate the version of IBM Security Access Manager (or Tivoli Access Manager for E Business) installed in your environment. This is typically visible in the product's admin console, about section, or via command line tools such as 'iamutil -version' or 'pdadmin -version' depending on the component.
    Affected if The installed version matches one of the affected versions: 6.1.0 through 6.1.0.11, 7.0.0.0 through 7.0.0.11, 8.0.0.0 through 8.0.0.5, 8.0.0.22, 8.0.0.31, 8.0.1.0 through 8.0.1.2, 9.0.0.0 through 9.0.3.0.
  2. Confirm ECSSO (Enterprise Custom SSO) Master Authentication is enabled
    Check whether the Enterprise Custom SSO (ECSSO) Master Authentication component is configured and active. This is typically managed through the IBM Security Access Manager administration console under authentication settings or SSO configuration panels.
    Affected if ECSSO Master Authentication is enabled and in use for authentication flows.
  3. Check for e-community configuration in use
    Review the ECSSO configuration for e-community settings. Look for e-community domain definitions or e-community server lists in the authentication configuration. This is often found in the ECSSO master authentication settings or e-community management section of the admin console.
    Affected if E-community configurations are defined and the e-community includes servers outside your trusted network or contains wildcard or overly permissive domain entries.

You are affected if your IBM Security Access Manager version is one of the listed affected versions AND ECSSO Master Authentication is enabled with e-community configurations in use.

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

Apply the vendor patch or upgrade to a supported version of IBM Security Access Manager. Additionally, review and restrict e-community domain configuration to explicitly whitelist only trusted participating servers for redirect destinations.

Fix this in Tivoli Access Manager For E Business Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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