GitHub Advisoryadvisory · Go

GHSA-2q8q-8fgw-9p6p OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias

MEDIUM Published 2025-08-08 Modified 2025-08-11 Official page ↗
Aliases
CVE-2025-55001
Ecosystem
Go
Packages
github.com/openbao/openbao
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
Weaknesses
CWE-156
Reviewed
2025-08-08

Affected packages

• Go github.com/openbao/openbao: >= 0.1.0, < 2.3.2 → fixed in 2.3.2 • Go github.com/openbao/openbao: < 0.0.0-20250807212521-c52795c1ef74 → fixed in 0.0.0-20250807212521-c52795c1ef74

Description

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: • https://discuss.hashicorp.com/t/hcsec-2025-20-vault-ldap-mfa-enforcement-bypass-when-using-username-as-alias/76092 • https://nvd.nist.gov/vuln/detail/CVE-2025-6013

Related

Alias · CVE (1)

  • CVE-2025-55001 OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. vulnerability

Weakness · CWE (1)

  • CWE-156 Improper Neutralization of Whitespace weakness

References