Advisory

GHSA-2q8q-8fgw-9p6p

Also known as: BIT-openbao-2025-55001, CVE-2025-55001, GO-2025-3859

Summary

OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-08-08 15:17 UTC
Modified
2026-07-27 09:11 UTC

Affected packages and fixes

github.com/openbao/openbao

Go · All systems

Affected

  • introduced 0.1.0, fixed 2.3.2 (semver)

Fixed versions

2.3.2

Fix

github.com/openbao/openbao

Go · All systems

Affected

  • introduced 0, fixed 0.0.0-20250807212521-c52795c1ef74 (semver)

Fixed versions

0.0.0-20250807212521-c52795c1ef74

Fix

  • Fixed version 0.0.0-20250807212521-c52795c1ef74
    go get github.com/openbao/[email protected]

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences