Skip to content
Fencer Vulns
medium 5.1

CVE-2025-24884 json

kube-audit-rest's example logging configuration could disclose secret values in the audit log

published 2025-01-29 21 mo ago modified 2026-06-17 4 mo ago also GHSA-hcr5-wv4p-h2g2 , GO-2025-3431 , EUVD-2025-0167

cvss
5.1
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits
0
none known

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.

Patch / fix

  • go github.com/RichardoC/kube-audit-rest 0.0.0-20250129191722-db1aa5b86725, 0.0.0-20250205113217-9df8886b4819
  • govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20250207T224745-150000.1.32.1

suse advisories SUSE-SU-2025:0429-1

  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250204T220613-1.1

opensuse advisories openSUSE-SU-2025:14732-1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
21 mo ago

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 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
CNA 4.0 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
go github.com/RichardoC/kube-audit-rest
<0.0.0-20250205113217-9df8886b4819
<0.0.0-20250129191722-db1aa5b86725
0.0.0-20250205113217-9df8886b4819
0.0.0-20250129191722-db1aa5b86725

Affected products

  • RichardoC kube-audit-rest

Classification

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

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.