A vulnerability was found in libssh through version 0.8.0, where a malicious client or server could crash the counterpart implemented with libssh AES-CTR ciphers are used and don't get fully initialized. It will crash when it tries to cleanup the AES-CTR ciphers when closing the connection.
Acknowledgments: Name: libssh team Upstream: Yasheng Yang (Google)
Mitigation: Disable AES-CTR ciphers (and DES in libssh 0.8). If you implement a server using libssh we advise to use a prefork model so each session runs in an own process. If you have implemented your server this way this is not really an issue. The client will kill its own connection.
External References: https://www.libssh.org/security/advisories/CVE-2020-1730.txt
Created libssh tracking bugs for this issue: Affects: fedora-all [bug 1822529]
Upstream patch: https://git.libssh.org/projects/libssh.git/commit/?id=b36272eac1b36982598c10de7af0a501582de07a
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2020:4545 https://access.redhat.com/errata/RHSA-2020:4545
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2020-1730
This issue has been addressed in the following products: Red Hat Virtualization 4 for Red Hat Enterprise Linux 8 Via RHSA-2020:5218 https://access.redhat.com/errata/RHSA-2020:5218