{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-35975 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-35975 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-35975 is a critical code injection vulnerability in weaveworks vscode-gitops-tools, published on 18 Aug 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-35975 and fix it if it is affected.\n\nWhat it is: CVE-2022-35975 is a critical code injection vulnerability in weaveworks vscode-gitops-tools, published on 18 Aug 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-35975 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-35975/ (Markdown: https://insights.sbomify.com/CVE-2022-35975/index.md)","id":"CVE-2022-35975","markdown":"https://insights.sbomify.com/CVE-2022-35975/index.md","name":"CVE-2022-35975","record":{"aliases":["GHSA-873x-829r-gxcp"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"VSCode GitOps extension","requires_auth":"low_privilege","summary":"A specially crafted Flux object allows remote code execution in the VSCode GitOps Tools extension, affecting users managing shared clusters.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gitops_tools","vendor":"weave"}],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H","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 can make it easier to manage Flux objects. A specially crafted Flux object may allow for remote code execution in the machine running the extension, in the context of the user that is running VSCode. Users using the VSCode extension to manage clusters that are shared amongst other users are affected by this issue. The only safe mitigation is to update to the latest version of the extension.","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 object validation allows for arbitrary code execution in GitOps Tools Extension for VSCode","id":"CVE-2022-35975","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Improper KubeConfig handling allows arbitrary code execution","id":"CVE-2022-35976"},"packages":[],"prev":{"headline":"Segfault in `QuantizeDownAndShrinkRange` in TensorFlow","id":"CVE-2022-35974"},"products":["vscode-gitops-tools"],"published":"2022-08-18","related":[{"cvss_score":5.2,"headline":"Improper KubeConfig handling allows arbitrary code execution","id":"CVE-2022-35976","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":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["weaveworks"]},"summary":"A specially crafted Flux object allows remote code execution in the VSCode GitOps Tools extension, affecting users managing shared clusters.","url":"https://insights.sbomify.com/CVE-2022-35975/"}