# CVE-2022-31098: Weave GitOps leaked cluster credentials into logs on connection errors > Attackers can access sensitive Kubernetes cluster credentials and service account tokens from Weave GitOps logs, enabling unauthorized cluster management. - **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 27 Jun 2022 - **Updated:** 23 Apr 2025 - **Also known as:** GHSA-xggc-qprg-x6mw, GO-2022-0502 ## What is CVE-2022-31098? CVE-2022-31098 is a critical vulnerability in weaveworks weave-gitops, published on 27 Jun 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description Weave GitOps is a simple open source developer platform for people who want cloud native applications, without needing Kubernetes expertise. A vulnerability in the logging of Weave GitOps could allow an authenticated remote attacker to view sensitive cluster configurations, aka KubeConfg, of registered Kubernetes clusters, including the service account tokens in plain text from Weave GitOps's pod logs on the management cluster. An unauthorized remote attacker can also view these sensitive configurations from external log storage if enabled by the management cluster. This vulnerability is due to the client factory dumping cluster configurations and their service account tokens when the cluster manager tries to connect to an API server of a registered cluster, and a connection error occurs. An attacker could exploit this vulnerability by either accessing logs of a pod of Weave GitOps, or from external log storage and obtaining all cluster configurations of registered clusters. A successful exploit could allow the attacker to use those cluster configurations to manage the registered Kubernetes clusters. This vulnerability has been fixed by commit 567356f471353fb5c676c77f5abc2a04631d50ca. Users should upgrade to Weave GitOps core version v0.8.1-rc.6 or newer. There is no known workaround for this vulnerability. Weakness: CWE-532 (Insertion of Sensitive Information into Log File) ## Which versions are affected by CVE-2022-31098? 3 open source packages ship an affected version, including github.com/weaveworks/weave-gitops. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/weaveworks/weave-gitops` | Go | All versions | 0.8.1-rc.6 | | `github.com/weaveworks/weave-gitops` | Go | All versions | 0.8.1-rc.6 | | `github.com/weaveworks/weave-gitops` | Go | All versions | 0.8.1-rc.6 | Products: Weave Weave Gitops. ## How do I fix CVE-2022-31098? Upgrade github.com/weaveworks/weave-gitops to 0.8.1-rc.6 or later. ## Is CVE-2022-31098 being exploited? There is no known exploitation of CVE-2022-31098 in the wild and no public exploit code. ## Other vulnerabilities in weaveworks weave-gitops - [CVE-2022-23508](https://insights.sbomify.com/CVE-2022-23508/): GitOps Run allows for Kubernetes workload injection (high 8.9) - [CVE-2022-23509](https://insights.sbomify.com/CVE-2022-23509/): Weave Gitops Run vulnerable to insecure communication (high 7.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-31098 and fix it if it is affected. What it is: CVE-2022-31098 is a critical vulnerability in weaveworks weave-gitops, published on 27 Jun 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2022-31098 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/weaveworks/weave-gitops (Go): affected all versions; fixed in 0.8.1-rc.6 - github.com/weaveworks/weave-gitops (Go): affected all versions; fixed in 0.8.1-rc.6 - github.com/weaveworks/weave-gitops (Go): affected all versions; fixed in 0.8.1-rc.6 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-31098/ (Markdown: https://insights.sbomify.com/CVE-2022-31098/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-31098 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-31098 - OSV: https://osv.dev/vulnerability/CVE-2022-31098 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-31098/ Summaries are generated and may contain mistakes; the official description above is the record.