{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-35976 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-35976 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-35976 is a medium-severity command injection vulnerability in weaveworks vscode-gitops-tools, published on 18 Aug 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-35976 and fix it if it is affected.\n\nWhat it is: CVE-2022-35976 is a medium-severity command injection vulnerability in weaveworks vscode-gitops-tools, published on 18 Aug 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-35976 in the wild and no public exploit code.\n\nAffected product: weaveworks vscode-gitops-tools. No package-level version data is available, so check the vendor advisory linked from the reference page.\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/CVE-2022-35976/ (Markdown: https://insights.sbomify.com/CVE-2022-35976/index.md)","id":"CVE-2022-35976","markdown":"https://insights.sbomify.com/CVE-2022-35976/index.md","name":"CVE-2022-35976","record":{"aliases":["GHSA-287h-vjhw-jqf7"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"VSCode GitOps extension","requires_auth":"high_privilege","summary":"A specially crafted kubeconfig file allows arbitrary code execution in the VSCode GitOps Tools extension, requiring an upgrade to mitigate.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gitops_tools","vendor":"weave"}],"cvss":{"score":5.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"The GitOps Tools Extension for VSCode relies on kubeconfigs in order to communicate with Kubernetes clusters. A specially crafted kubeconfig leads to arbitrary code execution on behalf of the user running VSCode. Users relying on kubeconfigs that are generated or altered by other processes or users are affected by this issue. Please note that the vulnerability is specific to this extension, and the same kubeconfig would not result in arbitrary code execution when used with kubectl. Using only trust-worthy kubeconfigs is a safe mitigation. However, updating to the latest version of the extension is still highly recommended.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Improper KubeConfig handling allows arbitrary code execution","id":"CVE-2022-35976","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Integer overflow in certain command arguments can drive Redis to OOM panic","id":"CVE-2022-35977"},"packages":[],"prev":{"headline":"Improper object validation allows for arbitrary code execution in GitOps Tools Extension for VSCode","id":"CVE-2022-35975"},"products":["vscode-gitops-tools"],"published":"2022-08-18","related":[{"cvss_score":9,"headline":"Improper object validation allows for arbitrary code execution in GitOps Tools Extension for VSCode","id":"CVE-2022-35975","kev_date_added":null,"published":"2022-08-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["weaveworks"]},"summary":"A specially crafted kubeconfig file allows arbitrary code execution in the VSCode GitOps Tools extension, requiring an upgrade to mitigate.","url":"https://insights.sbomify.com/CVE-2022-35976/"}