Cloudanix VulnDB

CVE-2024-0793

High · 7.7

CVSS

7.7

EPSS

0.6%

Published

Nov 17, 2024

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A configuration handling problem in container management software can make its core components keep restarting when certain scaling setup files are first used, causing operational interruptions.

Exploitation
Remote Authenticated
Attacker needs
Low Privilege
Complexity
Low
Impact
Denial Of Service
Component
Application
Class
Denial of service
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

The flaw causes denial of service when an HPA config YAML lacking a .spec.behavior.scaleUp block is initially applied, leading to kube-controller-manager pods entering restart churn.

Why it matters to the business

This can result in instability and downtime for Kubernetes cluster management, affecting application scaling and availability. Low urgency as the issue is not known to be exploited in ransomware or KEV-listed campaigns and has shown no EPSS increase over 30 days.

How an attack unfolds

An attacker or misconfigured deployment applies an HPA YAML lacking the scaleUp behavior block to a cluster, triggering the controller manager to enter a restart loop and denying service to dependent workloads. Mentioned threat actor context around HTTP/2 Rapid Reset is unrelated to this flaw.

How to fix it

Upgrade affected kube-controller-manager deployments to versions that properly handle missing scaleUp blocks in initial HPA application. No fixed versions listed for the described component; bind9 entries appear unrelated to this CVE.

How to confirm the fix worked

Apply test HPA configurations both with and without the scaleUp block, confirm kube-controller-manager pods remain stable without churn, and review pod restart metrics and logs post-upgrade.

Typical attack path

  1. Locate or craft an HPA configuration missing the .spec.behavior.scaleUp block
  2. Apply the malformed configuration via the Kubernetes API
  3. Observe repeated restarts of kube-controller-manager pods

How to detect it

Review kube-controller-manager pod logs and restart counts for patterns following HPA application events; inspect recently applied HPA YAML resources for absence of scaleUp behavior sections. No threat actor specific indicators apply.

What your security team should do

  • Prioritize patching kube-controller-manager in all clusters
  • Audit existing HPA manifests for missing behavior blocks
  • Implement configuration validation in CI pipelines before applying HPA resources
  • Monitor cluster health dashboards for controller pod restart rates

The record

A flaw was found in kube-controller-manager. This issue occurs when the initial application of a HPA config YAML lacking a .spec.behavior.scaleUp block causes a denial of service due to KCM pods going into restart churn.

Affected packages

Ecosystem Package Introduced Fixed
Go k8s.io/kubernetes 0 1.27.0-alpha.1
Chainguard argocd-image-updater 0 0.17.0-r1
Chainguard argocd-image-updater-compat 0 0.17.0-r1
Chainguard argocd-image-updater-fips 0 0.17.0-r2
Chainguard aws-efs-csi-driver 0 2.1.1-r0
Chainguard aws-efs-csi-driver-fips 0 2.1.1-r0
Red Hat:openshift:4.12::el8 openshift 0 0:4.12.0-202403042037.p0.g9946c63.assembly.stream.el8
Red Hat:openshift:4.12::el8 openshift-hyperkube 0 0:4.12.0-202403042037.p0.g9946c63.assembly.stream.el8
Red Hat:openshift:4.12::el9 openshift 0 0:4.12.0-202403042037.p0.g9946c63.assembly.stream.el9
Red Hat:openshift:4.12::el9 openshift-hyperkube 0 0:4.12.0-202403042037.p0.g9946c63.assembly.stream.el9
SUSE:Enterprise Storage 7.1 kubernetes1.23 0 1.23.17-150300.7.12.1
SUSE:Enterprise Storage 7.1 kubernetes1.24 0 1.24.17-150300.7.6.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS kubernetes1.23 0 1.23.17-150300.7.12.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS kubernetes1.24 0 1.24.17-150300.7.6.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS kubernetes1.23 0 1.23.17-150300.7.12.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS kubernetes1.24 0 1.24.17-150400.9.16.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS kubernetes1.23 0 1.23.17-150300.7.12.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS kubernetes1.24 0 1.24.17-150400.9.16.1
SUSE:Linux Enterprise Module for Containers 15 SP5 kubernetes1.23 0 1.23.17-150500.3.9.1
SUSE:Linux Enterprise Module for Containers 15 SP5 kubernetes1.24 0 1.24.17-150500.3.13.1
SUSE:Linux Enterprise Module for Containers 15 SP5 kubernetes1.25 0 1.25.16-150400.9.6.1
SUSE:Linux Enterprise Module for Containers 15 SP5 kubernetes1.26 0 1.26.14-150400.9.6.1
SUSE:Linux Enterprise Module for Containers 15 SP6 kubernetes1.26 0 1.26.14-150400.9.6.1
SUSE:Linux Enterprise Server 15 SP3-LTSS kubernetes1.23 0 1.23.17-150300.7.12.1
SUSE:Linux Enterprise Server 15 SP3-LTSS kubernetes1.24 0 1.24.17-150300.7.6.1
SUSE:Linux Enterprise Server 15 SP4-LTSS kubernetes1.23 0 1.23.17-150300.7.12.1
SUSE:Linux Enterprise Server 15 SP4-LTSS kubernetes1.24 0 1.24.17-150400.9.16.1
SUSE:Linux Enterprise Server for SAP Applications 15 SP3 kubernetes1.23 0 1.23.17-150300.7.12.1
SUSE:Linux Enterprise Server for SAP Applications 15 SP3 kubernetes1.24 0 1.24.17-150300.7.6.1
SUSE:Linux Enterprise Server for SAP Applications 15 SP4 kubernetes1.23 0 1.23.17-150300.7.12.1
SUSE:Linux Enterprise Server for SAP Applications 15 SP4 kubernetes1.24 0 1.24.17-150400.9.16.1
Wolfi argocd-image-updater 0 0.17.0-r1
Wolfi argocd-image-updater-compat 0 0.17.0-r1
Wolfi aws-efs-csi-driver 0 2.1.1-r0
openSUSE:Leap 15.5 kubernetes1.23 0 1.23.17-150500.3.9.1
openSUSE:Leap 15.5 kubernetes1.24 0 1.24.17-150500.3.13.1
openSUSE:Leap 15.5 kubernetes1.25 0 1.25.16-150400.9.6.1
openSUSE:Leap 15.5 kubernetes1.26 0 1.26.14-150400.9.6.1
openSUSE:Tumbleweed govulncheck-vulndb 0 0.0.20241119T173509-1.1
openSUSE:Tumbleweed kubernetes1.26 0 1.26.14-1.1

Related vulnerabilities