CyberRota Analysis
AI-GeneratedThe vulnerability affects KubeVela versions prior to 1.9.14, 1.10.0-alpha.1 to 1.10.9, and 1.11.0-alpha.1 to 1.11.0-alpha.4, allowing users with permission to create or update ComponentDefinition objects to exploit symlink manipulation in Terraform configurations. This can lead to excessive memory consumption, resulting in out-of-memory (OOM) conditions that may crash the vela-core controller and cause repeated Pod restarts. Organizations using affected versions should prioritize upgrading to the fixed releases to mitigate the risk of service disruption.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
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.