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

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

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jun 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-8f4f-v9x5-cg6j, GO-2022-0500

## 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 (NULL Pointer Dereference)

## 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.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kubeedge/kubeedge` | Go | All versions | 1.9.3, 1.10.1 |
| `github.com/kubeedge/kubeedge` | Go | All versions | 1.9.3 |
| `github.com/kubeedge/kubeedge` | Go | All versions | 1.9.3 |
| `github.com/kubeedge/kubeedge` | Go | From 1.10.0 | 1.10.1 |
| `github.com/kubeedge/kubeedge` | Go | From 1.10.0 | 1.10.1 |

Products: 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.

## Other vulnerabilities in kubeedge

- [CVE-2022-31073](https://insights.sbomify.com/CVE-2022-31073/): KubeEdge Edge ServiceBus module DoS (medium 6.5)
- [CVE-2022-31075](https://insights.sbomify.com/CVE-2022-31075/): KubeEdge DoS when signing the CSR from EdgeCore (medium 4.9)
- [CVE-2022-31074](https://insights.sbomify.com/CVE-2022-31074/): KubeEdge Cloud AdmissionController component DoS (medium 4.5)
- [CVE-2022-31078](https://insights.sbomify.com/CVE-2022-31078/): KubeEdge CloudCore Router memory exhaustion (medium 4.4)
- [CVE-2022-31079](https://insights.sbomify.com/CVE-2022-31079/): KubeEdge Cloud Stream and Edge Stream DoS from large stream message (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31076 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31076 exists.

Affected packages and fixed versions:
- github.com/kubeedge/kubeedge (Go): affected all versions; fixed in 1.9.3, 1.10.1
- github.com/kubeedge/kubeedge (Go): affected all versions; fixed in 1.9.3
- github.com/kubeedge/kubeedge (Go): affected all versions; fixed in 1.9.3
- github.com/kubeedge/kubeedge (Go): affected from 1.10.0; fixed in 1.10.1
- github.com/kubeedge/kubeedge (Go): affected from 1.10.0; fixed in 1.10.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-31076/ (Markdown: https://insights.sbomify.com/CVE-2022-31076/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-31076
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-31076
- OSV: https://osv.dev/vulnerability/CVE-2022-31076

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-31076/
Summaries are generated and may contain mistakes; the official description above is the record.