CVE-2025-24884GHSA-HCR5-WV4P-H2G2GO-2025-3431
kube-audit-rest's example logging configuration could disclose secret values in the audit log
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.0.16, 0.0.0-20250205113217-9df8886b4819, 0.0.0-20250129191722-db1aa5b86725
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
kube-audit-rest is a simple logger of mutation/creation requests to the k8s api. 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. This vulnerability is fixed in 1.0.16.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- RichardoC kube-audit-rest
fixed in 1.0.16
- github.com/RichardoC/kube-audit-restGo
fixed in 0.0.0-20250205113217-9df8886b4819
- github.com/RichardoC/kube-audit-restGo
fixed in 0.0.0-20250129191722-db1aa5b86725