# CVE-2025-24884: kube-audit-rest's example logging configuration could disclose secret values in the audit log

> Using the full-elastic-stack example configuration in kube-audit-rest discloses Kubernetes secret values in audit logs.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jan 2025
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-hcr5-wv4p-h2g2, GO-2025-3431

## What is CVE-2025-24884?

CVE-2025-24884 is a medium-severity vulnerability in RichardoC kube-audit-rest, published on 29 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-24884?

3 open source packages ship an affected version, including github.com/RichardoC/kube-audit-rest.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/RichardoC/kube-audit-rest` | Go | All versions | 0.0.0-20250129191722-db1aa5b86725 |
| `github.com/RichardoC/kube-audit-rest` | Go | All versions | 0.0.0-20250205113217-9df8886b4819 |
| `github.com/RichardoC/kube-audit-rest` | Go | All versions | 0.0.0-20250205113217-9df8886b4819 |

## How do I fix CVE-2025-24884?

Upgrade github.com/RichardoC/kube-audit-rest to a fixed version for your release line: 0.0.0-20250129191722-db1aa5b86725 or 0.0.0-20250205113217-9df8886b4819.

## Is CVE-2025-24884 being exploited?

There is no known exploitation of CVE-2025-24884 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24884 and fix it if it is affected.

What it is: CVE-2025-24884 is a medium-severity vulnerability in RichardoC kube-audit-rest, published on 29 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24884 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/RichardoC/kube-audit-rest (Go): affected all versions; fixed in 0.0.0-20250129191722-db1aa5b86725
- github.com/RichardoC/kube-audit-rest (Go): affected all versions; fixed in 0.0.0-20250205113217-9df8886b4819
- github.com/RichardoC/kube-audit-rest (Go): affected all versions; fixed in 0.0.0-20250205113217-9df8886b4819

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-24884/ (Markdown: https://insights.sbomify.com/CVE-2025-24884/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24884
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24884
- OSV: https://osv.dev/vulnerability/CVE-2025-24884

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24884/
Summaries are generated and may contain mistakes; the official description above is the record.