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 allowed the assignment of policies and MFA attribution based upon entity aliases, chosen by the underlying auth method. When the username_as_alias=true parameter in the LDAP auth method was in use, the caller-supplied username was used verbatim without normalization, allowing an attacker to bypass alias-specific MFA requirements. This issue was fixed in version 2.3.2. To work around this, remove all usage of the username_as_alias=true parameter and update any entity aliases accordingly.
Metrics
Affected Vendors & Products
References
History
Sat, 09 Aug 2025 02:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | 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 allowed the assignment of policies and MFA attribution based upon entity aliases, chosen by the underlying auth method. When the username_as_alias=true parameter in the LDAP auth method was in use, the caller-supplied username was used verbatim without normalization, allowing an attacker to bypass alias-specific MFA requirements. This issue was fixed in version 2.3.2. To work around this, remove all usage of the username_as_alias=true parameter and update any entity aliases accordingly. | |
Title | OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias | |
Weaknesses | CWE-156 | |
References |
| |
Metrics |
cvssV3_1
|

Status: PUBLISHED
Assigner: GitHub_M
Published: 2025-08-09T02:01:29.056Z
Updated: 2025-08-09T02:01:29.056Z
Reserved: 2025-08-04T17:34:24.421Z
Link: CVE-2025-55001

No data.

Status : Received
Published: 2025-08-09T03:15:46.887
Modified: 2025-08-09T03:15:46.887
Link: CVE-2025-55001

No data.