github.com/kubeedge/kubeedge
Affected
- introduced
1.10.0, fixed1.10.1(semver)
Fixed versions
1.10.1
Fix
- Fixed version
1.10.1go get github.com/kubeedge/[email protected]
Advisory
Also known as: CVE-2022-31077, GO-2022-0501
CloudCore CSI Driver: Malicious response from KubeEdge can crash CSI Driver controller server
Impact
A malicious message response from KubeEdge can crash the CSI Driver controller server by triggering a nil-pointer dereference panic. As a consequence, the CSI Driver controller will be in denial of service. An attacker would already need to be an authenticated user of the Cloud, and only when the authenticated user launches the csidriver then CloudCore may be attacked.
Patches
This bug has been fixed in Kubeedge 1.11.0, 1.10.1, and 1.9.3. Users should update to these versions to resolve the issue.
Workarounds
At the time of writing, no workaround exists.
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:
Notes: This vulnerability was found by fuzzing KubeEdge by way of OSS-Fuzz.
Medium Basis: The source's own band: MODERATE
1.10.0, fixed 1.10.1 (semver)1.10.1
1.10.1go get github.com/kubeedge/[email protected]0, fixed 1.9.3 (semver)1.9.3
1.9.3go 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