Information disclosure via hard-coded credentials
Published Oct 16, 2023 · Updated Sep 16, 2024
Hard-coded credentials in IBM Security Verify Governance 10.0 allow attackers to disclose sensitive information over an adjacent network. IBM has not disclosed whether the embedded credential is used for inbound authentication, outbound component access, or internal-data encryption, nor has it named the affected locus. Exploitation requires adjacent-network reachability and high complexity without authentication, and the documented impact is limited to confidentiality.
Summary
What happened
Hard-coded credentials in IBM Security Verify Governance 10.0 allow attackers to disclose sensitive information over an adjacent network. IBM has not disclosed whether the embedded credential is used for inbound authentication, outbound component access, or internal-data encryption, nor has it named the affected locus. Exploitation requires adjacent-network reachability and high complexity without authentication, and the documented impact is limited to confidentiality.
The record
- CVE
- CVE-2023-33836
- Published
- Oct 16, 2023
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Security Verify Governance - Identity Manager
- Classifications
- CWE-798
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2023CVE 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=10.0
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