You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Cross references:
No existing reports found with this module or alias.
See doc/triage.md for instructions on how to triage this report.
modules:
- module: github.com/weaveworks/tf-controller
vulnerable_at: 0.15.1
packages:
- package: tf-controller
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.
cves:
- CVE-2023-34236
references:
- advisory: https://github.com/weaveworks/tf-controller/security/advisories/GHSA-6hvv-j432-23cv
- report: https://github.com/weaveworks/tf-controller/issues/637
- report: https://github.com/weaveworks/tf-controller/issues/649
- fix: https://github.com/weaveworks/tf-controller/commit/28282bc644054e157c3b9a3d38f1f9551ce09074
- fix: https://github.com/weaveworks/tf-controller/commit/6323b355bd7f5d2ce85d0244fe0883af3881df4e
- fix: https://github.com/weaveworks/tf-controller/commit/9708fda28ccd0466cb0a8fd409854ab4d92f7dca
- fix: https://github.com/weaveworks/tf-controller/commit/98a0688036e9dbcf43fa84960d9a1ef3e09a69cf
The text was updated successfully, but these errors were encountered:
CVE-2023-34236 references github.com/weaveworks/tf-controller, which may be a Go module.
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, functionstfexec.ShowPlan
,tfexec.ShowPlanRaw
, andtfexec.Output
are implicated when thetfexec
object set itsStdout
andStderr
to beos.Stdout
andos.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 versionsv0.14.4
andv0.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 variableDISABLE_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.References:
Cross references:
No existing reports found with this module or alias.
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: