OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. In versions 0.1.0 through 2.3.1, 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. This issue was fixed in version 2.3.2. To work around this issue, 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/.
Metrics
Affected Vendors & Products
References
History
Sat, 09 Aug 2025 02:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. In versions 0.1.0 through 2.3.1, 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. This issue was fixed in version 2.3.2. To work around this issue, 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/. | |
Title | OpenBao: Timing Side-Channel in Userpass Auth Method | |
Weaknesses | CWE-203 | |
References |
|
|
Metrics |
cvssV3_1
|

Status: PUBLISHED
Assigner: GitHub_M
Published: 2025-08-09T02:00:46.271Z
Updated: 2025-08-09T02:00:46.271Z
Reserved: 2025-08-04T17:34:24.421Z
Link: CVE-2025-54999

No data.

Status : Received
Published: 2025-08-09T03:15:46.597
Modified: 2025-08-09T03:15:46.597
Link: CVE-2025-54999

No data.