Secret disclosure via incomplete audit-log redaction
Published Jan 29, 2025 · Updated Jan 31, 2025
Information disclosure in RichardoC kube-audit-rest before 1.0.16 allows attackers to expose Kubernetes secrets through audit messages. The full-elastic-stack Vector transform deletes Secret data fields but retains the kubectl.kubernetes.io/last-applied-configuration annotation containing a duplicate of the data. Exposure requires deployment of that example configuration and access to the resulting audit messages, where previous Secret values become readable.
Summary
What happened
Information disclosure in RichardoC kube-audit-rest before 1.0.16 allows attackers to expose Kubernetes secrets through audit messages. The full-elastic-stack Vector transform deletes Secret data fields but retains the kubectl.kubernetes.io/last-applied-configuration annotation containing a duplicate of the data. Exposure requires deployment of that example configuration and access to the resulting audit messages, where previous Secret values become readable.
The record
- CVE
- CVE-2025-24884
- Published
- Jan 29, 2025
- Updated
- Jan 31, 2025
- Vendor
- RichardoC
- Product
- kube-audit-rest
- Classifications
- CWE-532, CWE-200, CWE-212, T1552.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2025CVE publishedPublication date reported by the CVE source.
- Jan 31, 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=< 1.0.16
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