CVE-2022-31079: KubeEdge Cloud Stream and Edge Stream DoS from large stream message
First published: Mon Jul 11 2022(Updated: )
### Impact The Cloud Stream server and the Edge Stream server reads the entire message into memory without imposing a limit on the size of this message. An attacker can exploit this by sending a large message to exhaust memory and cause a DoS. The Cloud Stream server and the Edge Stream server are under DoS attack in this case. The consequence of the exhaustion is that the CloudCore and EdgeCore will be in a denial of service. Only an authenticated user can cause this issue. It will be affected only when users enable cloudStream module in the config file cloudcore.yaml and enable edgeStream module in the config file edgecore.yaml as below. cloudcore.yaml: ``` modules: ... cloudStream: enable: true ``` edgecore.yaml: ``` modules: ... edgeStream: 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 cloudStream module in the config file cloudcore.yaml and disable edgeStream module in the config file edgecore.yaml, restart process cloudcore and edgecore after modification. ### References NA ### Credits Thanks David Korczynski and Adam Korczynski of ADA Logics for responsibly disclosing this issue in accordance with the [kubeedge security policy](https://github.com/kubeedge/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](https://github.com/kubeedge/kubeedge/issues/new/choose) * To make a vulnerability report, email your vulnerability to the private [cncf-kubeedge-security@lists.cncf.io](mailto:cncf-kubeedge-security@lists.cncf.io) list with the security details and the details expected for [KubeEdge bug reports](https://github.com/kubeedge/kubeedge/blob/master/.github/ISSUE_TEMPLATE/bug-report.md).
Credit: security-advisories@github.com security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| go/github.com/kubeedge/kubeedge | <1.9.4 | 1.9.4 |
| go/github.com/kubeedge/kubeedge | >=1.10.0<1.10.2 | 1.10.2 |
| go/github.com/kubeedge/kubeedge | >=1.11.0<1.11.1 | 1.11.1 |
| KubeEdge | <1.9.4 | |
| KubeEdge | >=1.10.0<1.10.2 | |
| KubeEdge | >=1.11.0<1.11.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-31079?
CVE-2022-31079 is rated as high severity due to its potential to cause a denial of service (DoS) by exhausting memory resources.
How do I fix CVE-2022-31079?
To mitigate CVE-2022-31079, ensure you upgrade to versions 1.9.4, 1.10.2, or 1.11.1 of KubeEdge.
Who is affected by CVE-2022-31079?
CVE-2022-31079 affects KubeEdge versions prior to 1.9.4, between 1.10.0 and 1.10.2, and between 1.11.0 and 1.11.1.
What kind of attack can exploit CVE-2022-31079?
An attacker can exploit CVE-2022-31079 by sending a large message to the Cloud Stream server or Edge Stream server, leading to memory exhaustion.
What components are impacted by CVE-2022-31079?
CVE-2022-31079 impacts both the Cloud Stream server and the Edge Stream server within the KubeEdge framework.
- collector/github-advisory-latest
- alias/GHSA-wrcr-x4qj-j543
- alias/CVE-2022-31079
- agent/weakness
- agent/type
- agent/softwarecombine
- agent/author
- agent/references
- agent/severity
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/title
- agent/first-publish-date
- agent/event
- agent/trending
- agent/source
- agent/tags
- collector/nvd-cve
- agent/software-canonical-lookup-request
- collector/nvd-index
- collector/nvd-api
- package-manager/go
- vendor/linuxfoundation
- canonical/kubeedge
- version/kubeedge/1.10.0
- version/kubeedge/1.11.0