Advisory

GHSA-f7c3-mhj2-9pvg

Also known as: BIT-openbao-2025-55000, CVE-2025-55000, GO-2025-3853

Summary

OpenBao TOTP Secrets Engine Code Reuse

Details

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:

  • https://discuss.hashicorp.com/t/hcsec-2025-17-vault-totp-secrets-engine-code-reuse/76036
  • https://nvd.nist.gov/vuln/detail/CVE-2025-6014

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-08-08 14:42 UTC
Modified
2026-07-27 09:11 UTC

Affected packages and fixes

github.com/openbao/openbao

Go · All systems

Affected

  • introduced 0.1.0, fixed 2.3.2 (semver)

Fixed versions

2.3.2

Fix

github.com/openbao/openbao

Go · All systems

Affected

  • introduced 0, fixed 0.0.0-20250806193153-183891f8d535 (semver)

Fixed versions

0.0.0-20250806193153-183891f8d535

Fix

  • Fixed version 0.0.0-20250806193153-183891f8d535
    go 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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences