KubeEdge Cloud Stream and Edge Stream DoS from large stream message
Moderate severity
GitHub Reviewed
Published
Jul 11, 2022
in
kubeedge/kubeedge
•
Updated Jul 21, 2023
Package
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
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 21, 2023
Impact
The Cloud Stream server and the Edge Stream server reads the entire message into memory without imposing a limit on the size of this message. An attacker can exploit this by sending a large message to exhaust memory and cause a DoS. The Cloud Stream server and the Edge Stream server are under DoS attack in this case. The consequence of the exhaustion is that the CloudCore and EdgeCore will be in a denial of service.
Only an authenticated user can cause this issue. It will be affected only when users enable cloudStream module in the config file cloudcore.yaml and enable edgeStream module in the config file edgecore.yaml as below.
cloudcore.yaml:
edgecore.yaml:
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
Disable cloudStream module in the config file cloudcore.yaml and disable edgeStream module in the config file edgecore.yaml, restart process cloudcore and edgecore after modification.
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