github.com/kubeedge/kubeedge
Affected
- introduced
1.0.0, fixed1.21.2(semver)
Fixed versions
1.21.2
Fix
- Fixed version
1.21.2go get github.com/kubeedge/[email protected]
Advisory
Also known as: CVE-2026-62370, GO-2026-6569
KubeEdge: Unbounded allocation in viaduct packer enables authenticated remote DoS against CloudHub
Summary
KubeEdge CloudHub uses the viaduct packer to decode messages received from connected peers. The packer reads a 32-bit payload length from the message header and previously allocated a buffer of that size without enforcing an upper bound.
An authenticated peer that can establish a viaduct connection to CloudHub can send a crafted message header containing an excessively large payload length. This may cause CloudHub to allocate a large amount of memory and can result in memory exhaustion, process termination, or denial of service.
Impact
A successfully authenticated malicious or compromised edge node may repeatedly send crafted viaduct message headers to increase CloudHub memory consumption.
Depending on available memory and deployment limits, exploitation may cause:
Authentication to the viaduct endpoint is required. This issue does not provide unauthenticated access or direct code execution.
Root cause
The viaduct packer trusted the payload length encoded in the message header and allocated the payload buffer before validating whether the declared length was within an acceptable range.
Fix
The fix introduces a maximum viaduct payload size of 32 MiB.
The updated implementation:
Fixes have been prepared for the following patch releases:
These versions should not be listed as released until the coordinated release process is complete.
Workarounds
Before patched versions are available, operators should:
Affected component
pkg/viaduct/pkg/packerCredits
KubeEdge thanks Sang-Hoon Choi (KoreaSecurity, Sejong University)
for responsibly reporting this issue and for coordinating with the KubeEdge
maintainers through the security disclosure process.
Medium Basis: The source's own band: MODERATE
1.0.0, fixed 1.21.2 (semver)1.21.2
1.21.2go get github.com/kubeedge/[email protected]1.22.0, fixed 1.22.2 (semver)1.22.2
1.22.2go get github.com/kubeedge/[email protected]1.23.0, fixed 1.23.1 (semver)1.23.1
1.23.1go get github.com/kubeedge/[email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0