Security
Headlines
HeadlinesLatestCVEs

Headline

GHSA-8f4f-v9x5-cg6j: CloudCore UDS Server: Malicious Message can crash CloudCore

Impact

A malicious message can crash CloudCore by triggering a null-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.

It will be affected only when users turn on the unixsocket switch in the config file cloudcore.yaml as below:

modules:
  cloudHub:
    ...
    unixsocket:
      address: xxx
      enable: true

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

Disable the unixsocket switch of CloudHub in the config file cloudcore.yaml.

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.

ghsa
#vulnerability#git#auth

Impact

A malicious message can crash CloudCore by triggering a null-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.

It will be affected only when users turn on the unixsocket switch in the config file cloudcore.yaml as below:

modules:
  cloudHub:
    ...
    unixsocket:
      address: xxx
      enable: true

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

Disable the unixsocket switch of CloudHub in the config file cloudcore.yaml.

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:

  • Open an issue in KubeEdge repo
  • To make a vulnerability report, email your vulnerability to the private [email protected] list with the security details and the details expected for KubeEdge bug reports.

Notes: This vulnerability was found by fuzzing KubeEdge by way of OSS-Fuzz.

References

  • GHSA-8f4f-v9x5-cg6j

Related news

CVE-2022-31076: fix fuzzer extract message error by vincentgoat · Pull Request #3899 · kubeedge/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.