Confidential data exposure via hard-coded credentials
Published Mar 2, 2020 · Updated Sep 17, 2024
Hard-coded credentials in IBM Security Verify Information Queue 1.0.0 through 1.0.4 allow remote attackers to read protected data. The product embeds a reusable secret for authentication, external communication, or internal encryption, but IBM has not disclosed its storage locus. No account or user action is required; successful use exposes confidential data without reported modification or service interruption.
Summary
What happened
Hard-coded credentials in IBM Security Verify Information Queue 1.0.0 through 1.0.4 allow remote attackers to read protected data. The product embeds a reusable secret for authentication, external communication, or internal encryption, but IBM has not disclosed its storage locus. No account or user action is required; successful use exposes confidential data without reported modification or service interruption.
The record
- CVE
- CVE-2020-4283
- Published
- Mar 2, 2020
- Updated
- Sep 17, 2024
- Vendor
- IBM
- Product
- Security Verify Information Queue
- Classifications
- CWE-798
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 2, 2020CVE publishedPublication date reported by the CVE source.
- Sep 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=1.0.0
- Affected versionversion=1.0.1
- Affected versionversion=1.0.2
- Affected versionversion=1.0.3
- Affected versionversion=1.0.4
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