KubeVela Terraform remote loader DoS via unbounded file read
kubevela
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/oam-dev/kubevela Go |
|
|
kubevela
| Product | Affected | Fixed in |
|---|---|---|
| github.com/oam-dev/kubevela Go |
|
|
KubeVela is an open source application delivery platform. Prior to 1.9.14, from 1.10.0-alpha.1 until 1.10.9, and from 1.11.0-alpha.1 until 1.11.0-alpha.4, the Terraform remote configuration loader in pkg/controller/utils/capability.go, GetTerraformConfigurationFromRemote, clones a repository supplied through a core.oam.dev/v1beta1 ComponentDefinition and follows repository-controlled variables.tf or main.tf symlinks. A user with permission to create or update ComponentDefinition objects can point variables.tf to /dev/zero through terraform.path, after which os.Stat and os.ReadFile follow the link and read an unbounded stream before ParseTerraformVariables or HCL parsing can reject the content. The read can exhaust memory, OOM-kill the cluster-wide vela-core controller, cause repeated Pod restarts, and pressure node memory when no effective container limit is configured. This issue is fixed in versions 1.9.14, 1.10.9, and 1.11.0-alpha.4.
From the CVE record · GitHub_M
The Terraform remote configuration loader follows repository-controlled symlinks when processing a ComponentDefinition. A user permitted to create or update ComponentDefinition objects can point a Terraform file to /dev/zero, causing an unbounded read that can exhaust memory and restart the vela-core controller.
Operators running Go package github.com/oam-dev/kubevela before 1.9.14, from 1.10.0-alpha.1 to before 1.10.9, or from 1.11.0-alpha.1 to before 1.11.0-alpha.4 should check their deployments.