CWE
79
Advisory Published
Updated

CVE-2017-1673: XSS

First published: Wed Jan 03 2018(Updated: )

IBM Tivoli Key Lifecycle Manager 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.

Credit: psirt@us.ibm.com

Affected SoftwareAffected VersionHow to fix
IBM Security Guardium Key Lifecycle Manager=2.5.0
IBM Security Guardium Key Lifecycle Manager=2.5.0.0
IBM Security Guardium Key Lifecycle Manager=2.5.0.1
IBM Security Guardium Key Lifecycle Manager=2.5.0.2
IBM Security Guardium Key Lifecycle Manager=2.5.0.3
IBM Security Guardium Key Lifecycle Manager=2.5.0.4
IBM Security Guardium Key Lifecycle Manager=2.5.0.5
IBM Security Guardium Key Lifecycle Manager=2.5.0.6
IBM Security Guardium Key Lifecycle Manager=2.5.0.7
IBM Security Guardium Key Lifecycle Manager=2.5.0.8
IBM Security Guardium Key Lifecycle Manager=2.6.0
IBM Security Guardium Key Lifecycle Manager=2.6.0.1
IBM Security Guardium Key Lifecycle Manager=2.6.0.2
IBM Security Guardium Key Lifecycle Manager=2.6.0.3
IBM Security Guardium Key Lifecycle Manager=2.7.0
IBM Security Guardium Key Lifecycle Manager=2.7.0.1
IBM Security Guardium Key Lifecycle Manager=2.7.0.2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the severity of CVE-2017-1673?

    The severity of CVE-2017-1673 is classified as medium due to the potential for cross-site scripting leading to credential disclosure.

  • How do I fix CVE-2017-1673?

    To fix CVE-2017-1673, apply the latest patches and updates provided by IBM for affected versions of Tivoli Key Lifecycle Manager.

  • Which versions of IBM Tivoli Key Lifecycle Manager are affected by CVE-2017-1673?

    CVE-2017-1673 affects versions 2.5.0 through 2.7.0 of IBM Tivoli Key Lifecycle Manager.

  • What impact can CVE-2017-1673 have on my system?

    CVE-2017-1673 can allow unauthorized users to inject malicious JavaScript into the Web UI, potentially compromising user credentials in a trusted session.

  • Is there a workaround for CVE-2017-1673 if I cannot apply the fix immediately?

    A potential workaround for CVE-2017-1673 is to limit user input in the Web UI to prevent the execution of arbitrary JavaScript.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203