CVE-2025-55001
mediumPriorität · verfolgen · 0EPSS 0.002 · 14. PerzentilDEEURUUSEPSS · bewertet 2026-10-27
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.
cvss
Technischer Schweregrad, 0–10. Eine Zeile je Quelle.
Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen
SSVC
Eine Handlungsentscheidung — aus Ausnutzung und Auswirkung.
schwächen
Die CWE-Schwächeklassen, zu denen dies gehört.
betroffene Produkte (12)
Betroffene Produkte und Versionsbereiche.
- Go github.com/openbao/openbao< 0.0.0-20250807212521-c52795c1ef74osvUSpkg:golang/github.com/openbao/openbao
Advisories (4)
Hersteller- und Ökosystem-Meldungen dazu.
- WID-SEC-W-2025-1855OpenBao: Mehrere SchwachstellenDeutsch2025-08-17csaf · cert_bundDE
Ein entfernter, authentisierter oder anonymer Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um beliebigen Code auszuführen, Root-Rechte zu erlangen, Sicherheitsmaßnahmen zu umgehen und vertrauliche Informationen offenzulegen.
- GHSA-2q8q-8fgw-9p6pOpenBao LDAP MFA Enforcement Bypass When Using Username As Alias2025-08-08ghsa · osvUS
### 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
- BIT-openbao-2025-55001OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias2026-07-27vendor · osvUS
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.
- GO-2025-3859OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias in github.com/openbao/openbao2025-08-11vendor · osvUS
OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias in github.com/openbao/openbao. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/openbao/openbao before v2.3.2.
auch bekannt als (7)
Weitere Namen und Kennungen dieser Entität.
- CNNVD-202508-813cnnvd
- EUVD-2025-24033enisa_euvd
- BDU:2025-11279fstec_bdu
- GHSA-2q8q-8fgw-9p6penisa_euvd
- BIT-openbao-2025-55001osv
- GHSA-2q8q-8fgw-9p6posv
- GO-2025-3859osv
quellen
Welche Quellen diesen Datensatz belegen und wann.
Referenzen (11)
Externe Belege — Patches, Meldungen, Analysen.
- https://access.redhat.com/security/cve/cve-2025-55001cnnvd
- https://discuss.hashicorp.com/t/hcsec-2025-20-vault-ldap-mfa-enforcement-bypass-when-using-username-as-alias/76092cnnvd
- https://github.com/openbao/openbao/commit/c52795c1ef746c7f2c510f9225aa8ccbbd44f9fccnnvd
- https://github.com/openbao/openbao/releasesPatchcnnvd
- https://github.com/openbao/openbao/security/advisories/GHSA-2q8q-8fgw-9p6pcnnvd
- https://discuss.hashicorp.com/t/hcsec-2025-20-vault-ldap-mfa-enforcement-bypass-when-using-username-as-alias/76092enisa_euvd
- https://github.com/openbao/openbao/commit/c52795c1ef746c7f2c510f9225aa8ccbbd44f9fcenisa_euvd
- https://github.com/openbao/openbao/security/advisories/GHSA-2q8q-8fgw-9p6penisa_euvd
Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan