Description
rpcx through 1.9.3, fixed in commit 047aec1, contains a denial-of-service vulnerability in protocol.Message.Decode (protocol/message.go). When a message has the compression flag set, the payload is gzip-decompressed via util.Unzip with no limit on the decompressed output size. The only built-in size guard, protocol.MaxMessageLength, is checked against the compressed on-the-wire frame length, not the decompressed size, so it provides no protection. Because decoding (and decompression) occurs in readRequest before authentication, a single unauthenticated connection can send a small (under 2 MB) gzip-compressed message that expands to gigabytes of heap allocation, leading to out-of-memory conditions and service unavailability.
Problem types
Improper Handling of Highly Compressed Data (Data Amplification)
Product status
Any version
047aec18efa7d037105e2b72c36dd2ae05e1acc6 (git)
Credits
George Chen
References
github.com/smallnest/rpcx/issues/942 (Researcher Disclosure)
github.com/smallnest/rpcx/pull/943 (Fix PR)
github.com/...ommit/047aec18efa7d037105e2b72c36dd2ae05e1acc6 (Fix Commit)
www.vulncheck.com/...zip-decompression-bomb-in-wire-protocol