Account compromise via weak default password policy
Published May 28, 2020 · Updated Sep 16, 2024
Weak password requirements in IBM Security Identity Governance and Intelligence 5.2.6 allow remote attackers to compromise user accounts. The default password policy accepts weak passwords instead of enforcing strength requirements. Exploitation requires a reachable login interface and an account retaining a weak password; successful guessing exposes that account's information.
Summary
What happened
Weak password requirements in IBM Security Identity Governance and Intelligence 5.2.6 allow remote attackers to compromise user accounts. The default password policy accepts weak passwords instead of enforcing strength requirements. Exploitation requires a reachable login interface and an account retaining a weak password; successful guessing exposes that account's information.
The record
- CVE
- CVE-2020-4245
- Published
- May 28, 2020
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Security Identity Governance and Intelligence
- Classifications
- CWE-521, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2020CVE 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=5.2.6
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.
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