Skip to content

Terraform code injection may be possible when Terraformer is used for infrastructure provisioning

Critical
kon-angelo published GHSA-227x-7mh8-3cf6 Sep 25, 2025

Package

gomod github.com/gardener/gardener-extension-provider-aws (Go)

Affected versions

< v1.64.0

Patched versions

>= v1.64.0
gomod github.com/gardener/gardener-extension-provider-azure (Go)
< v1.55.0
>= v1.55.0
gomod github.com/gardener/gardener-extension-provider-gcp (Go)
< v1.46.0
>= v1.46.0
gomod github.com/gardener/gardener-extension-provider-openstack (Go)
< v1.49.0
>= v1.49.0

Description

Impact

A security vulnerability was discovered in Gardener when Terraformer is used for infrastructure provisioning. This vulnerability could allow a user with administrative privileges for a Gardener project to obtain control over the seed cluster where the shoot cluster is managed.

This issue has been rated Critical https://www.first.org/cvss/calculator/3-0#CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (Base score: 9.9).

This CVE affects all Gardener installations where Terraformer is used/can be enabled for infrastructure provisioning with any of the affected components mentioned below.

Affected Components

• gardener-extension-provider-gcp
• gardener-extension-provider-azure
• gardener-extension-provider-openstack
• gardener-extension-provider-aws

Affected Versions

• gardener-extension-provider-gcp < v1.46.0
• gardener-extension-provider-azure < v1.55.0
• gardener-extension-provider-openstack < v1.49.0
• gardener-extension-provider-aws < v1.64.0

Fixed versions

• gardener-extension-provider-gcp >= v1.46.0
• gardener-extension-provider-azure >= v1.55.0
• gardener-extension-provider-openstack >= v1.49.0
• gardener-extension-provider-aws >= v1.64.0

How do I mitigate this vulnerability?

Update to a fixed version.

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

CVE ID

CVE-2025-59823

Weaknesses

No CWEs

Credits