What is GHSA-2q8q-8fgw-9p6p?

GHSA-2q8q-8fgw-9p6p is a security advisory published by GitHub Security Advisories with Medium severity. OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias

Which CVE IDs does GHSA-2q8q-8fgw-9p6p cover?

GHSA-2q8q-8fgw-9p6p covers the following CVE IDs: CVE-2025-55001. Each CVE has its own detail page on EchelonGraph Pulse with the synthesized EG score.

What is the CVSS v3 score of GHSA-2q8q-8fgw-9p6p?

GHSA-2q8q-8fgw-9p6p has a CVSS v3 base score of 6.5, published by GitHub Security Advisories.

Which products are affected by GHSA-2q8q-8fgw-9p6p?

GHSA-2q8q-8fgw-9p6p affects 2 products, including: go/github.com/openbao/openbao:\u003e= 0.1.0, \u003c 2.3.2; go/github.com/openbao/openbao:\u003c 0.0.0-20250807212521-c52795c1ef74.

GHSA-2q8q-8fgw-9p6pMediumCVSS 6.5

OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias

Vendor

GitHub Security Advisories

Published

August 8, 2025

Last Modified

August 11, 2025

🔗 CVE IDs covered (1)

CVE-2025-55001 →

📋 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

🎯 Affected products2

go/github.com/openbao/openbao:>= 0.1.0, < 2.3.2
go/github.com/openbao/openbao:< 0.0.0-20250807212521-c52795c1ef74