CVE-2022-31080

DoS in KubeEdge's Websocket Client in package Viaduct

Workarounds

At the time of writing, no workaround exists.

References

NA

Credits

Thanks David Korczynski and Adam Korczynski of ADA Logics for responsibly disclosing this issue in accordance with the kubeedge security policy during a security audit sponsored by CNCF and facilitated by OSTIF.

For more information

If you have any questions or comments about this advisory:

• Open an issue in KubeEdge repo
• To make a vulnerability report, email your vulnerability to the private [email protected] list with the security details and the details expected for KubeEdge bug reports.

A large response received by the viaduct WSClient can cause a DoS from memory exhaustion. The entire body of the response is being read into memory which could allow an attacker to send a request that returns a response with a large body.
The consequence of the exhaustion is that the process which invokes a WSClient will be in a denial of service. It will be affected If users which are authenticated to the edge side and connect from the edge side to cloudhub through WebSocket protocol.

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

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