We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2025-55001

OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias



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.

Reserved 2025-08-04 | Published 2025-08-09 | Updated 2025-08-09 | Assigner GitHub_M


MEDIUM: 6.5CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Problem types

CWE-156: Improper Neutralization of Whitespace

Product status

< 2.3.2
affected

References

github.com/...penbao/security/advisories/GHSA-2q8q-8fgw-9p6p

github.com/...ommit/c52795c1ef746c7f2c510f9225aa8ccbbd44f9fc

discuss.hashicorp.com/...-when-using-username-as-alias/76092

cve.org (CVE-2025-55001)

nvd.nist.gov (CVE-2025-55001)

Download JSON

Share this page
https://cve.threatint.eu/CVE/CVE-2025-55001

Support options

Helpdesk Chat, Email, Knowledgebase