4 matches found
russh: peer-declared zero maximum packet size permanently stalls channel writes (silent AsyncWrite hang)
Summary A peer can advertise maximum packet size = 0 in its channel-open message CHANNELOPEN when attacking a server, CHANNELOPENCONFIRMATION when attacking a client. russh accepts the value without validation and copies it into the channel write state, where it caps the size of every outgoing da...
GHSA-FW5C-8223-6H42 russh: peer-declared zero maximum packet size permanently stalls channel writes (silent AsyncWrite hang)
Summary A peer can advertise maximum packet size = 0 in its channel-open message CHANNELOPEN when attacking a server, CHANNELOPENCONFIRMATION when attacking a client. russh accepts the value without validation and copies it into the channel write state, where it caps the size of every outgoing da...
GHSA-35G8-35P8-C8FW Russh: Unbounded memory exhaustion via CHANNEL_OPEN flood during a client-stalled rekey
Summary A russh server can be driven to unbounded heap growth process OOM / kill by a peer that speaks only standard SSH messages, in the default configuration. The peer starts a key re-exchange sends SSHMSGKEXINIT but never sends the follow-up SSHMSGKEXECDHINIT, leaving the server's kex state...
Russh: Unbounded memory exhaustion via CHANNEL_OPEN flood during a client-stalled rekey
Summary A russh server can be driven to unbounded heap growth process OOM / kill by a peer that speaks only standard SSH messages, in the default configuration. The peer starts a key re-exchange sends SSHMSGKEXINIT but never sends the follow-up SSHMSGKEXECDHINIT, leaving the server's kex state...