# CVE-2024-0793: Kube-controller-manager: malformed hpa v1 manifest causes crash > A malformed HPA manifest causes kube-controller-manager to crash, leading to denial of service in Kubernetes clusters. - **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 Nov 2024 - **Updated:** 17 Nov 2024 - **Also known as:** GHSA-h7wq-jj8r-qm7p, GO-2024-3277, RHSA-2024:1267, SUSE-SU-2024:1163-1, SUSE-SU-2024:1164-1, SUSE-SU-2024:1165-1, SUSE-SU-2024:1166-1, SUSE-SU-2024:1166-2, openSUSE-SU-2024:13715-1, openSUSE-SU-2024:13716-1, openSUSE-SU-2024:13717-1, openSUSE-SU-2024:13718-1 ## What is CVE-2024-0793? CVE-2024-0793 is a high-severity denial of service vulnerability in Red Hat OpenShift Container Platform 4, published on 17 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2024-0793? 3 open source packages ship an affected version, including k8s.io/kubernetes. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `k8s.io/kubernetes` | Go | All versions | 1.27.0-alpha.1 | | `k8s.io/kubernetes` | Go | All versions | 1.27.0-alpha.1 | | `k8s.io/kubernetes` | Go | All versions | 1.27.0-alpha.1 | | `openshift` | Red Hat:openshift:4.12::el8 | All versions | 0:4.12.0-202403042037.p0.g9946c63.assembly.stream.el8 | | `openshift-hyperkube` | Red Hat:openshift:4.12::el8 | All versions | 0:4.12.0-202403042037.p0.g9946c63.assembly.stream.el8 | | `openshift` | Red Hat:openshift:4.12::el9 | All versions | 0:4.12.0-202403042037.p0.g9946c63.assembly.stream.el9 | | `openshift-hyperkube` | Red Hat:openshift:4.12::el9 | All versions | 0:4.12.0-202403042037.p0.g9946c63.assembly.stream.el9 | | `kubernetes1.23` | SUSE:Linux Enterprise Module for Containers 15 SP5 | All versions | 1.23.17-150500.3.9.1 | | `kubernetes1.24` | SUSE:Linux Enterprise Module for Containers 15 SP5 | All versions | 1.24.17-150500.3.13.1 | | `kubernetes1.25` | SUSE:Linux Enterprise Module for Containers 15 SP5 | All versions | 1.25.16-150400.9.6.1 | | `kubernetes1.26` | SUSE:Linux Enterprise Module for Containers 15 SP5 | All versions | 1.26.14-150400.9.6.1 | | `kubernetes1.26` | SUSE:Linux Enterprise Module for Containers 15 SP6 | All versions | 1.26.14-150400.9.6.1 | | `kubernetes1.23` | openSUSE:Leap 15.5 | All versions | 1.23.17-150500.3.9.1 | | `kubernetes1.24` | openSUSE:Leap 15.5 | All versions | 1.24.17-150500.3.13.1 | | `kubernetes1.25` | openSUSE:Leap 15.5 | All versions | 1.25.16-150400.9.6.1 | | `kubernetes1.26` | openSUSE:Leap 15.5 | All versions | 1.26.14-150400.9.6.1 | | `kubernetes1.26` | openSUSE:Tumbleweed | All versions | 1.26.14-1.1 | ## How do I fix CVE-2024-0793? Upgrade k8s.io/kubernetes to 1.27.0-alpha.1 or later. ## Is CVE-2024-0793 being exploited? There is no known exploitation of CVE-2024-0793 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-0793 and fix it if it is affected. What it is: CVE-2024-0793 is a high-severity denial of service vulnerability in Red Hat OpenShift Container Platform 4, published on 17 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-0793 in the wild and no public exploit code. Affected packages and fixed versions: - k8s.io/kubernetes (Go): affected all versions; fixed in 1.27.0-alpha.1 - k8s.io/kubernetes (Go): affected all versions; fixed in 1.27.0-alpha.1 - k8s.io/kubernetes (Go): affected all versions; fixed in 1.27.0-alpha.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-0793/ (Markdown: https://insights.sbomify.com/CVE-2024-0793/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-0793 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-0793 - OSV: https://osv.dev/vulnerability/CVE-2024-0793 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-0793/ Summaries are generated and may contain mistakes; the official description above is the record.