Skip to content
Fencer Intel
medium 5.7

CVE-2025-55003 json

OpenBao Login MFA Bypasses Rate Limiting and TOTP Token Reuse

published last yr. modified 2mo ago also BIT-openbao-2025-55003 , EUVD-2025-24032 , GHSA-rxp7-9q75-vj3p , GO-2025-3856

cvss
5.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 20%
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 2.3.1 and below, OpenBao's Login Multi-Factor Authentication (MFA) system allows enforcing MFA using Time-based One Time Password (TOTP). Due to normalization applied by the underlying TOTP library, codes were accepted which could contain whitespace; this whitespace could bypass internal rate limiting of the MFA method and allow reuse of existing MFA codes. This issue was fixed in version 2.3.2. To work around this, use of rate-limiting quotas can limit an attacker's ability to exploit this: https://openbao.org/api-docs/system/rate-limit-quotas/.

Patch / fix

  • go github.com/openbao/openbao 0.0.0-20250807113757-8340a6918f6c, 2.3.2
  • bitnami openbao 0.0.0-20250807113757-8340a6918f6c, 2.3.2
  • openbao openbao 0.0.0-20250807113757-8340a6918f6c, 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

  • openbao openSUSE Tumbleweed 2.3.2-1.1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250811T192933-1.1

opensuse advisories openSUSE-SU-2025:15460-1openSUSE-SU-2025:15434-1

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

alpine advisories ALPINE-CVE-2025-55003

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-55003 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.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
GitHub 3.1 5.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
OSV 3.1 5.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/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-20250807113757-8340a6918f6c
>=0.1.0
2.3.2
0.0.0-20250807113757-8340a6918f6c
bitnami openbao
<0.0.0-20250807113757-8340a6918f6c
>=0.0.1, <2.3.2
0.0.0-20250807113757-8340a6918f6c
2.3.2

Affected products

  • openbao openbao

Classification

Weakness
  • CWE-307 Improper Restriction of Excessive Authentication Attempts

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.