Skip to content
OpenAdvisories
Medium · 6.5 CVE-2025-55001 BIT-openbao-2025-55001EUVD-2025-24033GHSA-2q8q-8fgw-9p6pGO-2025-3859

OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias

Published Aug 9, 2025 · Updated Aug 11, 2025 · Assigned by GitHub_M

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.

Affected products

VendorProductAffectedFixed
openbao openbao < 2.3.2 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
SLES 15 SP6 govulncheck-vulndb 0.0.20250814T182633-150000.1.98.1 SUSE-SU-2025:02912-1
ReleasePackageFixed inAdvisory
openSUSE Tumbleweed govulncheck-vulndb 0.0.20250811T192933-1.1 openSUSE-SU-2025:15434-1
openSUSE Leap 15.6 govulncheck-vulndb 0.0.20250814T182633-150000.1.98.1 SUSE-SU-2025:02912-1

Affected packages

EcosystemPackageAffectedFixedRecord
Go github.com/openbao/openbao >= 0.1.0, < 2.3.2 2.3.2 GHSA-2q8q-8fgw-9p6p
Go github.com/openbao/openbao < 0.0.0-20250807212521-c52795c1ef74 0.0.0-20250807212521-c52795c1ef74 GHSA-2q8q-8fgw-9p6p
Go github.com/openbao/openbao < 0.0.0-20250807212521-c52795c1ef74 · >= 0.1.0 0.0.0-20250807212521-c52795c1ef74 GO-2025-3859

Advisories 3

References