CVE-2020-1730

mediumpriority · track · 22EPSS 0.031 · 88 %ileDEEURUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
3.14% (88th) EPSS
CVSS 5 · medium
Is it mine?
60 products
Check your exposure
Who says so?
6 sources
cnnvd · enisa_euvd · fstec_bdu · cert_bund

EPSS · scored 2026-10-28

A flaw was found in libssh versions before 0.8.9 and before 0.9.4 in the way it 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.

01

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

  • Fixedlibssh-0:0.9.4-2.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-0:0.9.4-2.el8.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-0:0.9.4-2.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-0:0.9.4-2.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-0:0.9.4-2.el8.src as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-0:0.9.4-2.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-config-0:0.9.4-2.el8.noarch as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debuginfo-0:0.9.4-2.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debuginfo-0:0.9.4-2.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debuginfo-0:0.9.4-2.el8.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debuginfo-0:0.9.4-2.el8.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debuginfo-0:0.9.4-2.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debuginfo-0:0.9.4-2.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debuginfo-0:0.9.4-2.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debuginfo-0:0.9.4-2.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debuginfo-0:0.9.4-2.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debuginfo-0:0.9.4-2.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debugsource-0:0.9.4-2.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debugsource-0:0.9.4-2.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debugsource-0:0.9.4-2.el8.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debugsource-0:0.9.4-2.el8.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debugsource-0:0.9.4-2.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debugsource-0:0.9.4-2.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debugsource-0:0.9.4-2.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debugsource-0:0.9.4-2.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debugsource-0:0.9.4-2.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-debugsource-0:0.9.4-2.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-devel-0:0.9.4-2.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-devel-0:0.9.4-2.el8.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-devel-0:0.9.4-2.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-devel-0:0.9.4-2.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedlibssh-devel-0:0.9.4-2.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing these updated packages, all running applications using libssh must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2020:4545
  • Fixedredhat-virtualization-host-0:4.4.3-20201116.0.el8_3.src as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/2974891

    https://access.redhat.com/errata/RHSA-2020:5218
  • Fixedredhat-virtualization-host-image-update-0:4.4.3-20201116.0.el8_3.noarch as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/2974891

    https://access.redhat.com/errata/RHSA-2020:5218
  • Workaroundlibssh-0:0.9.4-2.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-0:0.9.4-2.el8.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-0:0.9.4-2.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-0:0.9.4-2.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-0:0.9.4-2.el8.src as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-0:0.9.4-2.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-config-0:0.9.4-2.el8.noarch as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debuginfo-0:0.9.4-2.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debuginfo-0:0.9.4-2.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debuginfo-0:0.9.4-2.el8.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debuginfo-0:0.9.4-2.el8.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debuginfo-0:0.9.4-2.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debuginfo-0:0.9.4-2.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debuginfo-0:0.9.4-2.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debuginfo-0:0.9.4-2.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debuginfo-0:0.9.4-2.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debuginfo-0:0.9.4-2.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debugsource-0:0.9.4-2.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debugsource-0:0.9.4-2.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debugsource-0:0.9.4-2.el8.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debugsource-0:0.9.4-2.el8.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debugsource-0:0.9.4-2.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debugsource-0:0.9.4-2.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debugsource-0:0.9.4-2.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debugsource-0:0.9.4-2.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debugsource-0:0.9.4-2.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-debugsource-0:0.9.4-2.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-devel-0:0.9.4-2.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-devel-0:0.9.4-2.el8.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-devel-0:0.9.4-2.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-devel-0:0.9.4-2.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundlibssh-devel-0:0.9.4-2.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    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.

  • Workaroundimgbased-0:1.2.13-0.1.el8ev.noarch as a component of RHEL 8-based RHEV-H for RHEV 4 (build requirements)redhat_csaf

    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.

  • Workaroundimgbased-0:1.2.13-0.1.el8ev.src as a component of RHEL 8-based RHEV-H for RHEV 4 (build requirements)redhat_csaf

    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.

  • Workaroundpython3-imgbased-0:1.2.13-0.1.el8ev.noarch as a component of RHEL 8-based RHEV-H for RHEV 4 (build requirements)redhat_csaf

    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.

  • Workaroundredhat-release-virtualization-host-0:4.4.3-1.el8ev.src as a component of RHEL 8-based RHEV-H for RHEV 4 (build requirements)redhat_csaf

    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.

  • Workaroundredhat-release-virtualization-host-0:4.4.3-1.el8ev.x86_64 as a component of RHEL 8-based RHEV-H for RHEV 4 (build requirements)redhat_csaf

    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.

  • Workaroundredhat-virtualization-host-0:4.4.3-20201116.0.el8_3.src as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8redhat_csaf

    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.

  • Workaroundredhat-virtualization-host-image-update-0:4.4.3-20201116.0.el8_3.noarch as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8redhat_csaf

    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.

  • Workaroundredhat-virtualization-host-image-update-placeholder-0:4.4.3-1.el8ev.noarch as a component of RHEL 8-based RHEV-H for RHEV 4 (build requirements)redhat_csaf

    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.

