Local secret disclosure via hard-coded credentials
Published May 5, 2021 · Updated Sep 16, 2024
Hard-coded credentials in IBM QRadar SIEM allow local users to disclose authentication or cryptographic secrets through local access. The product embeds a password or cryptographic key for inbound authentication, external-component communication, or internal-data encryption, but IBM has not disclosed the credential's locus or retrieval path. Affected releases span the 7.3 and 7.4 branches, and the published impact is limited to confidentiality.
Summary
What happened
Hard-coded credentials in IBM QRadar SIEM allow local users to disclose authentication or cryptographic secrets through local access. The product embeds a password or cryptographic key for inbound authentication, external-component communication, or internal-data encryption, but IBM has not disclosed the credential's locus or retrieval path. Affected releases span the 7.3 and 7.4 branches, and the published impact is limited to confidentiality.
The record
- CVE
- CVE-2020-4932
- Published
- May 5, 2021
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- QRadar SIEM
- Classifications
- CWE-798, T1552
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 5, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=7.3
- Affected versionversion=7.4
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.
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