CVE-2017-1669

UnknownEPSS 1.05%

Last modified

CVE-2017-1669 is a vulnerability of currently unknown severity. 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. EPSS estimates a 1.05% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
1.05%

59.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
IbmSecurity Key Lifecycle Manager2.5.0.0
IbmSecurity Key Lifecycle Manager2.5.0.1
IbmSecurity Key Lifecycle Manager2.5.0.2
IbmSecurity Key Lifecycle Manager2.5.0.3
IbmSecurity Key Lifecycle Manager2.5.0.4
IbmSecurity Key Lifecycle Manager2.5.0.5
IbmSecurity Key Lifecycle Manager2.5.0.6
IbmSecurity Key Lifecycle Manager2.5.0.7
IbmSecurity Key Lifecycle Manager2.5.0.8
IbmSecurity Key Lifecycle Manager2.6.0
IbmSecurity Key Lifecycle Manager2.6.0.1
IbmSecurity Key Lifecycle Manager2.6.0.2
IbmSecurity Key Lifecycle Manager2.6.0.3
IbmSecurity Key Lifecycle Manager2.7.0
IbmSecurity Key Lifecycle Manager2.7.0.1
IbmSecurity Key Lifecycle Manager2.7.0.2

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-1669?
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.
How severe is CVE-2017-1669?
Severity scoring for CVE-2017-1669 is pending analysis. The EPSS model estimates a 1.05% probability of exploitation in the next 30 days.
How do I fix CVE-2017-1669?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-1669?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST