CVE-2022-31078

KubeEdge CloudCore Router memory exhaustion vulnerability

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 as below.

modules:
  ...
  router:
    enable: true

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2022-31078 has a CVSS score of 4.4 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.11.1, 1.10.2, 1.9.4); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

This bug has been fixed in Kubeedge 1.11.1, 1.10.2, 1.9.4. Users should update to these versions to resolve the issue.

1. What is CVE-2022-31078? CVE-2022-31078 is a medium-severity uncontrolled resource consumption vulnerability in github.com/kubeedge/kubeedge (go), affecting versions >= 1.11.0, < 1.11.1. It is fixed in 1.11.1, 1.10.2, 1.9.4. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. How severe is CVE-2022-31078? CVE-2022-31078 has a CVSS score of 4.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/kubeedge/kubeedge are affected by CVE-2022-31078? github.com/kubeedge/kubeedge (go) versions >= 1.11.0, < 1.11.1 is affected.
4. Is there a fix for CVE-2022-31078? Yes. CVE-2022-31078 is fixed in 1.11.1, 1.10.2, 1.9.4. Upgrade to this version or later.
5. Is CVE-2022-31078 exploitable, and should I be worried? Whether CVE-2022-31078 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-31078 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-31078?
   • Upgrade github.com/kubeedge/kubeedge to 1.11.1 or later
   • Upgrade github.com/kubeedge/kubeedge to 1.10.2 or later
   • Upgrade github.com/kubeedge/kubeedge to 1.9.4 or later

Other vulnerabilities in github.com/kubeedge/kubeedge