Skip to content

← Public intelligence

npm package

@mittwald/kubernetes

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.4npmAmendedPublished

    @mittwald/kubernetes's secret contents leaked via debug logging

    GHSA-g35x-j6jj-8g7j

    Affected
    • npm @mittwald/kubernetes < 3.5.0
    Fixed in
    3.5.0· Vendor fix available
    Issue
    Impact When debug logging is enabled (via DEBUG environment variable), the Kubernetes client may log all response bodies into the debug log -- including sensitive data from Secret resources. When running in a Kubernetes cluster, this might expose sensitive information to users who are not authorised to access secrets, but have access to Pod logs (either directly using kubectl, or by Pod logs being shipped elsewhere). Patches Upgrade to 3.5.0 or newer. Workarounds Disable debug logging entirely, or exclude the kubernetes:client debug item (for example, using DEBUG=,-kubernetes:client). References - https://cwe.mitre.org/data/definitions/532.html

    Recommended action: Upgrade to 3.5.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →