Information disclosure via hard-coded credentials
Published Oct 23, 2023 · Updated Sep 11, 2024
Hard-coded credentials in IBM Security Verify Governance 10.0 allow remote attackers to obtain sensitive information over the network. The product embeds a password or cryptographic key for inbound authentication, outbound component communication, or internal-data encryption, but IBM has not disclosed its component or exposure path. Exploitation requires no account or user interaction but has high complexity, and the published impact excludes integrity or availability loss.
Summary
What happened
Hard-coded credentials in IBM Security Verify Governance 10.0 allow remote attackers to obtain sensitive information over the network. The product embeds a password or cryptographic key for inbound authentication, outbound component communication, or internal-data encryption, but IBM has not disclosed its component or exposure path. Exploitation requires no account or user interaction but has high complexity, and the published impact excludes integrity or availability loss.
The record
- CVE
- CVE-2022-22466
- Published
- Oct 23, 2023
- Updated
- Sep 11, 2024
- Vendor
- IBM
- Product
- IBM Security Verify Governance - Identity Manager
- Classifications
- CWE-798, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 23, 2023CVE publishedPublication date reported by the CVE source.
- Sep 11, 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=10.0
What conditions does exploitation require?
What is affected?
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