Security readout for executives and security teams
Plain-English summary
CVE-2022-31079 can let an authenticated KubeEdge user crash CloudCore or EdgeCore by causing stream components to consume excessive memory. Business impact is availability, not data theft. Exposure is limited to vulnerable KubeEdge versions with both cloudStream and edgeStream enabled, but affected edge orchestration services may be disrupted.
Executive priority
Prioritize remediation for production KubeEdge environments that rely on CloudCore and EdgeCore availability, especially edge sites with limited operational redundancy. This is not currently evidenced as actively exploited, but a successful attack can interrupt orchestration services.
Technical view
KubeEdge Cloud Stream and Edge Stream read an entire stream message into memory without a size limit, causing CWE-400 uncontrolled resource consumption. A network attacker with high privileges can trigger memory exhaustion and denial of service against CloudCore and EdgeCore when the relevant stream modules are enabled.
Likely exposure
Likely exposure is KubeEdge 1.11.0, 1.10.0 through before 1.10.2, and versions before 1.9.4 where cloudStream and edgeStream are enabled. Systems without those modules enabled are not described as affected.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The advisory states only an authenticated user can cause the issue by sending a large stream message, with high attack complexity and high privileges required.
Researcher notes
The affected condition is configuration-dependent and privilege-gated. Validate version and module state before rating internal exposure. The source bundle names fixed versions and the disable-module workaround, but does not provide independent exploit telemetry or additional mitigations.
Mitigation direction
- Upgrade KubeEdge to 1.11.1, 1.10.2, 1.9.4, or later supported releases.
- If upgrade is delayed, disable cloudStream in cloudcore.yaml.
- If upgrade is delayed, disable edgeStream in edgecore.yaml.
- Review vendor guidance before changing production edge orchestration behavior.
- Restrict authenticated access to KubeEdge stream capabilities where operationally possible.
Validation and detection
- Inventory KubeEdge versions across CloudCore and EdgeCore deployments.
- Check cloudcore.yaml for whether cloudStream is enabled.
- Check edgecore.yaml for whether edgeStream is enabled.
- Confirm upgraded components report fixed KubeEdge versions.
- Review monitoring for CloudCore or EdgeCore memory exhaustion and restarts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-31079 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H0.73.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.4MediumVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/kubeedge/kubeedge/security/advisories/GHSA-wrcr-x4qj-j543CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.