Vulnerability in github.com/openbao/openbao (CVE-2025-55001)
Summary
Vulnerability in github.com/openbao/openbao (CVE-2025-55001). Confidential information can be exposed externally. Mitigation: upgrade to 0.0.0-20250807212521-c52795c1ef74 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-55001 has been found in github.com/openbao/openbao.
Confidential information can be exposed externally.
What to do: upgrade github.com/openbao/openbao to 0.0.0-20250807212521-c52795c1ef74 or later.
If unsure, ask your IT team or search "github.com/openbao/openbao CVE-2025-55001" on the vendor's site.
CVE-2025-55001 (github.com/openbao/openbao) — CWE-156
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.0.0-20250807212521-c52795c1ef74 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-156) exists in github.com/openbao/openbao.
Check the vendor advisory for the affected versions of github.com/openbao/openbao.
Severity: ?. Confidential information can be exposed externally.
Update to 0.0.0-20250807212521-c52795c1ef74.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/openbao/openbao' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/openbao/openbao' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/openbao/openbaoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/openbao/openbao to 0.0.0-20250807212521-c52795c1ef74ステージング環境で 0.0.0-20250807212521-c52795c1ef74 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- package github.com
- patch github.com
- web nvd.nist.gov
- web nvd.nist.gov
- web discuss.hashicorp.com