CVE-2022-31073

KubeEdge Edge ServiceBus module DoS

HIGH
7.5
CVSS Score
Published: July 11, 2022 at 08:05 PM UTC
Updated: June 17, 2026 at 04:44 AM UTC
2 products affected across 2 vendorsKubeedgeKubeedge

Using kubeedge by kubeedge?

Get instant alerts when new vulnerabilities affect kubeedge - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 2%
SSVC
PoC

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 1.9.41.10.0 ≤ v < 1.10.21.11.0 ≤ v < 1.11.1
Affected range stops below 1.10.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.11.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.9.4, so it looks safe — our inference, not a vendor statement
v < 1.10.2v < 1.9.4= 1.11.0
Affected range stops below 1.10.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.9.4, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (4)

x_refsource_MISCIssue TrackingPatchThird Party Advisory
https://github.com/kubeedge/kubeedge/pull/4038
x_refsource_MISCIssue TrackingPatchThird Party Advisory
https://github.com/kubeedge/kubeedge/pull/4039
x_refsource_MISCIssue TrackingPatchThird Party Advisory
https://github.com/kubeedge/kubeedge/pull/4042

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-400

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card