CVE-2022-31075

KubeEdge DoS when signing the CSR from EdgeCore

EdgeCore may be susceptible to a DoS attack on CloudHub if an attacker was to send a well-crafted HTTP request to /edge.crt.
If an attacker can send a well-crafted HTTP request to CloudHub, and that request has a very large body, that request could crash the HTTP service through a memory exhaustion vector. The request body is being read into memory, and a body that was larger than the available memory could lead to a successful attack.
Because the request would have to make it through authorization, only authorized users could perform this attack. The consequence of the exhaustion is that CloudHub will be in denial of service. It will be affected only when users enable the CloudHub module in the file cloudcore.yaml as below:

modules:
  ...
  cloudHub:
    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-31075 has a CVSS score of 4.9 (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-31075? CVE-2022-31075 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-31075? CVE-2022-31075 has a CVSS score of 4.9 (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-31075? github.com/kubeedge/kubeedge (go) versions >= 1.11.0, < 1.11.1 is affected.
4. Is there a fix for CVE-2022-31075? Yes. CVE-2022-31075 is fixed in 1.11.1, 1.10.2, 1.9.4. Upgrade to this version or later.
5. Is CVE-2022-31075 exploitable, and should I be worried? Whether CVE-2022-31075 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-31075 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-31075?
   • 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