Credential disclosure via configuration-file storage
Published Dec 17, 2024 · Updated Dec 17, 2024
Credential exposure in IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 allows local users to read stored credentials. The product writes user credentials into configuration files without protection sufficient to prevent their recovery by a reader of those files. Access requires local high-privilege rights, and the documented consequence is credential disclosure rather than configuration changes or service interruption.
Summary
What happened
Credential exposure in IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 allows local users to read stored credentials. The product writes user credentials into configuration files without protection sufficient to prevent their recovery by a reader of those files. Access requires local high-privilege rights, and the documented consequence is credential disclosure rather than configuration changes or service interruption.
The record
- CVE
- CVE-2024-49817
- Published
- Dec 17, 2024
- Updated
- Dec 17, 2024
- Vendor
- IBM
- Product
- IBM Guardium Key Lifecycle Manager
- Classifications
- CWE-522, CWE-260, T1552.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 17, 2024CVE publishedPublication date reported by the CVE source.
- Dec 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.1, 4.1.1, 4.2.0, 4.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo