CVE-2016-5919: Weak Encryption

Published Feb 16, 2017
·
Updated

IBM Security Access Manager for Web 7.0.0, 8.0.0, and 9.0.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM Reference #: 1996868.

Affected Software

13 affected components
IBM Security Access Manager For Web 7.0 Firmware
IBM Security Access Manager For Web Appliance=7.0
IBM Security Access Manager For Web 8.0 Firmware
IBM Security Access Manager For Web Appliance=8.0
IBM Security Access Manager for Mobile
IBM Security Access Manager For Mobile Appliance=8.0
IBM Security Access Manager 9.0 Firmware
All of the following
IBM Security Access Manager For Web 7.0 Firmware
IBM Security Access Manager For Web Appliance=7.0
All of the following
IBM Security Access Manager For Web 8.0 Firmware
IBM Security Access Manager For Web Appliance=8.0
All of the following
IBM Security Access Manager for Mobile
IBM Security Access Manager For Mobile Appliance=8.0

Event History

Feb 16, 2017
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
DescriptionWeakness
Data Sourced
via NVD·08: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-5919?

CVE-2016-5919 has a medium severity rating due to its use of weaker cryptographic algorithms.

2

How do I fix CVE-2016-5919?

To fix CVE-2016-5919, ensure that you upgrade to a version of IBM Security Access Manager that uses stronger cryptographic algorithms.

3

What versions of IBM Security Access Manager are affected by CVE-2016-5919?

CVE-2016-5919 affects IBM Security Access Manager for Web versions 7.0.0, 8.0.0, and 9.0.0.

4

What type of threat does CVE-2016-5919 pose?

CVE-2016-5919 poses a risk of exposing sensitive information to unauthorized decryption.

5

Is there a workaround for CVE-2016-5919?

There are no documented workarounds for CVE-2016-5919, the best mitigation is to update to the latest software version.

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