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-55001, CVE-2025-55001, GO-2025-3859
OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias
Impact
OpenBao allows assignment of policies and MFA attribution based upon entity aliases, chosen by the underlying auth method. When using the username_as_alias=true parameter in the LDAP auth method, the caller-supplied username is used verbatim without normalization, allowing an attacker to bypass alias-specific MFA requirements.
Patches
OpenBao v2.3.2 will patch this issue.
Workarounds
LDAP methods are only vulnerable if using username_as_alias=true. Remove all usage of this parameter and update any entity aliases accordingly.
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-20250807212521-c52795c1ef74 (semver)0.0.0-20250807212521-c52795c1ef74
0.0.0-20250807212521-c52795c1ef74go 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