First published: Mon Jun 27 2022(Updated: )
KubeEdge is built upon Kubernetes and extends native containerized application orchestration and device management to hosts at the Edge. In affected versions a malicious message can crash CloudCore by triggering a nil-pointer dereference in the UDS Server. Since the UDS Server only communicates with the CSI Driver on the cloud side, the attack is limited to the local host network. As such, an attacker would already need to be an authenticated user of the Cloud. Additionally it will be affected only when users turn on the unixsocket switch in the config file cloudcore.yaml. 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. Users unable to upgrade should sisable the unixsocket switch of CloudHub in the config file cloudcore.yaml.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
KubeEdge | <1.9.3 | |
KubeEdge | =1.10.0 | |
KubeEdge | =1.10.0-beta0 |
https://github.com/kubeedge/kubeedge/pull/3899/commits/5d60ae9eabd6b6b7afe38758e19bbe8137664701
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-31076 is considered a critical severity vulnerability due to the potential for remote denial-of-service attacks.
To fix CVE-2022-31076, upgrade KubeEdge to version 1.10.0 or later, as the issue has been addressed in these versions.
CVE-2022-31076 affects KubeEdge versions prior to 1.10.0 and version 1.9.3.
The impact of CVE-2022-31076 is that a malicious message can cause CloudCore to crash, resulting in service disruption.
Yes, CVE-2022-31076 is exploitable remotely, allowing attackers to send malicious messages that can crash the service.