CVE-2022-31076 Malicious Message can crash CloudCore in KubeEdge

Medium 4.2 Published Updated

An authenticated local attacker can crash CloudCore via a nil-pointer dereference in the UDS Server when the unixsocket switch is enabled.

Exploited in the wild
Not known
Login needed
An administrator
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2022-31076?

CVE-2022-31076 is a medium-severity vulnerability in kubeedge, published on 27 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

KubeEdge is built upon Kubernetes and extends native containerized application orchestration and device management to hosts at the Edge. In affected versions a malicious message can crash CloudCore by triggering a nil-pointer dereference in the UDS Server. Since the UDS Server only communicates with the CSI Driver on the cloud side, the attack is limited to the local host network. As such, an attacker would already need to be an authenticated user of the Cloud. Additionally it will be affected only when users turn on the unixsocket switch in the config file cloudcore.yaml. 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. Users unable to upgrade should sisable the unixsocket switch of CloudHub in the config file cloudcore.yaml.

Weakness: CWE-476

Which versions are affected by CVE-2022-31076?

5 open source packages ship an affected version, including github.com/kubeedge/kubeedge. It affects 1 product.

PackageAffectedFixed in
github.com/kubeedge/kubeedge GoAll versions1.9.3, 1.10.1
github.com/kubeedge/kubeedge GoAll versions1.9.3
github.com/kubeedge/kubeedge GoAll versions1.9.3
github.com/kubeedge/kubeedge GoFrom 1.10.01.10.1
github.com/kubeedge/kubeedge GoFrom 1.10.01.10.1

Products include Linuxfoundation Kubeedge.

How do I fix CVE-2022-31076?

Upgrade github.com/kubeedge/kubeedge to a fixed version for your release line: 1.9.3 or 1.10.1.

Is CVE-2022-31076 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31076 exists.

Sources

Also known as GHSA-8f4f-v9x5-cg6j, GO-2022-0500.

Is CVE-2022-31076 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free