Vulnerability Details : CVE-2022-31076
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.
Products affected by CVE-2022-31076
- cpe:2.3:a:linuxfoundation:kubeedge:*:*:*:*:*:*:*:*
- cpe:2.3:a:linuxfoundation:kubeedge:1.10.0:-:*:*:*:*:*:*
- cpe:2.3:a:linuxfoundation:kubeedge:1.10.0:beta0:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2022-31076
0.04%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 11 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2022-31076
Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
---|---|---|---|---|---|---|
2.7
|
LOW | AV:A/AC:L/Au:S/C:N/I:N/A:P |
5.1
|
2.9
|
NIST | |
5.7
|
MEDIUM | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
2.1
|
3.6
|
NIST | |
4.2
|
MEDIUM | CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H |
0.5
|
3.6
|
GitHub, Inc. |
CWE ids for CVE-2022-31076
-
The product dereferences a pointer that it expects to be valid but is NULL.Assigned by: security-advisories@github.com (Primary)
References for CVE-2022-31076
-
https://github.com/kubeedge/kubeedge/security/advisories/GHSA-8f4f-v9x5-cg6j
CloudCore UDS Server: Malicious Message can crash CloudCore · Advisory · kubeedge/kubeedge · GitHubExploit;Third Party Advisory
-
https://github.com/kubeedge/kubeedge/pull/3899/commits/5d60ae9eabd6b6b7afe38758e19bbe8137664701
fix fuzzer extract message error by vincentgoat · Pull Request #3899 · kubeedge/kubeedge · GitHubPatch;Third Party Advisory
Jump to