Skip to content

Helm Controller denial of service

High severity GitHub Reviewed Published Sep 7, 2022 in fluxcd/flux2 • Updated Jan 27, 2023

Package

gomod github.com/fluxcd/flux2 (Go)

Affected versions

>= 0.0.17, < 0.32.0

Patched versions

0.32.0
gomod github.com/fluxcd/helm-controller (Go)
>= 0.0.4, < 0.23.0
0.23.0

Description

Helm controller is tightly integrated with the Helm SDK. A vulnerability found in the Helm SDK allows for specific data inputs to cause high memory consumption, which in some platforms could cause the controller to panic and stop processing reconciliations.

Impact

In a shared cluster multi-tenancy environment, a tenant could create a HelmRelease that makes the controller panic, denying all other tenants from their Helm releases being reconciled.

Credits

The initial crash bug was reported by oss-fuzz. The Flux Security team produced the first exploit and worked together with the Helm Security team to ensure that both projects were patched timely.

For more information

If you have any questions or comments about this advisory:

  • Open an issue in any of the affected repositories.
  • Contact us at the CNCF Flux Channel.

References

References

@hiddeco hiddeco published to fluxcd/flux2 Sep 7, 2022
Published by the National Vulnerability Database Sep 7, 2022
Published to the GitHub Advisory Database Sep 16, 2022
Reviewed Sep 16, 2022
Last updated Jan 27, 2023

Severity

High

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
None
Integrity
None
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.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

EPSS score

0.142%
(50th percentile)

Weaknesses

CVE ID

CVE-2022-36049

GHSA ID

GHSA-p2g7-xwvr-rrw3

Source code

Credits

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