CVE-2024-49819: IBM Security Guardium Key Lifecycle Manager information disclosure

Published Nov 7, 2024
·
Updated

IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 could allow a remote attacker to obtain sensitive information in cleartext in a communication channel that can be sniffed by unauthorized actors.

Other sources

IBM Security Guardium Key Lifecycle Manager could allow a remote attacker to obtain sensitive information in cleartext in a communication channel that can be sniffed by unauthorized actors.

IBM

Affected Software

5 affected components
IBM Security Guardium Key Lifecycle Manager<=4.1, 4.1.1, 4.2, 4.2.1
IBM Security Guardium Key Lifecycle Manager=4.1.0
IBM Security Guardium Key Lifecycle Manager=4.1.1
IBM Security Guardium Key Lifecycle Manager=4.2.0
IBM Security Guardium Key Lifecycle Manager=4.2.1

Event History

Nov 7, 2024
CVE Published
via IBM·12:00 AM
Dec 17, 2024
CVE Published
via MITRE·05:41 PM
Data Sourced
via MITRE·05:41 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

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-2024-49819?

CVE-2024-49819 is classified as a high severity vulnerability due to the potential exposure of sensitive information.

2

How do I fix CVE-2024-49819?

To address CVE-2024-49819, it is recommended to update IBM Security Guardium Key Lifecycle Manager to the latest version that addresses this vulnerability.

3

Which versions are affected by CVE-2024-49819?

CVE-2024-49819 affects IBM Security Guardium Key Lifecycle Manager versions 4.1, 4.1.1, 4.2.0, and 4.2.1.

4

What type of attack can exploit CVE-2024-49819?

CVE-2024-49819 can be exploited by remote attackers who can sniff communications to obtain sensitive cleartext information.

5

Is there a workaround for CVE-2024-49819?

Currently, the best approach to mitigate CVE-2024-49819 is to upgrade to a patched version of IBM Security Guardium Key Lifecycle Manager.

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