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-31079, GO-2022-0511
KubeEdge Cloud Stream and Edge Stream DoS from large stream message
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:
modules:
...
cloudStream:
enable: true
edgecore.yaml:
modules:
...
edgeStream:
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 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:
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