An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SSH_MSG_CHANNEL_REQUEST packets with an exit status message and no payload are parsed. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.
The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Libssh2 | Libssh2 | * | 1.8.1 (excluding) |
| Red Hat Ansible Tower 3.4 for RHEL 7 | RedHat | ansible-tower-34/ansible-tower-memcached:1.4.15-28 | * |
| Red Hat Ansible Tower 3.4 for RHEL 7 | RedHat | ansible-tower-35/ansible-tower-memcached:1.4.15-28 | * |
| Red Hat Ansible Tower 3.4 for RHEL 7 | RedHat | ansible-tower-37/ansible-tower-memcached-rhel7:1.4.15-28 | * |
| Red Hat Enterprise Linux 7 | RedHat | libssh2-0:1.4.3-12.el7_6.3 | * |
| Libssh2 | Ubuntu | bionic | * |
| Libssh2 | Ubuntu | cosmic | * |
| Libssh2 | Ubuntu | esm-apps/bionic | * |
| Libssh2 | Ubuntu | esm-apps/xenial | * |
| Libssh2 | Ubuntu | trusty | * |
| Libssh2 | Ubuntu | trusty/esm | * |
| Libssh2 | Ubuntu | upstream | * |
| Libssh2 | Ubuntu | xenial | * |