Medium, CVSS 5.1GoPublished
kube-audit-rest's example logging configuration could disclose secret values in the audit log
CVE-2025-24884 · GHSA-hcr5-wv4p-h2g2
- Affected
- Go github.com/RichardoC/kube-audit-rest < 0.0.0-20250205113217-9df8886b4819
- Fixed in
- 0.0.0-20250205113217-9df8886b4819· Vendor fix available
- Issue
- Impact What kind of vulnerability is it? Who is impacted? If the "full-elastic-stack" example vector configuration was used for a real cluster, the previous values of kubernetes secrets would have been disclosed in the audit messages. Patches Has the problem been patched? What versions should users upgrade to? The example has been updated to fix this in commit 9df8886b4819409f566233adc7c3b7a43a4096ba Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading? Replace In the vector "audit-files-json-parser-and-redaction" step with References Are there any links users can visit to find out more?
Recommended action: Upgrade to 0.0.0-20250205113217-9df8886b4819 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.