medium
4.3
CWE
200
Advisory Published
Updated

CVE-2017-1669: Infoleak

First published: Thu Jan 04 2018(Updated: )

IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referrer header or browser history. IBM X-Force ID: 133636.

Credit: psirt@us.ibm.com

Affected SoftwareAffected VersionHow to fix
IBM Security Key Lifecycle Manager=2.5.0.0
IBM Security Key Lifecycle Manager=2.5.0.1
IBM Security Key Lifecycle Manager=2.5.0.2
IBM Security Key Lifecycle Manager=2.5.0.3
IBM Security Key Lifecycle Manager=2.5.0.4
IBM Security Key Lifecycle Manager=2.5.0.5
IBM Security Key Lifecycle Manager=2.5.0.6
IBM Security Key Lifecycle Manager=2.5.0.7
IBM Security Key Lifecycle Manager=2.5.0.8
IBM Security Key Lifecycle Manager=2.6.0
IBM Security Key Lifecycle Manager=2.6.0.1
IBM Security Key Lifecycle Manager=2.6.0.2
IBM Security Key Lifecycle Manager=2.6.0.3
IBM Security Key Lifecycle Manager=2.7.0
IBM Security Key Lifecycle Manager=2.7.0.1
IBM Security 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.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

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

    CVE-2017-1669 is classified as a medium severity vulnerability due to potential information disclosure.

  • How do I fix CVE-2017-1669?

    To fix CVE-2017-1669, ensure you configure your IBM Tivoli Key Lifecycle Manager to avoid exposing sensitive information through URL parameters.

  • What are the affected versions of IBM Tivoli Key Lifecycle Manager for CVE-2017-1669?

    The affected versions for CVE-2017-1669 are IBM Tivoli Key Lifecycle Manager versions 2.5 to 2.7.

  • What type of data is at risk in CVE-2017-1669?

    CVE-2017-1669 risks sensitive information exposure stored in URL parameters.

  • Can exploitation of CVE-2017-1669 be mitigated?

    Mitigation of CVE-2017-1669 can be achieved by ensuring proper access controls and sanitizing URL parameters.

Company

Resources

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