CVE-2025-55001

CVSS v3 6.5 MEDIUM

6.5^/10

CVSS v3 : MEDIUM

Vector :

Exploitability : 1.2 / Impact : 5.2

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required HIGH

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact NONE

Scope UNCHANGED

O

penBao 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.

References

Link	Resource
https://discuss.hashicorp.com/t/hcsec-2025-20-vault-ldap-mfa-enforcement-bypass-when-using-username-as-alias/76092	Not Applicable
https://github.com/openbao/openbao/commit/c52795c1ef746c7f2c510f9225aa8ccbbd44f9fc	Patch
https://github.com/openbao/openbao/security/advisories/GHSA-2q8q-8fgw-9p6p	Vendor Advisory

Configurations

Configuration 1 (hide)

cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*

History

12 Aug 2025, 20:44

Type	Values Removed	Values Added
New CVE

Information

Published : 2025-08-09 03:15

Updated : 2025-08-12 20:44

NVD link : CVE-2025-55001

Mitre link : CVE-2025-55001

CVE.ORG link : CVE-2025-55001

JSON object : View

Products Affected

openbao

CWE

CWE-156

Improper Neutralization of Whitespace

{"id": "CVE-2025-55001", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "[email protected]", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "HIGH", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 1.2}]}, "published": "2025-08-09T03:15:46.887", "references": [{"url": "https://discuss.hashicorp.com/t/hcsec-2025-20-vault-ldap-mfa-enforcement-bypass-when-using-username-as-alias/76092", "tags": ["Not Applicable"], "source": "[email protected]"}, {"url": "https://github.com/openbao/openbao/commit/c52795c1ef746c7f2c510f9225aa8ccbbd44f9fc", "tags": ["Patch"], "source": "[email protected]"}, {"url": "https://github.com/openbao/openbao/security/advisories/GHSA-2q8q-8fgw-9p6p", "tags": ["Vendor Advisory"], "source": "[email protected]"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "[email protected]", "description": [{"lang": "en", "value": "CWE-156"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "OpenBao existe para proporcionar una soluci\u00f3n de software que permite gestionar, almacenar y distribuir datos confidenciales, como secretos, certificados y claves. En las versiones 2.3.1 y anteriores, OpenBao permit\u00eda la asignaci\u00f3n de pol\u00edticas y la atribuci\u00f3n de MFA seg\u00fan alias de entidad, seleccionados mediante el m\u00e9todo de autenticaci\u00f3n subyacente. Cuando se utilizaba el par\u00e1metro username_as_alias=true en el m\u00e9todo de autenticaci\u00f3n LDAP, el nombre de usuario proporcionado por el usuario se utilizaba textualmente sin normalizaci\u00f3n, lo que permit\u00eda a un atacante eludir los requisitos de MFA espec\u00edficos del alias. Este problema se solucion\u00f3 en la versi\u00f3n 2.3.2. Para solucionarlo, elimine el uso del par\u00e1metro username_as_alias=true y actualice los alias de entidad seg\u00fan corresponda."}], "lastModified": "2025-08-12T20:44:04.173", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "5572B591-02AC-4B8F-8956-FC9A606D7F32", "versionEndExcluding": "2.3.2"}], "operator": "OR"}]}], "sourceIdentifier": "[email protected]"}