Malicious Message can crash CloudCore in KubeEdge
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
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2022-31076
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 19:09 UTC · Revision 1
Source evidence
Malicious Message can crash CloudCore in KubeEdge
core-osv · Original sourcePublished 27 Jun 2022, 20:10 UTC
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.
osv:CVE-2022-31076
Complete source record
{
"id": "58f660777aecc2f144b624a5782f0093a27954d135053b895cb660636390f241",
"url": "https://osv.dev/vulnerability/CVE-2022-31076",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Malicious Message can crash CloudCore in KubeEdge",
"summary": "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.",
"evidence": "osv:CVE-2022-31076",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2022-31076",
"aliases": [
"CVE-2022-31076",
"GHSA-8f4f-v9x5-cg6j",
"GO-2022-0500"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/kubeedge/kubeedge",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "932e145484c86d47d8ae726607dc5fc2434c06a4"
},
{
"introduced": "3803951602f938d9d90d74957eb0fbc238142101"
},
{
"last_affected": "3803951602f938d9d90d74957eb0fbc238142101"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:linuxfoundation:kubeedge:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "1.9.3"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:linuxfoundation:kubeedge:1.10.0:-:*:*:*:*:*:*",
"range": [
{
"introduced": "1.10.0-NA"
},
{
"last_affected": "1.10.0-NA"
}
],
"source": "CPE_STRING"
}
]
}
}
],
"versions": [
"1.10.0-NA",
"v1.9.2",
"v1.10.0",
"v1.9.1",
"v1.9.0-beta.0",
"v1.9.0",
"v1.8.0-beta.0",
"v1.7.0-beta.0",
"v1.7.0",
"v1.6.0-beta.0",
"v1.5.0-beta.0",
"v1.4.0-beta.0",
"v1.4.0-alpha.0",
"v1.3.0",
"v1.3.0-beta.0",
"v1.3.0-alpha.0",
"v1.2.0-beta.0",
"v1.1.0-beta.0",
"v1.0.0",
"v0.3.0-beta.0",
"v0.2.1",
"v0.2",
"v0.1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-31076.json"
}
}
],
"modified": "2026-10-28T02:30:22.613064333Z",
"provider": "osv",
"references": [
"https://github.com/kubeedge/kubeedge/pull/3899/commits/5d60ae9eabd6b6b7afe38758e19bbe8137664701",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/31xxx/CVE-2022-31076.json",
"https://github.com/kubeedge/kubeedge/security/advisories/GHSA-8f4f-v9x5-cg6j",
"https://nvd.nist.gov/vuln/detail/CVE-2022-31076"
],
"provider_metadata": {
"cwe_ids": [
"CWE-476"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/31xxx/CVE-2022-31076.json"
}
},
"related_cves": [
{
"value": "CVE-2022-31076",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 488986,
"published_at": "2022-06-27T20:10:10+00:00"
}