dbcve.org
Security Access ManagerApplication · Ibm

CVE-2016-3018

MEDIUM · 6.1 CVSS v3.0 Published 2017-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 →
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 for Web is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

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

IBM Security Access Manager for Web contains a stored cross-site scripting (XSS) vulnerability in its Web UI. Attackers can embed malicious JavaScript code that executes in the browsers of other users accessing the compromised interface, potentially hijacking trusted sessions and disclosing credentials.

MitigationImplement proper input validation and output encoding for all user-supplied data in the Web UI. Apply IBM security patches when available and consider deploying a WAF 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
Security Access ManagerApplication
Affected:= 9.0.0= 9.0.0.1= 9.0.1.0
Security Access Manager For MobileApplication
Affected:= 8.0.0.0= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.0.0.5= 8.0.1.0= 8.0.1.2= 8.0.1.3= 8.0.1.4
Security Access Manager For WebApplication
Affected:= 8.0.0.0= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.0.0.5= 8.0.1.0= 8.0.1.2= 8.0.1.3= 8.0.1.4

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 product
    Run the appropriate command to query the installed product: on Linux use 'rpm -qa | grep -i ibm' or 'ls /opt/IBM' to find the installed product directory. On Windows, check the installed programs list or registry under 'HKLM\SOFTWARE\IBM'.
    Affected if The product name matches 'Security Access Manager', 'Security Access Manager For Mobile', or 'Security Access Manager For Web'.
  2. Check the installed version
    Run the product-specific version command. For ISAM/ISAM for Web check '/opt/ibm/isd/var/VERSION' or use 'ibmsealite -version' if available. For ISAM for Mobile check the installation directory for a version file. Alternatively, examine the WAR file manifest in the Web UI deployment directory.
    Affected if The version matches exactly: 9.0.0, 9.0.0.1, or 9.0.1.0 for ISAM; any of 8.0.0.0 through 8.0.1.4 (excluding 8.0.0.4 and 8.0.1.1) for ISAM for Mobile or ISAM for Web.
  3. Confirm the Web UI is enabled
    Check the configuration file for Web UI status. Look for 'LmiPort' or 'WSIWebUIPort' in the server.xml or isamconfig.properties file located in the configuration directory (typically /opt/ibm/isd/config/). Also verify the Web UI application is deployed by checking for the administrative console WAR file.
    Affected if The Web UI port is configured and the administrative console application is deployed and accessible.
  4. Audit Web UI input fields for malicious scripts
    Log into the Web UI administrative console as an administrator. Navigate to the user management or configuration sections where user-supplied data is stored. Review all text fields for suspicious content containing <script>, javascript:, onerror=, or other XSS payload patterns. Check browser developer console for any script execution errors.
    Affected if Any user-configurable fields in the Web UI contain unsanitized script tags or event handlers that could execute in another user's browser.

The environment is affected if any IBM Security Access Manager product matching the listed versions has its Web UI enabled and accessible, regardless of whether exploitation has occurred.

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

Implement proper input validation and output encoding for all user-supplied data in the Web UI. Apply IBM security patches when available and consider deploying a WAF as a compensating control.

Fix this in Security Access Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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