KubeEdge Edge ServiceBus module DoS
Moderate severity
GitHub Reviewed
Published
Jul 11, 2022
in
kubeedge/kubeedge
•
Updated Jan 27, 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 by the National Vulnerability Database
Jul 11, 2022
Published to the GitHub Advisory Database
Jul 11, 2022
Reviewed
Jul 11, 2022
Last updated
Jan 27, 2023
Impact
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 which by accident 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 fileedgecore.yaml
as below: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 the ServiceBus module in the config file
edgecore.yaml
.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