Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2022-31078: CWE-400: Uncontrolled Resource Consumption in kubeedge kubeedge

0
Medium
Published: Mon Jul 11 2022 (07/11/2022, 20:25:09 UTC)
Source: CVE
Vendor/Project: kubeedge
Product: kubeedge

Description

KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. Prior to versions 1.11.1, 1.10.2, and 1.9.4, the CloudCore Router does not impose a limit on the size of responses to requests made by the REST handler. An attacker could use this weakness to make a request that will return an HTTP response with a large body and cause DoS of CloudCore. In the HTTP Handler API, the rest handler makes a request to a pre-specified handle. The handle will return an HTTP response that is then read into memory. The consequence of the exhaustion is that CloudCore will be in a denial of service. Only an authenticated user of the cloud can make an attack. It will be affected only when users enable `router` module in the config file `cloudcore.yaml`. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. As a workaround, disable the router switch in the config file `cloudcore.yaml`.

AI-Powered Analysis

AILast updated: 06/23/2025, 03:50:22 UTC

Technical Analysis

CVE-2022-31078 is a medium-severity vulnerability affecting KubeEdge, an open-source platform designed to extend containerized application orchestration to edge hosts. The vulnerability arises from an uncontrolled resource consumption issue (CWE-400) in the CloudCore component's Router module. Specifically, prior to versions 1.11.1, 1.10.2, and 1.9.4, the CloudCore Router's REST handler does not impose limits on the size of HTTP response bodies returned from requests to predefined handlers. When an authenticated user sends a request that triggers a large HTTP response, the response is read fully into memory without size restrictions, potentially exhausting system resources. This exhaustion can lead to a denial of service (DoS) condition, rendering CloudCore unresponsive or crashing it. The vulnerability requires that the attacker be an authenticated cloud user and that the Router module be enabled in the cloudcore.yaml configuration file. The issue has been fixed in the specified patched versions, and a temporary mitigation involves disabling the Router module. No known exploits have been reported in the wild to date. The vulnerability affects KubeEdge versions prior to 1.9.4, versions from 1.10.0 up to but not including 1.10.2, and version 1.11.0. This vulnerability is significant because CloudCore is central to KubeEdge's orchestration and management of edge nodes, and a DoS here can disrupt edge computing operations and services dependent on KubeEdge infrastructure.

Potential Impact

For European organizations leveraging KubeEdge to manage edge computing environments, this vulnerability poses a risk of service disruption through denial of service attacks. Since CloudCore orchestrates containerized applications at the edge, a successful exploitation could interrupt critical edge services such as IoT data processing, real-time analytics, and localized application delivery. This disruption could affect sectors reliant on edge computing, including manufacturing, smart cities, healthcare, and telecommunications. The requirement for authenticated access limits the attack surface to insiders or compromised accounts, but insider threats or credential theft could enable exploitation. The lack of response size limits means that even a single malicious request can consume excessive memory, potentially cascading into broader service outages. Given the increasing adoption of edge computing in Europe to support latency-sensitive and data privacy-compliant applications, such disruptions could lead to operational downtime, financial losses, and reputational damage. Additionally, organizations that have enabled the Router module without applying patches or mitigations remain vulnerable. However, the absence of known exploits in the wild and the medium severity rating suggest that while impactful, the threat is currently manageable with proper controls.

Mitigation Recommendations

European organizations should prioritize upgrading KubeEdge to versions 1.11.1, 1.10.2, or 1.9.4 or later, where the vulnerability has been addressed. Until upgrades can be applied, disabling the Router module in the cloudcore.yaml configuration file is an effective workaround to prevent exploitation. Organizations should audit their KubeEdge deployments to verify whether the Router module is enabled and restrict access to authenticated users with the least privilege principle to reduce the risk of insider threats. Implementing robust authentication mechanisms, such as multi-factor authentication (MFA), can further mitigate risks associated with credential compromise. Monitoring CloudCore logs for unusual or large response requests can help detect attempted exploitation. Network segmentation and strict access controls should be enforced to limit exposure of the CloudCore API endpoints. Additionally, organizations should incorporate this vulnerability into their incident response plans and conduct regular security assessments of their edge computing infrastructure. Finally, maintaining up-to-date software and subscribing to vendor security advisories will ensure timely awareness of patches and emerging threats.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2022-05-18T00:00:00.000Z
Cisa Enriched
true

Threat ID: 682d9844c4522896dcbf3621

Added to database: 5/21/2025, 9:09:24 AM

Last enriched: 6/23/2025, 3:50:22 AM

Last updated: 2/6/2026, 8:06:04 PM

Views: 49

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats