CVE-2024-49816: 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 stores potentially sensitive information in log files that could be read by a local privileged user.

Other sources

IBM Security Guardium Key Lifecycle Manager stores potentially sensitive information in log files that could be read by a local privileged user.

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:42 PM
Data Sourced
via MITRE·05:42 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-49816?

CVE-2024-49816 is considered a medium severity vulnerability due to the exposure of sensitive information in log files.

2

How do I fix CVE-2024-49816?

To fix CVE-2024-49816, you should upgrade to the latest version of IBM Security Guardium Key Lifecycle Manager that addresses this vulnerability.

3

Who is affected by CVE-2024-49816?

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

4

What information is stored insecurely in CVE-2024-49816?

CVE-2024-49816 potentially exposes sensitive information which is stored in log files accessible to privileged users.

5

Is there a workaround for CVE-2024-49816?

Currently, the recommended action for CVE-2024-49816 is to update to the fixed version as no specific workaround is provided.

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