NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.70% (FIRST EPSS); higher than 53.1% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: github.com/kubeedge/kubeedge (Go) 1.10.2, 1.11.1, 1.9.4.
Severity is disputed: the assigning authority (CNA) scores it 4.4, NVD 6.5.

Low priority for now. Upgrade to github.com/kubeedge/kubeedge (Go) 1.10.2, 1.11.1, 1.9.4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

MediumCVSS 6.5 · v3.1—No exploit Fix available

Denial of service

Published: Jul 11, 2022
Updated: Jun 17, 2026
EPSS: 0.7% · 53th percentile
CWE: CWE-400

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.7%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 6.5
CNA · GitHub_M: 4.4; 2.1 point gap

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linuxfoundation	kubeedge	cpe:2.3:a:linuxfoundation:kubeedge

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linuxfoundation kubeedgebefore 1.9.4
linuxfoundation kubeedge1.10.0 and later · before 1.10.2
linuxfoundation kubeedge1.11.0 and later · before 1.11.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

kubeedge kubeedge
- = 1.11.0, >= 1.10.0, < 1.10.2, < 1.9.4affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	github.com/kubeedge/kubeedge	from 1.10.0 · before 1.10.2	1.10.2
Go	github.com/kubeedge/kubeedge	from 1.11.0 · before 1.11.1	1.11.1
Go	github.com/kubeedge/kubeedge	before 1.9.4	1.9.4

Same product

linuxfoundation: all records

Other highest-scoring records for the same primary product.

CVE-2022-31073KubeEdge Edge ServiceBus module DoS
31Monitor
CVE-2022-31080KubeEdge Websocket Client in package Viaduct: DoS from large response message
26Monitor
CVE-2022-31078KubeEdge CloudCore Router memory exhaustion
26Monitor

Published before and after this one in the same product

← EarlierCVE-2022-31077Jun 27, 2022 · Malicious response from KubeEdge can crash CSI Driver controller server
22Monitor
← EarlierCVE-2022-31074Jul 11, 2022 · KubeEdge Cloud AdmissionController component DoS
26Monitor
← EarlierCVE-2022-31075Jul 11, 2022 · KubeEdge DoS when signing the CSR from EdgeCore
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Go:github.com/kubeedge/kubeedge	1.10.2	Package registry (OSV)
Go:github.com/kubeedge/kubeedge	1.11.1	Package registry (OSV)
Go:github.com/kubeedge/kubeedge	1.9.4	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1function expand(node) {
2  return node.children.map(expand);
3}

Fixed

1const MAX_DEPTH = 32;
2function expand(node, depth = 0) {
3  if (depth > MAX_DEPTH) throw new Error("too deep");
4  return node.children.map((c) => expand(c, depth + 1));
5}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Endpoint Denial of ServiceT1499

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

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

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records