CVE-2017-1673
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 · uneditedIBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 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. IBM X-Force ID: 133640.
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 confidenceIBM Tivoli Key Lifecycle Manager versions 2.5, 2.6, and 2.7 contains a stored XSS vulnerability in the Web UI that allows authenticated users to inject arbitrary JavaScript code. This JavaScript executes in the context of other users' sessions, potentially enabling session hijacking and credential theft within trusted sessions.
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= 2.5.0= 2.5.0.0= 2.5.0.1= 2.5.0.2= 2.5.0.3= 2.5.0.4= 2.5.0.5= 2.5.0.6= 2.5.0.7= 2.5.0.8= 2.6.0= 2.6.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of IBM Security Key Lifecycle ManagerCheck the product version by inspecting the installation directory or running 'version' command if available in the installation path. Common locations include /opt/ibm/tklm or C:\Program Files\IBM\Tivoli Key Lifecycle Manager. Look for a version file or check the about page of the Web UI if accessible.Affected if The installed version matches 2.5.0.x, 2.6.0, 2.6.0.1, or 2.7 (these versions are within the affected range).
-
Confirm Web UI component is enabled and accessibleVerify that the Web UI interface is deployed and accessible. This may involve checking if the web application server (typically embedded or external) is running and the TKLM web interface port is listening (default often 443 or 8443).Affected if The Web UI is enabled and reachable, making the stored XSS attack surface available to authenticated users.
-
Verify authentication is configured for the Web UIConfirm that user authentication is active for the Web UI. Check the security configuration settings within the TKLM administration console or configuration files to ensure the login mechanism is enabled.Affected if User authentication is configured, which is required for the stored XSS to be exploitable since the vulnerability allows authenticated users to inject malicious scripts.
You are affected if IBM Security Key Lifecycle Manager version 2.5.0.x, 2.6.0, 2.6.0.1, or 2.7 is installed AND the Web UI is enabled with authentication configured.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-provided patches for this vulnerability. Additionally, implement robust input validation and output encoding for all user-supplied data in the Web UI, and configure Content Security Policy headers to mitigate XSS risks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1673 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-1673 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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