KubeEdge Websocket Client in package Viaduct: DoS from large response message
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.10.2, 1.9.4, 1.11.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. Prior to versions 1.11.1, 1.10.2, and 1.9.4, a large response received by the viaduct WSClient can cause a DoS from memory exhaustion. The entire body of the response is being read into memory which could allow an attacker to send a request that returns a response with a large body. The consequence of the exhaustion is that the process which invokes a WSClient will be in a denial of service. The software is affected If users who are authenticated to the edge side connect to `cloudhub` from the edge side through WebSocket protocol. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. There are currently no known workarounds.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- kubeedge kubeedge
From 1.10.0 · fixed in 1.10.2; fixed in 1.9.4
- github.com/kubeedge/kubeedgeGo
fixed in 1.9.4; From 1.10.0 · fixed in 1.10.2; From 1.11.0 · fixed in 1.11.1
- github.com/kubeedge/kubeedgeGo
From 1.11.0 · fixed in 1.11.1
- github.com/kubeedge/kubeedgeGo
From 1.10.0 · fixed in 1.10.2
- github.com/kubeedge/kubeedgeGo
fixed in 1.9.4