An issue in AsyncSSH before 2.14.1 allows attackers to control the extension info message (RFC 8308) via a man-in-the-middle attack, aka a Rogue Extension Negotiation.
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Asyncssh | Asyncssh_project | * | 2.14.1 (excluding) |
Python-asyncssh | Ubuntu | bionic | * |
Python-asyncssh | Ubuntu | esm-apps/bionic | * |
Python-asyncssh | Ubuntu | esm-apps/noble | * |
Python-asyncssh | Ubuntu | esm-apps/xenial | * |
Python-asyncssh | Ubuntu | focal | * |
Python-asyncssh | Ubuntu | jammy | * |
Python-asyncssh | Ubuntu | lunar | * |
Python-asyncssh | Ubuntu | mantic | * |
Python-asyncssh | Ubuntu | noble | * |
Python-asyncssh | Ubuntu | trusty | * |
Python-asyncssh | Ubuntu | upstream | * |
Python-asyncssh | Ubuntu | xenial | * |