LiveActive security incident?Get immediate response
CVE Record

CVE-2022-31080: KubeEdge Websocket Client in package Viaduct: DoS from large response message

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, a large response received by the viaduct WSClient can cause a DoS from memory exhaustion. The entire body of the response is being read into memory which could allow an attacker to send a request that returns a response with a large body. The consequence of the exhaustion is that the process which invokes a WSClient will be in a denial of service. The software is affected If users who are authenticated to the edge side connect to `cloudhub` from the edge side through WebSocket protocol. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. There are currently no known workarounds.

MediumCVSS 4.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-31080 can let a highly privileged, authenticated edge-side user crash a KubeEdge process by causing the WebSocket client to read an overly large response into memory. The business impact is service disruption, not data theft or tampering, based on the provided sources.

Executive priority

Treat as a targeted availability risk. Schedule remediation for affected KubeEdge environments, especially operational edge deployments, but it does not appear to warrant emergency response absent exposure or exploitation evidence.

Technical view

KubeEdge viaduct WSClient reads an entire response body into memory. In affected versions, a large response can exhaust memory and deny service to the process invoking WSClient. The issue is CWE-400 and affects specific KubeEdge releases before 1.11.1, 1.10.2, and 1.9.4.

Likely exposure

Exposure is likely limited to KubeEdge deployments running affected versions where authenticated edge-side users connect to cloudhub through the WebSocket protocol.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. CVSS indicates network access, high attack complexity, high privileges, no user interaction, and high availability impact.

Researcher notes

Affected version data is precise, but exploitation evidence is limited in the supplied sources. The key validation question is whether the vulnerable viaduct WSClient path is reachable by authenticated edge-side users over WebSocket.

Mitigation direction

  • Upgrade KubeEdge to 1.11.1, 1.10.2, 1.9.4, or later.
  • Prioritize systems using edge-side WebSocket connections to cloudhub.
  • Review KubeEdge vendor guidance because sources state no known workarounds.
  • Limit authenticated edge-side access where operationally possible until upgraded.

Validation and detection

  • Inventory deployed KubeEdge versions across cloud and edge components.
  • Confirm whether edge-side users connect to cloudhub through WebSocket.
  • Check process restart, memory exhaustion, and availability logs around cloudhub WebSocket activity.
  • Verify upgraded environments report fixed KubeEdge versions.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2022-31080 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

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

ScoreVersionSeverityVectorExploitImpactSource
4.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H0.73.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.4Medium
CVSS 3.1 vector shape for CVE-2022-31080Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
kubeedgekubeedge= 1.11.0, >= 1.10.0, < 1.10.2, < 1.9.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.