dbcve.org
Gitops ToolsApplication · Weave

CVE-2022-35975

CRITICAL · 9.8 CVSS v3.1 Published 2022-08-18
Fix available
A fix is available. Upgrade to after 0.20.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The GitOps Tools Extension for VSCode has a remote code execution vulnerability where specially crafted Flux objects can execute arbitrary code on the machine running VSCode, in the context of the current user. This is exploitable when the extension is used to manage shared Kubernetes clusters.

MitigationUpdate the GitOps Tools Extension for VSCode to the latest version available in the VSCode marketplace. Avoid managing shared clusters with untrusted Flux objects until the update is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gitops ToolsApplication
Affected:>= 0.7.0, <= 0.20.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Weave Gitops Tools extension is installed
    Open VSCode, go to Extensions view (Ctrl+Shift+X), search for 'Weave Gitops' or 'GitOps Tools'. Look for an installed extension with that name.
    Affected if The extension is listed as installed in VSCode
  2. Identify the installed version of Weave Gitops Tools
    In VSCode Extensions view, click on the Weave Gitops Tools extension to open its details. The version number is displayed in the extension information panel (typically in the format 0.x.x).
    Affected if The installed version falls within the range >= 0.7.0 and <= 0.20.2
  3. Determine if the extension is managing shared Kubernetes clusters
    Review your VSCode workspace and extension usage. Check if you have kubeconfig files configured that point to shared or multi-tenant Kubernetes clusters, or if you have connected the extension to any cluster that is accessible by other users.
    Affected if The extension is configured to manage or connect to shared Kubernetes clusters accessible by multiple users or untrusted parties
  4. Check if Flux objects from untrusted sources are being processed
    Examine your Kubernetes cluster and Flux configuration. Identify if any Flux sources (GitRepository, OCIRepository, Bucket) could contain Flux objects from untrusted or public repositories that you do not control.
    Affected if Flux objects from untrusted or publicly accessible sources could be reconciled by the cluster connected to VSCode

You are affected if the Weave Gitops Tools extension version is between 0.7.0 and 0.20.2 AND you use it to manage shared Kubernetes clusters that could receive Flux objects from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.20.2
Interim mitigation

Update the GitOps Tools Extension for VSCode to the latest version available in the VSCode marketplace. Avoid managing shared clusters with untrusted Flux objects until the update is applied.

Recommended fix High confidence

latest version (>0.20.2) from VSCode Marketplace

  1. 1. Open VSCode and navigate to the Extensions view (Ctrl+Shift+X or Cmd+Shift+X)
  2. 2. Search for 'GitOps Tools' or 'Weave GitOps' in the Extensions marketplace
  3. 3. Locate the GitOps Tools extension and check the current installed version
  4. 4. If installed version is <= 0.20.2, click 'Update' to install the latest version
  5. 5. Restart VSCode after the update completes
  6. 6. Verify the extension updated successfully by checking the version in Extensions > Installed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gitops Tools Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-35975 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-35975 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data