What is CVE-2022-31077?

CVE-2022-31077 is a medium-severity null pointer dereference vulnerability in github.com/kubeedge/kubeedge (go), affecting versions = 1.10.0. It is fixed in 1.10.1, 1.9.3. The application dereferences a null pointer, causing a crash.

How severe is CVE-2022-31077?

CVE-2022-31077 has a CVSS score of 4.0 (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.

Which versions of github.com/kubeedge/kubeedge are affected by CVE-2022-31077?

github.com/kubeedge/kubeedge (go) versions = 1.10.0 is affected.

Is there a fix for CVE-2022-31077?

Yes. CVE-2022-31077 is fixed in 1.10.1, 1.9.3. Upgrade to this version or later.

Is CVE-2022-31077 exploitable, and should I be worried?

Whether CVE-2022-31077 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.

What actually determines whether CVE-2022-31077 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.

How do I fix CVE-2022-31077?

Upgrade: github.com/kubeedge/kubeedge to 1.10.1 or later, github.com/kubeedge/kubeedge to 1.9.3 or later.

CVE-2022-31077 in github.com/kubeedge/kubeedge

Summary

CloudCore CSI Driver: Malicious response from KubeEdge can crash CSI Driver controller server

Workarounds

At the time of writing, no workaround exists.

References

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.

Notes: This vulnerability was found by fuzzing KubeEdge by way of OSS-Fuzz.

Impact

A malicious message response from KubeEdge can crash the CSI Driver controller server by triggering a nil-pointer dereference panic. As a consequence, the CSI Driver controller will be in denial of service. An attacker would already need to be an authenticated user of the Cloud, and only when the authenticated user launches the csidriver then CloudCore may be attacked.

The application dereferences a null pointer, causing a crash. Typical impact: denial of service via crash.

CVE-2022-31077 has a CVSS score of 4.0 (Medium). The vector is reachable from an adjacent network, high privileges required, and user interaction required. 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.10.1, 1.9.3); upgrading removes the vulnerable code path.

Affected versions

github.com/kubeedge/kubeedge (= 1.10.0) github.com/kubeedge/kubeedge (< 1.9.3)

Security releases

github.com/kubeedge/kubeedge → 1.10.1 (go) github.com/kubeedge/kubeedge → 1.9.3 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

This bug has been fixed in Kubeedge 1.11.0, 1.10.1, and 1.9.3. Users should update to these versions to resolve the issue.

Frequently Asked Questions

What is CVE-2022-31077? CVE-2022-31077 is a medium-severity null pointer dereference vulnerability in github.com/kubeedge/kubeedge (go), affecting versions = 1.10.0. It is fixed in 1.10.1, 1.9.3. The application dereferences a null pointer, causing a crash.
How severe is CVE-2022-31077? CVE-2022-31077 has a CVSS score of 4.0 (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.
Which versions of github.com/kubeedge/kubeedge are affected by CVE-2022-31077? github.com/kubeedge/kubeedge (go) versions = 1.10.0 is affected.
Is there a fix for CVE-2022-31077? Yes. CVE-2022-31077 is fixed in 1.10.1, 1.9.3. Upgrade to this version or later.
Is CVE-2022-31077 exploitable, and should I be worried? Whether CVE-2022-31077 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
What actually determines whether CVE-2022-31077 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.
How do I fix CVE-2022-31077?
- Upgrade github.com/kubeedge/kubeedge to 1.10.1 or later
- Upgrade github.com/kubeedge/kubeedge to 1.9.3 or later

Other vulnerabilities in github.com/kubeedge/kubeedge

CVE-IDSeverityPackage summary

CVE-2022-31080Mediumgithub.com/kubeedge/kubeedge: DoS in KubeEdge's Websocket Client in package Viaduct CVE-2022-31079Mediumgithub.com/kubeedge/kubeedge: KubeEdge Cloud Stream and Edge Stream DoS from large stream message CVE-2022-31078Mediumgithub.com/kubeedge/kubeedge: KubeEdge CloudCore Router memory exhaustion vulnerability CVE-2022-31075Mediumgithub.com/kubeedge/kubeedge: KubeEdge DoS when signing the CSR from EdgeCore CVE-2022-31074Mediumgithub.com/kubeedge/kubeedge: KubeEdge Cloud AdmissionController component DoS