Skip to content

GHSA-ghfh-fmx4-26h8 BIT-openbao-2025-62513 CVE-2025-62513 GO-2025-4049

OpenBao leaks HTTPRawBody in Audit Logs

High Go
Severity
0.0 / 10
High · CVSS 4.0
Exploit chance (EPSS)
0.32%
Chance of exploitation in the next 30 days. Higher than 24.57% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-532 Insertion of Sensitive Information into Log File
Fix
0.0.0-20251022165510-cc2c476bac66
Upgrade github.com/openbao/openbao to this version or later

Description

Impact

OpenBao's audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC'd). This impacted the following subsystems:

  • When using the ACME functionality of PKI, this would result in short-lived ACME verification challenge codes being leaked in the audit logs.
  • When using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs.

Third-party plugins may be affected.

Patches

OpenBao v2.4.2 will patch this issue.

Workarounds

If users do not use the above functionality, they are not impacted. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use.

Affected versions

Go

PackageVulnerableFixed in
github.com/openbao/openbao
>= 0.0.0-20241114205727-b1235e585db7, < 0.0.0-20251022165510-cc2c476bac66
0.0.0-20251022165510-cc2c476bac66

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/openbao/openbao Go → 0.0.0-20251022165510-cc2c476bac66

go
go get github.com/openbao/openbao@v0.0.0-20251022165510-cc2c476bac66 && go mod tidy

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
Present
Privileges required
High
User interaction
Passive
Confidentiality (vulnerable system)
High
Integrity (vulnerable system)
None
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-532: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How to prevent it
  • Architecture and Design, Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
  • Distribution: Remove debug log files before deploying the application into production.
  • Operation: Protect log files against unauthorized read/write.
  • Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-xp3c-3jw3-4vcr
OpenBao Skips Stricter Deny Policy for LIST operations
Medium Also affects github.com/openbao/openbao
GHSA-34fc-gh42-pj53
OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack
Critical Also affects github.com/openbao/openbao
GHSA-444v-8vxr-p36h
OpenBao Agent Writes Secrets to Stdout
Low Also affects github.com/openbao/openbao
GHSA-59w7-v8rr-pr4p
OpenBao's Templated Policies Allow Privilege Escalation via Wildcard Characters
High Also affects github.com/openbao/openbao
GHSA-8w8f-r2xv-4q4j
OpenBao: Transit secrets engine crashes on key creation with `derived: true` for asymmetric key types
Medium Also affects github.com/openbao/openbao
GHSA-mwr2-wmgp-crj6
OpenBao's System Backend allows Unauthorized Management of the containing Namespace
Low Also affects github.com/openbao/openbao
GHSA-c36x-h252-g9x2
OpenBao: Cross-namespace lease revocation/renewal via canonical sys/leases/{revoke,renew} — incomplete fix of CVE-2026-45808
Low Also affects github.com/openbao/openbao
GHSA-6mwx-4547-5vc9
OpenBao: LDAPi ldaputil (wrong escape func)
Medium Also affects github.com/openbao/openbao
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor