Russh: Post-decompression SSH packet size was not bounded, allowing remote oversized compressed packets
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in russh 0.61.1.
Russh is a Rust SSH client & server library. From version 0.34.0 to before version 0.61.1, when SSH compression is enabled, russh accepted compressed packets whose on-wire size passed the normal transport packet-length checks but whose decompressed size was much larger. This allowed a remote peer to send oversized post-decompression packets that should have been rejected. In current releases, this is a remote denial-of-service / resource-exhaustion issue in the post-decompression receive path. In older releases before 0.58.0, the same remote decompression path used CryptoVec, which appears to make the historical impact worse. This issue has been patched in version 0.61.1.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Eugeny | >=0.34.0 <0.61.1 | ||
| cargo: russh | >=0.34.0 <0.61.1 | 0.61.1 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in russh (Cargo), strongest first
Embed
A live severity badge for an advisory, README or ticket