{"answers":{"affected":"2 open source packages ship an affected version, including @mittwald/kubernetes.","exploited":"There is no known exploitation of GHSA-g35x-j6jj-8g7j in the wild and no public exploit code.","fix":"Upgrade @mittwald/kubernetes to 3.5.0 or later.","what":"GHSA-g35x-j6jj-8g7j is a vulnerability in @mittwald/kubernetes, published on 2 May 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-g35x-j6jj-8g7j and fix it if it is affected.\n\nWhat it is: GHSA-g35x-j6jj-8g7j is a vulnerability in @mittwald/kubernetes, published on 2 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-g35x-j6jj-8g7j in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @mittwald/kubernetes (npm): affected all versions; fixed in 3.5.0\n- @mittwald/kubernetes (npm): affected all versions; fixed in 3.5.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-g35x-j6jj-8g7j/ (Markdown: https://insights.sbomify.com/GHSA-g35x-j6jj-8g7j/index.md)","id":"GHSA-g35x-j6jj-8g7j","markdown":"https://insights.sbomify.com/GHSA-g35x-j6jj-8g7j/index.md","name":"GHSA-g35x-j6jj-8g7j","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Kubernetes client library","requires_auth":"low_privilege","summary":"Enabling debug logging in the Kubernetes client library leaks sensitive Secret data to logs, exposing it to unauthorized users with log access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n\nWhen 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.\n\nWhen 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).\n\n### Patches\nUpgrade to 3.5.0 or newer.\n\n### Workarounds\nDisable debug logging entirely, or exclude the `kubernetes:client` debug item (for example, using `DEBUG=*,-kubernetes:client`).\n\n### References\n\n- https://cwe.mitre.org/data/definitions/532.html","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"@mittwald/kubernetes's secret contents leaked via debug logging","id":"GHSA-g35x-j6jj-8g7j","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["3.5.0"],"introduced":["0"],"last_affected":[],"package":"@mittwald/kubernetes","purl":null,"source":"GHSA-g35x-j6jj-8g7j"},{"ecosystem":"npm","fixed":["3.5.0"],"introduced":["0"],"last_affected":[],"package":"@mittwald/kubernetes","purl":"pkg:npm/%40mittwald/kubernetes","source":"GHSA-g35x-j6jj-8g7j"}],"products":null,"published":"2023-05-02","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Enabling debug logging in the Kubernetes client library leaks sensitive Secret data to logs, exposing it to unauthorized users with log access.","url":"https://insights.sbomify.com/GHSA-g35x-j6jj-8g7j/"}