Bug 1801998 (CVE-2020-1730) - CVE-2020-1730 libssh: denial of service when handling AES-CTR (or DES) ciphers
Summary: CVE-2020-1730 libssh: denial of service when handling AES-CTR (or DES) ciphers
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2020-1730
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1802422 1814517 1822529
Blocks: 1795471
TreeView+ depends on / blocked
 
Reported: 2020-02-12 05:27 UTC by Dhananjay Arunesh
Modified: 2023-12-15 17:18 UTC (History)
29 users (show)

Fixed In Version: libssh 0.8.9, libssh 0.9.4
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the way libssh handled AES-CTR (or DES ciphers if enabled) ciphers. The server or client could crash when the connection hasn't been fully initialized and the system tries to cleanup the ciphers when closing the connection. The biggest threat from this vulnerability is system availability.
Clone Of:
Environment:
Last Closed: 2020-11-04 02:24:17 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4545 0 None None None 2020-11-04 01:52:05 UTC
Red Hat Product Errata RHSA-2020:5218 0 None None None 2020-11-24 13:14:37 UTC

Description Dhananjay Arunesh 2020-02-12 05:27:24 UTC 
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.
Comment 2 Huzaifa S. Sidhpurwala 2020-02-13 05:58:01 UTC 
Acknowledgments:

Name: libssh team
Upstream: Yasheng Yang (Google)
Comment 3 Huzaifa S. Sidhpurwala 2020-02-13 06:01:24 UTC 
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.
Comment 8 Huzaifa S. Sidhpurwala 2020-04-09 09:26:21 UTC 
External References:

https://www.libssh.org/security/advisories/CVE-2020-1730.txt
Comment 9 Huzaifa S. Sidhpurwala 2020-04-09 09:27:04 UTC 
Created libssh tracking bugs for this issue:

Affects: fedora-all [bug 1822529]
Comment 10 Huzaifa S. Sidhpurwala 2020-04-09 09:31:32 UTC 
Upstream patch: https://git.libssh.org/projects/libssh.git/commit/?id=b36272eac1b36982598c10de7af0a501582de07a
Comment 11 errata-xmlrpc 2020-11-04 01:52:19 UTC 
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
Comment 12 Product Security DevOps Team 2020-11-04 02:24:17 UTC 
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
Comment 14 errata-xmlrpc 2020-11-24 13:14:32 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.