CVE-2016-5918: Infoleak

Published Feb 8, 2017
·
Updated

IBM Tivoli Storage Manager HSM for Windows displays the encrypted Tivoli Storage Manager password in application trace output if the password access option is prompt and the password is changed.

Affected Software

14 affected components
IBM Tivoli Storage Manager for Space Management<=7.1.4.1
IBM Tivoli Storage Manager for Space Management=7.1.0.0
Microsoft Windows
IBM Tivoli Storage Manager for Space Management<=6.4.3.0
IBM Tivoli Storage Manager for Space Management=6.4.0.0
IBM Tivoli Storage Manager for Space Management<=6.3
All of the following
Any of the following
IBM Tivoli Storage Manager for Space Management<=7.1.4.1
IBM Tivoli Storage Manager for Space Management=7.1.0.0
Microsoft Windows
All of the following
Any of the following
IBM Tivoli Storage Manager for Space Management<=6.4.3.0
IBM Tivoli Storage Manager for Space Management=6.4.0.0
Microsoft Windows
All of the following
IBM Tivoli Storage Manager for Space Management<=6.3
Microsoft Windows

Event History

Feb 8, 2017
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
DescriptionWeakness
Data Sourced
via NVD·10:59 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2016-5918?

CVE-2016-5918 is rated as a medium severity vulnerability.

2

How do I fix CVE-2016-5918?

To fix CVE-2016-5918, upgrade to IBM Tivoli Storage Manager for Space Management version 7.1.4.2 or later.

3

What is the impact of CVE-2016-5918?

The impact of CVE-2016-5918 is that it exposes the encrypted Tivoli Storage Manager password in application trace output, which could lead to password disclosure.

4

Which software is affected by CVE-2016-5918?

CVE-2016-5918 affects IBM Tivoli Storage Manager for Space Management versions up to 7.1.4.1, as well as earlier versions down to 6.4.0.0.

5

Is there a workaround for CVE-2016-5918?

There are no officially documented workarounds for CVE-2016-5918, so upgrading is recommended.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203