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.
https://www.tenable.com/blog/oracle-critical-patch-update-for-october-contains-180-fixes
https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html
https://www.oracle.com/security-alerts/cpujan2020.html
https://www.libssh2.org/CVE-2019-3862.html
https://www.debian.org/security/2019/dsa-4431
https://security.netapp.com/advisory/ntap-20190327-0005/
https://seclists.org/bugtraq/2019/Mar/25
https://seclists.org/bugtraq/2019/Apr/25
https://lists.debian.org/debian-lts-announce/2019/03/msg00032.html
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3862
https://access.redhat.com/errata/RHSA-2019:1884
http://www.securityfocus.com/bid/107485
http://www.openwall.com/lists/oss-security/2019/03/18/3
http://packetstormsecurity.com/files/152136/Slackware-Security-Advisory-libssh2-Updates.html
http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00003.html
http://lists.opensuse.org/opensuse-security-announce/2019-03/msg00040.html