User lockout bypass via inconsistent alias attribution
Published Aug 9, 2025 · Updated Aug 11, 2025
Authentication throttling bypass in OpenBao 0.1.0 through 2.3.1 allows remote attackers to evade Userpass or LDAP user lockout. Alias lookahead and full login processing attribute equivalent usernames differently, so failed attempts are recorded against a different alias than the account used for authentication. The affected auth method must be enabled; varying equivalent username case or spacing permits continued password attempts against one account.
Summary
What happened
Authentication throttling bypass in OpenBao 0.1.0 through 2.3.1 allows remote attackers to evade Userpass or LDAP user lockout. Alias lookahead and full login processing attribute equivalent usernames differently, so failed attempts are recorded against a different alias than the account used for authentication. The affected auth method must be enabled; varying equivalent username case or spacing permits continued password attempts against one account.
The record
- CVE
- CVE-2025-54998
- Published
- Aug 9, 2025
- Updated
- Aug 11, 2025
- Vendor
- OpenBao
- Product
- OpenBao
- Classifications
- CWE-307, T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 9, 2025CVE publishedPublication date reported by the CVE source.
- Aug 11, 2025Record 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=>= 0.1.0, < 2.3.2
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