github.com/moby/spdystream
Affected
- introduced
0, fixed0.5.1(semver)
Fixed versions
0.5.1
Fix
- Fixed version
0.5.1go get github.com/moby/[email protected]
Advisory
Also known as: CVE-2026-35469, GHSA-pc3f-x583-g7j2
Uncontrolled resource consumption when parsing SPDY frames in github.com/moby/spdystream
The SPDY/3 frame parser in spdystream does not validate attacker-controlled counts and lengths before allocating memory. A remote peer that can send SPDY frames to a service using spdystream can cause the process to allocate gigabytes of memory with a small number of malformed control frames, leading to an out-of-memory crash.
Three allocation paths in the receive side are affected:
Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into attacker-controlled bytes that the parser interprets as 32-bit counts and lengths. A single crafted frame is enough to exhaust process memory.
Not rated by the source.
0, fixed 0.5.1 (semver)0.5.1
0.5.1go get github.com/moby/[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: Go Vulnerability Database · CC BY 4.0