Skip to content

OpenBao TOTP Secrets Engine Code Reuse

Moderate severity GitHub Reviewed Published Aug 8, 2025 in openbao/openbao • Updated Aug 11, 2025

Package

gomod github.com/openbao/openbao (Go)

Affected versions

>= 0.1.0, < 2.3.2
< 0.0.0-20250806193153-183891f8d535

Patched versions

2.3.2
0.0.0-20250806193153-183891f8d535

Description

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:

References

@cipherboy cipherboy published to openbao/openbao Aug 8, 2025
Published to the GitHub Advisory Database Aug 8, 2025
Reviewed Aug 8, 2025
Published by the National Vulnerability Database Aug 9, 2025
Last updated Aug 11, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(3rd percentile)

Weaknesses

Improper Neutralization of Whitespace

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as whitespace when they are sent to a downstream component. Learn more on MITRE.

CVE ID

CVE-2025-55000

GHSA ID

GHSA-f7c3-mhj2-9pvg

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.