KubeEdge CloudCore Router memory exhaustion vulnerability
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 CloudCore Router does not impose a limit on the size of responses to requests made by the REST handler. An attacker could use this weakness to make a request that will return an HTTP response with a large body and cause DoS of CloudCore. In the HTTP Handler API, the rest handler makes a request to a pre-specified handle. The handle will return an HTTP response that is then read into memory. The consequence of the exhaustion is that CloudCore will be in a denial of service.
Only an authenticated user of the cloud can make an attack. It will be affected only when users enable
router
module in the config filecloudcore.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 router module in the config file
cloudcore.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