Categories
CVE-2025-62513

Vulnerability in github.com/openbao/openbao (CVE-2025-62513)

Summary

Vulnerability in github.com/openbao/openbao (CVE-2025-62513). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.0.0-20251022165510-cc2c476bac66 or later.

Original description

The description as published by the source.

OpenBao is an open source identity-based secrets management system. In versions 2.2.0 to 2.4.1, OpenBao's audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC'd). This impacts those using the ACME functionality of PKI, resulting in short-lived ACME verification challenge codes being leaked in the audit logs. Additionally, this impacts those using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use. This issue has been patched in OpenBao 2.4.2.

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 weakness called CVE-2025-62513 was discovered in github.com/openbao/openbao.
Severity is Info. Low severity or not yet rated.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "github.com/openbao/openbao CVE-2025-62513".

CVE-2025-62513 (github.com/openbao/openbao). Severity: Info. Category: CWE-532.
Response plan:

  1. Check the vendor advisory for affected versions and the patched release.
  2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
  3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
  4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
    PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem

A weakness (CVE-2025-62513) in github.com/openbao/openbao. A serious software flaw has been identified.

📍 Affected scope

Target versions of github.com/openbao/openbao (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: Info. Low severity or not yet rated.

🔧 How to fix

Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-532)

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.

Affected packages

Go github.com/openbao/openbao
[{"type":"SEMVER","events":[{"introduced":"0.0.0-20241114205727-b1235e585db7"},{"fixed":"0.0.0-20251022165510-cc2c476bac66"}]}]
Bitnami openbao
[{"type":"SEMVER","events":[{"introduced":"2.2.0"},{"fixed":"2.4.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details