This issue is significant for developers of automation, orchestration, or CI/CD tools that use russh as an SSH client. Applications that trust the library's implicit contract - expecting that Handler callbacks only fire for valid, user-initiated channels - are vulnerable to state desynchronization. A malicious or compromised SSH server can inject spoofed events to manipulate internal application state, such as exit code trackers or completion futures, or trigger application panics if the developer performs unsafe indexing based on the provided channel ID.

Attack Chain

1. Attacker controls or intercepts an SSH server (e.g., a rogue jump host or compromised build server).
2. Client connects to the malicious server and completes SSH authentication.
3. Attacker monitors for SSH_MSG_CHANNEL_OPEN or predicts future channel IDs based on the sequential allocation pattern starting at 1.
4. Attacker transmits spoofed channel-scoped messages (e.g., CHANNEL_REQUEST for exit-status or CHANNEL_CLOSE) referencing an uninitialized or non-existent channel_num.
5. The vulnerable russh client receives the message in client_read_authenticated.
6. The library fails to perform a validation check against the known active channels.
7. The library unconditionally invokes a Handler callback (e.g., client.exit_status(...) or client.channel_close(...)) with the attacker-supplied ID.
8. Downstream application code processes the callback, leading to state corruption or an unhandled panic (DoS).

Impact

Successful exploitation results in application-level denial-of-service (panics) or logic integrity violations. Automation tools relying on russh may incorrectly report success/failure of remote commands, leading to flawed deployment outcomes or bypassed security checks in CI/CD pipelines. The vulnerability affects any software utilizing russh versions up to 0.63.0 as an SSH client.

Recommendation

1. Audit downstream applications using the russh library for logic that assumes the validity of ChannelId values provided via Handler trait methods.
2. Upgrade the russh library immediately upon the availability of a patched version.
3. Implement explicit channel validation logic within the Handler trait implementations as an interim defense-in-depth measure, ensuring the application maintains its own set of active, known channels and rejecting callbacks for unknown IDs.