Eugeny russh
russh: Client-side channel-scoped Handler callbacks fire for channel IDs the client never opened
Russh is a Rust SSH client and server library. Prior to 0.63.1, client_read_authenticated in russh/src/client/encrypted.rs forwards CHANNEL_DATA, CHANNEL_EXTENDED_DATA, CHANNEL_EOF, CHANNEL_CLOSE, CHANNEL_OPEN_FAILURE, CHANNEL_SUCCESS, CHANNEL_FAILURE, and CHANNEL_REQUEST subtypes exit-status, exit-signal, and xon-xoff to public client::Handler callbacks without confirming that the ChannelId belongs to a channel the client opened and established. A malicious SSH server can send lifecycle events for predicted, unopened, unconfirmed, or released channel identifiers, causing application panics or corrupting command completion and exit-code tracking. This issue is fixed in version 0.63.1.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.63.1
Fixed in 0.63.1
Mitigation
Upgrade russh to 0.63.1 or later.
References
- Vendor advisory github.com/Eugeny/russh/security/advisories/GH…
- Patch github.com/Eugeny/russh/commit/3430fd26ecafc0d…
- Release notes github.com/Eugeny/russh/releases/tag/v0.63.1
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.