Advisory

GHSA-x3px-2p95-f6jr

Also known as: CVE-2022-31075, GO-2022-0509

Summary

KubeEdge DoS when signing the CSR from EdgeCore

Details

Impact
EdgeCore may be susceptible to a DoS attack on CloudHub if an attacker was to send a well-crafted HTTP request to /edge.crt.
If an attacker can send a well-crafted HTTP request to CloudHub, and that request has a very large body, that request could crash the HTTP service through a memory exhaustion vector. The request body is being read into memory, and a body that was larger than the available memory could lead to a successful attack.
Because the request would have to make it through authorization, only authorized users could perform this attack. The consequence of the exhaustion is that CloudHub will be in denial of service. It will be affected only when users enable the CloudHub module in the file cloudcore.yaml as below:

modules:
  ...
  cloudHub:
    enable: true

Patches
This bug has been fixed in Kubeedge 1.11.1, 1.10.2, 1.9.4. Users should update to these versions to resolve the issue.

Workarounds
Disable the CloudHub module 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:

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2022-07-11 21:04 UTC
Modified
2024-08-21 15:26 UTC

Affected packages and fixes

github.com/kubeedge/kubeedge

Go · All systems

Affected

  • introduced 1.11.0, fixed 1.11.1 (semver)

Fixed versions

1.11.1

Fix

github.com/kubeedge/kubeedge

Go · All systems

Affected

  • introduced 1.10.0, fixed 1.10.2 (semver)

Fixed versions

1.10.2

Fix

github.com/kubeedge/kubeedge

Go · All systems

Affected

  • introduced 0, fixed 1.9.4 (semver)

Fixed versions

1.9.4

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences