Skip to content
Fencer Intel
low 3.7

CVE-2025-54999 json

OpenBao: Timing Side-Channel in Userpass Auth Method

published last yr. modified 2mo ago also BIT-openbao-2025-54999 , EUVD-2025-24035 , GHSA-hh28-h22f-8357 , GO-2025-3854

cvss
3.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

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/.

Patch / fix

  • go github.com/openbao/openbao 0.0.0-20250806193356-4d9b5d3d6486, 2.3.2
  • bitnami openbao 0.0.0-20250806193356-4d9b5d3d6486, 2.3.2
  • openbao openbao 0.0.0-20250806193356-4d9b5d3d6486, 2.3.2
  • govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20250814T182633-150000.1.98.1

suse advisories SUSE-SU-2025:02912-1

  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250811T192933-1.1

opensuse advisories openSUSE-SU-2025:15434-1

  • openbao Alpine 3.24, Alpine 3.23, Alpine 3.22 2.3.2-r0

alpine advisories ALPINE-CVE-2025-54999

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2025-54999 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OSV 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/openbao/openbao
>=0.1.0, <2.3.2
<0.0.0-20250806193356-4d9b5d3d6486
>=0.1.0
2.3.2
0.0.0-20250806193356-4d9b5d3d6486
bitnami openbao
<0.0.0-20250806193356-4d9b5d3d6486
>=0.0.1, <2.3.2
0.0.0-20250806193356-4d9b5d3d6486
2.3.2

Affected products

  • openbao openbao

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.