02

cvss

Technical severity, 0–10. One row per scoring source.

7.5
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 4.9–7.5

v2.05mediumAV:N/AC:L/Au:N/C:N/I:N/A:Pprimary · NVD / NIST USexploitability 10 · impact 2.9
v3.15.3mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lprimary · NVD / NIST USexploitability 3.9 · impact 1.4
v3.17.5highAV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hsecondary · FSTEC (BDU) RU
v3.15.3mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lsecondary · ENISA EU
v3.15.3mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lsecondary · secalert@redhat.com USexploitability 3.9 · impact 1.4
v3.14.9mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:Usecondary · CVSS-BT (t0sche)
v3.15.3mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lsecondary · Red Hat Product Security US
03

weaknesses

The CWE weakness classes this flaw belongs to.

04

affected products (60)

Products and version ranges known to be affected.

05

advisories (6)

Vendor and ecosystem advisories describing this.

  • RHSA-2020:4545Red Hat Security Advisory: libssh security, bug fix, and enhancement update2020-11-04csaf · redhat_csafUS

    An update for libssh is now available for Red Hat Enterprise Linux 8. Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • RHSA-2020:5218Red Hat Security Advisory: Red Hat Virtualization security, bug fix, and enhancement update2020-11-24csaf · redhat_csafUS

    An update for imgbased, redhat-release-virtualization-host, and redhat-virtualization-host is now available for Red Hat Virtualization 4 for Red Hat Enterprise Linux 8. Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • WID-SEC-W-2024-0439libssh: Schwachstelle ermöglicht Denial of ServiceDeutsch2020-04-08csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann eine Schwachstelle in libssh ausnutzen, um einen Denial of Service Angriff durchzuführen.

  • WID-SEC-W-2024-3377Dell PowerProtect Data Domain: Mehrere SchwachstellenDeutsch2024-11-07csaf · cert_bundDE

    Ein lokaler Angreifer kann mehrere Schwachstellen in Dell PowerProtect Data Domain ausnutzen, um seine Privilegien zu erhöhen, Informationen offenzulegen und um nicht näher beschriebene Auswirkungen zu erzielen.

  • WID-SEC-W-2025-0227IBM QRadar SIEM: Mehrere SchwachstellenDeutsch2021-11-30csaf · cert_bundDE

    Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um seine Privilegien zu erweitern, Administratorrechte zu erlangen, beliebigen Programmcode auszuführen, Informationen offenzulegen, Dateien zu manipulieren oder Sicherheitsvorkehrungen zu umgehen.

  • WID-SEC-W-2026-0205Oracle MySQL: Mehrere SchwachstellenDeutsch2020-10-20csaf · cert_bundDE

    Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle MySQL ausnutzen, um die Verfügbarkeit, Vertraulichkeit und Integrität zu gefährden.

06

also known as (4)

Other names and identifiers for this entity.

07

sources

Which sources assert this record, and when.

09

references (50)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan