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-55000, CVE-2025-55000, GO-2025-3853
OpenBao TOTP Secrets Engine Code Reuse
Impact
OpenBao's TOTP secrets engine could accept valid codes multiple times rather than strictly-once. This was caused by unexpected normalization in the underlying TOTP library.
Patches
OpenBao v2.3.2 will patch this issue.
In patching, codes which were not normalized (strictly N numeric digits) will now be rejected. This is a potentially breaking change.
Workarounds
TOTP code verification is a privileged action; only trusted systems should be verifying codes. Ensure that all codes are first normalized before submitting to the OpenBao endpoint.
References
This issue was disclosed to HashiCorp and is the OpenBao equivalent of the following tickets:
Medium Basis: The source's own band: MODERATE
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-20250806193153-183891f8d535 (semver)0.0.0-20250806193153-183891f8d535
0.0.0-20250806193153-183891f8d535go 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