Skip to content

Example logging configuration could disclose secret values in the audit log

Low
RichardoC published GHSA-hcr5-wv4p-h2g2 Jan 29, 2025

Package

No package listed

Affected versions

<1.0.16

Patched versions

1.0.17

Description

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 9df8886

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?

Severity

Low

CVE ID

CVE-2025-24884

Weaknesses

Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Learn more on MITRE.

Improper Removal of Sensitive Information Before Storage or Transfer

The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors. Learn more on MITRE.

Insertion of Sensitive Information into Log File

Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. Learn more on MITRE.