github.com/kubeedge/kubeedge
Affected
- introduced
1.11.0, fixed1.11.1(semver)
Fixed versions
1.11.1
Fix
- Fixed version
1.11.1go get github.com/kubeedge/[email protected]
Advisory
Also known as: CVE-2022-31078, GO-2022-0510
KubeEdge CloudCore Router memory exhaustion vulnerability
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 file cloudcore.yaml as below.
modules:
...
router:
enable: true
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:
Medium Basis: The source's own band: MODERATE
1.11.0, fixed 1.11.1 (semver)1.11.1
1.11.1go get github.com/kubeedge/[email protected]1.10.0, fixed 1.10.2 (semver)1.10.2
1.10.2go get github.com/kubeedge/[email protected]0, fixed 1.9.4 (semver)1.9.4
1.9.4go get github.com/kubeedge/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0