Vulnerabilities · 2025 · Openbao
CVE-2025-55001
Openbao vulnerability
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.
Affected products
Openbao. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Openbao runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/openbao/openbao/security/advisories/GHSA-2q8q-8fgw-9p6p · Vendor Advisory
- github.com/openbao/openbao/commit/c52795c1ef746c7f2c510f9225aa8ccbbd44f9fc · Patch
- discuss.hashicorp.com/t/hcsec-2025-20-vault-ldap-mfa-enforcement-bypass-when-using-usernam
- nvd.nist.gov/vuln/detail/CVE-2025-6013
- nvd.nist.gov/vuln/detail/CVE-2025-55001
- github.com/advisories/GHSA-2q8q-8fgw-9p6p
- nvd.nist.gov/vuln/detail/CVE-2025-55001
- cve.org/CVERecord?id=CVE-2025-55001
More vulnerabilities in Openbao products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.