Summary
kube-audit-rest's example logging configuration could disclose secret values in the audit log
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Replace
if .request.requestKind.kind == "Secret" {
del(.request.object.data)
.request.object.data.redacted = "REDACTED"
del(.request.oldObject.data)
.request.oldObject.data.redacted = "REDACTED"
}
In the vector "audit-files-json-parser-and-redaction" step
with
if .request.requestKind.kind == "Secret" {
# Redact the secret data
del(.request.object.data)
.request.object.data.redacted = "REDACTED"
del(.request.oldObject.data)
.request.oldObject.data.redacted = "REDACTED"
# Remove the previously set secret data - Not bothering to parse it as this annotation shouldn't ever be needed
del(.request.object.metadata.annotations.["kubectl.kubernetes.io/last-applied-configuration"])
del(.request.oldObject.metadata.annotations.["kubectl.kubernetes.io/last-applied-configuration"])
}
References
Are there any links users can visit to find out more?
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Has the problem been patched? What versions should users upgrade to?
The example has been updated to fix this in commit 9df8886b4819409f566233adc7c3b7a43a4096ba
Frequently Asked Questions
- What is CVE-2025-24884? CVE-2025-24884 is a medium-severity security vulnerability in github.com/RichardoC/kube-audit-rest (go), affecting versions < 0.0.0-20250205113217-9df8886b4819. It is fixed in 0.0.0-20250205113217-9df8886b4819.
- Which versions of github.com/RichardoC/kube-audit-rest are affected by CVE-2025-24884? github.com/RichardoC/kube-audit-rest (go) versions < 0.0.0-20250205113217-9df8886b4819 is affected.
- Is there a fix for CVE-2025-24884? Yes. CVE-2025-24884 is fixed in 0.0.0-20250205113217-9df8886b4819. Upgrade to this version or later.
- Is CVE-2025-24884 exploitable, and should I be worried? Whether CVE-2025-24884 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-24884 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-24884? Upgrade
github.com/RichardoC/kube-audit-restto 0.0.0-20250205113217-9df8886b4819 or later.