Skip to content

Gardener allows bypassing project secret validation which can lead to privilege escalation

Critical severity GitHub Reviewed Published May 19, 2025 in gardener/gardener • Updated May 19, 2025

Package

gomod github.com/gardener/gardener (Go)

Affected versions

< 1.116.4
>= 1.117.0, < 1.117.5
>= 1.118.0, < 1.118.2

Patched versions

1.116.4
1.117.5
1.118.2

Description

A security vulnerability was discovered in Gardener that could allow a user with administrative privileges for a Gardener project to obtain control over the seed cluster(s) where their shoot clusters are managed.

Am I Vulnerable?

This CVE affects all Gardener installations no matter of the public cloud provider(s) used for the seed clusters/shoot clusters.

Affected Components

  • gardener/gardener

Affected Versions

  • < v1.116.4
  • < v1.117.5
  • < v1.118.2
  • < v1.119.0

Fixed Versions

  • >= v1.116.4
  • >= v1.117.5
  • >= v1.118.2
  • >= v1.119.0

How do I mitigate this vulnerability?

Update to a fixed version.

References

@rfranzke rfranzke published to gardener/gardener May 19, 2025
Published to the GitHub Advisory Database May 19, 2025
Reviewed May 19, 2025
Published by the National Vulnerability Database May 19, 2025
Last updated May 19, 2025

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

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(30th percentile)

Weaknesses

CVE ID

CVE-2025-47283

GHSA ID

GHSA-3hw7-qj9h-r835

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.