Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

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

Quick assessment

Affected
kubeedge kubeedge
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

KubeEdge是KubeEdge开源的一个 Kubernetes 原生边缘计算框架。基于 Kubernetes 构建，并将本机容器化应用编排和设备管理扩展到边缘主机。 KubeEdge 1.11.1之前版本、1.10.2之前版本 和 1.9.4之前版本存在安全漏洞，该漏洞源于Cloud Stream 服务器和 Edge Stream 服务器将整条消息读入内存，而不限制此消息的大小，攻击者利用该漏洞可以发送大消息来耗尽内存并导致 DoS。

CVSS 4.4 · Medium EPSS 0.67% · P49

Possible ATT&CK Techniques 1 AI

T1499 · Endpoint Denial of Service
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2022-31079

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
KubeEdge Cloud Stream and Edge Stream DoS from large stream message
Source: CVE Program / CVE List V5
Vulnerability 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`.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
未加控制的资源消耗(资源穷尽)
Source: CVE Program / CVE List V5
Vulnerability Title
KubeEdge 资源管理错误漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
KubeEdge是KubeEdge开源的一个 Kubernetes 原生边缘计算框架。基于 Kubernetes 构建，并将本机容器化应用编排和设备管理扩展到边缘主机。 KubeEdge 1.11.1之前版本、1.10.2之前版本 和 1.9.4之前版本存在安全漏洞，该漏洞源于Cloud Stream 服务器和 Edge Stream 服务器将整条消息读入内存，而不限制此消息的大小，攻击者利用该漏洞可以发送大消息来耗尽内存并导致 DoS。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
kubeedge kubeedge = 1.11.0 -

II. Public POCs for CVE-2022-31079

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2022-31079

请登录查看更多情报信息。

Vendor Advisories for CVE-2022-31079 (1)

Same Patch Batch · kubeedge · 2022-07-11 · 6 CVEs total

CVE-2022-31073 6.5 MEDIUM KubeEdge Edge ServiceBus module DoS
CVE-2022-31075 4.9 MEDIUM KubeEdge DoS when signing the CSR from EdgeCore
CVE-2022-31074 4.5 MEDIUM KubeEdge Cloud AdmissionController component DoS
CVE-2022-31078 4.4 MEDIUM KubeEdge CloudCore Router memory exhaustion
CVE-2022-31080 4.4 MEDIUM KubeEdge Websocket Client in package Viaduct: DoS from large response message

IV. Related Vulnerabilities

Same product: kubeedge
Same vendor: kubeedge
Same weakness: CWE-400

V. Comments for CVE-2022-31079

No comments yet

Leave a comment