Sensitive-data exposure via misapplied audit-log HMAC
Published Oct 22, 2025 · Updated Oct 22, 2025
Sensitive-data exposure in OpenBao 2.2.0 through 2.4.1 allows attackers to read ACME and OIDC secrets from audit logs. The audit formatter walks the original response while modifying its clone, so byte-valued HTTPRawBody fields bypass HMAC redaction and remain raw. Exposure requires audit logging plus PKI ACME or identity OIDC issuer use and access to the resulting logs; ACME codes expire quickly.
Summary
What happened
Sensitive-data exposure in OpenBao 2.2.0 through 2.4.1 allows attackers to read ACME and OIDC secrets from audit logs. The audit formatter walks the original response while modifying its clone, so byte-valued HTTPRawBody fields bypass HMAC redaction and remain raw. Exposure requires audit logging plus PKI ACME or identity OIDC issuer use and access to the resulting logs; ACME codes expire quickly.
The record
- CVE
- CVE-2025-62513
- Published
- Oct 22, 2025
- Updated
- Oct 22, 2025
- Vendor
- OpenBao
- Product
- OpenBao
- Classifications
- CWE-532, T1552.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Oct 22, 2025CVE publishedPublication date reported by the CVE source.
- Oct 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.2.0, < 2.4.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo