CVE-2025-6013: Vault LDAP MFA Enforcement Bypass When Using Username As Alias
Vault and Vault Enterprise’s (“Vault”) ldap auth method may not have correctly enforced MFA if usernameasalias was set to true and a user had multiple CNs that are equal but with leading or trailing spaces. Fixed in Vault Community Edition 1.20.2 and Vault Enterprise 1.20.2, 1.19.8, 1.18.13, and 1.16.24.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/hashicorp/vaultto a version that resolves this vulnerability.Fixed in 1.20.2 - Upgrade
Upgrade
Vault Community Editionto a version that resolves this vulnerability.Fixed in 1.20.2 - Upgrade
Upgrade
Vault Enterpriseto a version that resolves this vulnerability.Fixed in 1.20.2 - Upgrade
Upgrade
Vault Enterpriseto a version that resolves this vulnerability.Fixed in 1.19.8 - Upgrade
Upgrade
Vault Enterpriseto a version that resolves this vulnerability.Fixed in 1.18.13 - Upgrade
Upgrade
Vault Enterpriseto a version that resolves this vulnerability.Fixed in 1.16.24
Event History
Frequently Asked Questions
What is the severity of CVE-2025-6013?
CVE-2025-6013 is considered a medium severity vulnerability due to its potential impact on multi-factor authentication enforcement.
How do I fix CVE-2025-6013?
To fix CVE-2025-6013, upgrade to Vault Community Edition 1.20.2 or Vault Enterprise 1.20.2, or 1.19.8.
What systems are affected by CVE-2025-6013?
CVE-2025-6013 affects HashiCorp Vault Community Edition versions prior to 1.20.2 and Vault Enterprise versions between 1.16.24 and 1.20.2 or 1.19.8.
What specific issue does CVE-2025-6013 address?
CVE-2025-6013 addresses a vulnerability where the ldap auth method may not enforce multi-factor authentication correctly under certain conditions.
What actions should users of affected versions take regarding CVE-2025-6013?
Users of affected versions should prioritize upgrading to the fixed versions to ensure proper multi-factor authentication enforcement.