Credential brute force via inadequate account lockout
Published Jul 14, 2022 · Updated Sep 17, 2024
Improper authentication-attempt restriction in IBM Security Verify Identity Manager 10.0 allows remote attackers to brute-force account credentials. The authentication service applies an inadequate account-lockout setting, permitting repeated credential guesses; IBM has not disclosed the endpoint or enforcement logic. No prior authentication or user interaction is required, and successful guessing exposes only accounts whose credentials are discovered.
Summary
What happened
Improper authentication-attempt restriction in IBM Security Verify Identity Manager 10.0 allows remote attackers to brute-force account credentials. The authentication service applies an inadequate account-lockout setting, permitting repeated credential guesses; IBM has not disclosed the endpoint or enforcement logic. No prior authentication or user interaction is required, and successful guessing exposes only accounts whose credentials are discovered.
The record
- CVE
- CVE-2022-22452
- Published
- Jul 14, 2022
- Updated
- Sep 17, 2024
- Vendor
- IBM
- Product
- IBM Security Verify Governance - Identity Manager
- Classifications
- CWE-307, T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2022CVE 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=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