Eugeny russh
russh: Agent server never calls `Agent::confirm`, so keys added with the confirm constraint (`ssh-add -c`) sign without confirmation
russh is a Rust SSH client and server library that includes an SSH agent protocol implementation. From 0.50.0-beta.12 until 0.65.0, the agent server's Connection::try_sign path in russh/src/keys/agent/server.rs recognizes SSH_AGENT_CONSTRAIN_CONFIRM but returns a hard-coded successful result instead of calling Agent::confirm. In applications that override Agent::confirm to require user approval or another policy check, a process that can reach the agent socket, including the remote side of a forwarded agent, can use a key added through ssh-add -c without that check and can authenticate or sign data as the user while the key remains loaded. The separate Agent::confirm_request hook still runs for every signing request, so checks implemented there remain effective, and implementations that retain the default always-successful Agent::confirm do not lose an approval check through this regression. This issue is fixed in version 0.65.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.65
Fixed in 0.65
Mitigation
Upgrade russh to 0.65 or later.
References
- Vendor advisory github.com/Eugeny/russh/security/advisories/GH…
- Patch github.com/Eugeny/russh/commit/3e04597dc54e36b…
- Patch github.com/Eugeny/russh/commit/62db6e7defd6d24…
1 more
- Release notes github.com/Eugeny/russh/releases/tag/v0.65.0
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.