Skip to content

DoS in KubeEdge's Websocket Client in package Viaduct

Moderate severity GitHub Reviewed Published Jul 11, 2022 in kubeedge/kubeedge • Updated Jul 24, 2023

Package

gomod github.com/kubeedge/kubeedge (Go)

Affected versions

>= 1.11.0, < 1.11.1
>= 1.10.0, < 1.10.2
< 1.9.4

Patched versions

1.11.1
1.10.2
1.9.4

Description

Impact

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. It will be affected If users which are authenticated to the edge side and connect from the edge side to cloudhub through WebSocket protocol.

Patches

This bug has been fixed in Kubeedge 1.11.1, 1.10.2, 1.9.4. Users should update to these versions to resolve the issue.

Workarounds

At the time of writing, no workaround exists.

References

NA

Credits

Thanks David Korczynski and Adam Korczynski of ADA Logics for responsibly disclosing this issue in accordance with the kubeedge security policy during a security audit sponsored by CNCF and facilitated by OSTIF.

For more information

If you have any questions or comments about this advisory:

References

@kevin-wangzefeng kevin-wangzefeng published to kubeedge/kubeedge Jul 11, 2022
Published to the GitHub Advisory Database Jul 11, 2022
Reviewed Jul 11, 2022
Published by the National Vulnerability Database Jul 11, 2022
Last updated Jul 24, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.070%
(32nd percentile)

Weaknesses

CVE ID

CVE-2022-31080

GHSA ID

GHSA-6wvc-6pww-qr4r

Source code

github.com/kubeedge/kubeedge

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.