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-31073, GO-2022-0507
KubeEdge Edge ServiceBus module DoS
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 file edgecore.yaml as below:
modules:
...
serviceBus:
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 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:
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