CVE-2025-55000
BaseFortify
Publication date: 2025-08-09
Last updated on: 2025-11-13
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openbao | openbao | to 2.3.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-156 | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in OpenBao versions 0.1.0 through 2.3.1 involves the TOTP secrets engine accepting valid codes multiple times instead of only once. This happens due to unexpected normalization behavior in the underlying TOTP library, which allows the same code to be reused. The intended behavior is that each TOTP code should be accepted strictly once to ensure security.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing repeated use of the same TOTP code for authentication or verification, potentially enabling unauthorized access or bypassing security controls. Since TOTP code verification is a privileged action, improper handling could lead to security risks if untrusted systems verify codes multiple times.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that all TOTP codes are first normalized before submitting them to the OpenBao endpoint. Additionally, restrict TOTP code verification to trusted systems only, as it is a privileged action.