Sensitive-data disclosure via byte-slice audit logging
Published Oct 22, 2025 · Updated Oct 22, 2025
Sensitive-data exposure in OpenBao before 2.4.2 allows remote authenticated users to write unredacted response fields to audit logs. In audit/hashstructure.go, hashMap walked the original map while writing a copied map, so byte-slice values bypassed HMAC redaction and remained plaintext. Exposure requires an enabled audit device and a privileged operation returning byte slices, such as base64 sys/raw access or derived Ed25519 signing; attackers with log access can read the emitted data.
Summary
What happened
Sensitive-data exposure in OpenBao before 2.4.2 allows remote authenticated users to write unredacted response fields to audit logs. In audit/hashstructure.go, hashMap walked the original map while writing a copied map, so byte-slice values bypassed HMAC redaction and remained plaintext. Exposure requires an enabled audit device and a privileged operation returning byte slices, such as base64 sys/raw access or derived Ed25519 signing; attackers with log access can read the emitted data.
The record
- CVE
- CVE-2025-62705
- 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.4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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