LiveActive security incident?Get immediate response
CVE Record

CVE-2022-31073: KubeEdge Edge ServiceBus module DoS

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 ServiceBus server on the edge side may be susceptible to a DoS attack if an HTTP request containing a very large Body is sent to it. It is possible for the node to be exhausted of memory. The consequence of the exhaustion is that other services on the node, e.g. other containers, will be unable to allocate memory and thus causing a denial of service. Malicious apps accidentally pulled by users on the host and have the access to send HTTP requests to localhost may make an attack. It will be affected only when users enable the `ServiceBus` 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 the `ServiceBus` module in the config file `edgecore.yaml`.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a denial-of-service issue in KubeEdge edge nodes. If the optional ServiceBus module is enabled, an actor able to send HTTP requests to the edge-side service could exhaust node memory. That can disrupt other containers on the same node. Fixed KubeEdge releases are available.

Executive priority

Treat this as a targeted availability risk for edge environments, not a broad remote compromise. Prioritize remediation where edge nodes run untrusted workloads, support critical operations, or have ServiceBus enabled.

Technical view

Before KubeEdge 1.11.1, 1.10.2, and 1.9.4, the edge-side ServiceBus server could consume excessive memory when processing an oversized HTTP request body. The issue is CWE-400 uncontrolled resource consumption, affects availability only, and applies only when ServiceBus is enabled in edgecore.yaml.

Likely exposure

Exposure is limited to KubeEdge deployments running affected versions with the ServiceBus module enabled. The advisory specifically notes risk from malicious apps on the host that can send HTTP requests to localhost.

Exploitation context

The source bundle does not show KEV listing or confirmed active exploitation. Practical exploitation requires network or local request access to the edge-side ServiceBus path and enough request volume or size to exhaust node memory.

Researcher notes

CVSS is 6.5 with availability impact only. Affected ranges are <1.9.4, 1.10.0 to <1.10.2, and 1.11.0. The provided sources do not describe confidentiality or integrity impact, public exploitation, or affected products beyond KubeEdge.

Mitigation direction

  • Upgrade KubeEdge to 1.11.1, 1.10.2, 1.9.4, or a later fixed release.
  • Disable the ServiceBus module in edgecore.yaml if it is not required.
  • Prioritize edge nodes where untrusted applications can run on the host.
  • Check the KubeEdge advisory for any deployment-specific guidance before changing production clusters.

Validation and detection

  • Inventory KubeEdge versions across edge nodes.
  • Check edgecore.yaml for ServiceBus module enablement.
  • Identify workloads or host apps able to reach localhost services on edge nodes.
  • Monitor affected nodes for memory pressure and service disruption indicators.
  • Confirm upgraded nodes report fixed KubeEdge versions after remediation.
Prepared
Confidence
high
Sources
6

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-31073 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
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/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
5Source 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
6.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:A/AC:L/PR:N/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.9.4, >= 1.10.0, < 1.10.2, = 1.11.0Listed
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.