Credential compromise via inadequate account lockout
Published Aug 28, 2023 · Updated Oct 2, 2024
Improper account lockout in IBM Guardium Cloud Key Manager 1.10.3 and earlier allows remote attackers to brute-force account credentials. The login path keeps accepting repeated failed attempts because the account lockout setting does not adequately restrict them. No prior access or user interaction is required; successful guessing exposes information available to the compromised account.
Summary
What happened
Improper account lockout in IBM Guardium Cloud Key Manager 1.10.3 and earlier allows remote attackers to brute-force account credentials. The login path keeps accepting repeated failed attempts because the account lockout setting does not adequately restrict them. No prior access or user interaction is required; successful guessing exposes information available to the compromised account.
The record
- CVE
- CVE-2023-26271
- Published
- Aug 28, 2023
- Updated
- Oct 2, 2024
- Vendor
- IBM
- Product
- IBM Guardium Cloud Key Manager
- Classifications
- CWE-307, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 2023CVE publishedPublication date reported by the CVE source.
- Oct 2, 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.10.3
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