github.com/openbao/openbao
Affected
- introduced
0.1.0, fixed2.3.2(semver)
Fixed versions
2.3.2
Fix
- Fixed version
2.3.2go get github.com/openbao/[email protected]
Advisory
Also known as: BIT-openbao-2025-54999, CVE-2025-54999, GO-2025-3854
OpenBao has a Timing Side-Channel in the Userpass Auth Method
Impact
When using OpenBao's userpass auth method, user enumeration was possible due to timing difference between non-existent users and users with stored credentials. This is independent of whether the supplied credentials were valid for the given user.
Patches
OpenBao v2.3.2 will patch this issue.
Workarounds
Users may use another auth method or apply rate limiting quotas to limit the number of requests in a period of time: https://openbao.org/api-docs/system/rate-limit-quotas/
References
This issue was disclosed to HashiCorp and is the OpenBao equivalent of the following tickets:
Barring further information, this is also assumed to cover and remediate the following additional vulnerability:
If this is not the case as further details emerge, a new CVE will be assigned for remediating that. Otherwise, no further CVE will be sought.
Low Basis: The source's own band: LOW
0.1.0, fixed 2.3.2 (semver)2.3.2
2.3.2go get github.com/openbao/[email protected]0, fixed 0.0.0-20250806193356-4d9b5d3d6486 (semver)0.0.0-20250806193356-4d9b5d3d6486
0.0.0-20250806193356-4d9b5d3d6486go get github.com/openbao/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0