https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 02:45:42 +0000 https://cve.radiocsirt.org/vuln/alsa-2022:2031 <p><strong>Affected:</strong> AlmaLinux:8: libssh, AlmaLinux:8: libssh-config, AlmaLinux:8: libssh-devel</p> <p>libssh is a library which implements the SSH protocol. It can be used to implement client and server applications.</p> <p>The following packages have been upgraded to a later upstream version: libssh (0.9.6). (BZ#1896651)</p> <p>Security Fix(es):</p> <p>* libssh: possible heap-based buffer overflow when rekeying (CVE-2021-3634)</p> <p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p> <p>Additional Changes:</p> <p>For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.</p> <p><strong>Affected:</strong> AlmaLinux:8: libssh, AlmaLinux:8: libssh-config, AlmaLinux:8: libssh-devel</p> <p>libssh is a library which implements the SSH protocol. It can be used to implement client and server applications.</p> <p>The following packages have been upgraded to a later upstream version: libssh (0.9.6). (BZ#1896651)</p> <p>Security Fix(es):</p> <p>* libssh: possible heap-based buffer overflow when rekeying (CVE-2021-3634)</p> <p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p> <p>Additional Changes:</p> <p>For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.</p> https://cve.radiocsirt.org/vuln/alsa-2022:2031 https://cve.radiocsirt.org/vuln/bdu:2022-01073 bdu:2022-01073 https://cve.radiocsirt.org/vuln/bdu:2022-01073 https://cve.radiocsirt.org/vuln/bell-cve-2021-3634 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2021-3634 https://cve.radiocsirt.org/vuln/certfr-2022-avi-052 certfr-2022-avi-052 https://cve.radiocsirt.org/vuln/certfr-2022-avi-052 https://cve.radiocsirt.org/vuln/cnvd-2021-71262 cnvd-2021-71262 https://cve.radiocsirt.org/vuln/cnvd-2021-71262 https://cve.radiocsirt.org/vuln/euvd-2026-20945 EUVD-2026-20945 https://cve.radiocsirt.org/vuln/euvd-2026-20945 https://cve.radiocsirt.org/vuln/fkie_cve-2021-3634 <p>A flaw has been found in libssh in versions prior to 0.9.6. The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called secret_hash and the other session_id. Initially, both of them are the same, but after key re-exchange, previous session_id is kept and used as an input to new secret_hash. Historically, both of these buffers had shared length variable, which worked as long as these buffers were same. But the key re-exchange operation can also change the key exchange method, which can be based on hash of different size, eventually creating &#34;secret_hash&#34; of different size than the session_id has. This becomes an issue when the session_id memory is zeroed or when it is used again during second key re-exchange.</p> <p>A flaw has been found in libssh in versions prior to 0.9.6. The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called secret_hash and the other session_id. Initially, both of them are the same, but after key re-exchange, previous session_id is kept and used as an input to new secret_hash. Historically, both of these buffers had shared length variable, which worked as long as these buffers were same. But the key re-exchange operation can also change the key exchange method, which can be based on hash of different size, eventually creating &#34;secret_hash&#34; of different size than the session_id has. This becomes an issue when the session_id memory is zeroed or when it is used again during second key re-exchange.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-3634 https://cve.radiocsirt.org/vuln/ghsa-4wwm-f449-qwpq <p>A flaw has been found in libssh in versions prior to 0.9.6. The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called secret_hash and the other session_id. Initially, both of them are the same, but after key re-exchange, previous session_id is kept and used as an input to new secret_hash. Historically, both of these buffers had shared length variable, which worked as long as these buffers were same. But the key re-exchange operation can also change the key exchange method, which can be based on hash of different size, eventually creating &#34;secret_hash&#34; of different size than the session_id has. This becomes an issue when the session_id memory is zeroed or when it is used again during second key re-exchange.</p> <p>A flaw has been found in libssh in versions prior to 0.9.6. The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called secret_hash and the other session_id. Initially, both of them are the same, but after key re-exchange, previous session_id is kept and used as an input to new secret_hash. Historically, both of these buffers had shared length variable, which worked as long as these buffers were same. But the key re-exchange operation can also change the key exchange method, which can be based on hash of different size, eventually creating &#34;secret_hash&#34; of different size than the session_id has. This becomes an issue when the session_id memory is zeroed or when it is used again during second key re-exchange.</p> https://cve.radiocsirt.org/vuln/ghsa-4wwm-f449-qwpq https://cve.radiocsirt.org/vuln/gsd-2021-3634 gsd-2021-3634 https://cve.radiocsirt.org/vuln/gsd-2021-3634 https://cve.radiocsirt.org/vuln/msrc_cve-2021-3634 msrc_CVE-2021-3634 https://cve.radiocsirt.org/vuln/msrc_cve-2021-3634 https://cve.radiocsirt.org/vuln/oesa-2021-1343 <p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: libssh, openEuler:20.03-LTS-SP2: libssh</p> <p>The ssh library was designed to be used by programmers needing a working SSH implementation by the mean of a library. The complete control of the client is made by the programmer. With libssh, you can remotely execute programs, transfer files, use a secure and transparent tunnel for your remote programs. With its Secure FTP implementation, you can play with remote files easily, without third-party programs others than libcrypto (from openssl). Security Fix(es): A flaw has been found in libssh in versions prior to 0.9.6. The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called secret_hash and the other session_id. Initially, both of them are the same, but after key re-exchange, previous session_id is kept and used as an input to new secret_hash. Historically, both of these buffers had shared length variable, which worked as long as these buffers were same. But the key re-exchange operation can also change the key exchange method, which can be based on hash of different size, eventually creating &amp;quot;secret_hash&amp;quot; of different size than the session_id has. This becomes an issue when the session_id memory is zeroed or when it is used again during second key re-exchange.(CVE-2021-3634)</p> <p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: libssh, openEuler:20.03-LTS-SP2: libssh</p> <p>The ssh library was designed to be used by programmers needing a working SSH implementation by the mean of a library. The complete control of the client is made by the programmer. With libssh, you can remotely execute programs, transfer files, use a secure and transparent tunnel for your remote programs. With its Secure FTP implementation, you can play with remote files easily, without third-party programs others than libcrypto (from openssl). Security Fix(es): A flaw has been found in libssh in versions prior to 0.9.6. The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called secret_hash and the other session_id. Initially, both of them are the same, but after key re-exchange, previous session_id is kept and used as an input to new secret_hash. Historically, both of these buffers had shared length variable, which worked as long as these buffers were same. But the key re-exchange operation can also change the key exchange method, which can be based on hash of different size, eventually creating &amp;quot;secret_hash&amp;quot; of different size than the session_id has. This becomes an issue when the session_id memory is zeroed or when it is used again during second key re-exchange.(CVE-2021-3634)</p> https://cve.radiocsirt.org/vuln/oesa-2021-1343 https://cve.radiocsirt.org/vuln/opensuse-su-2024:10998-1 <p>libssh-config-0.9.6-1.2 on GA media</p> <p>libssh-config-0.9.6-1.2 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:10998-1 https://cve.radiocsirt.org/vuln/suse-su-2024:0525-1 <p>Security update for libssh</p> <p>Security update for libssh</p> https://cve.radiocsirt.org/vuln/suse-su-2024:0525-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-3634 <p><strong>Affected:</strong> Ubuntu:20.04:LTS: libssh, Ubuntu:22.04:LTS: libssh</p> <p>A flaw has been found in libssh in versions prior to 0.9.6. The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called secret_hash and the other session_id. Initially, both of them are the same, but after key re-exchange, previous session_id is kept and used as an input to new secret_hash. Historically, both of these buffers had shared length variable, which worked as long as these buffers were same. But the key re-exchange operation can also change the key exchange method, which can be based on hash of different size, eventually creating &#34;secret_hash&#34; of different size than the session_id has. This becomes an issue when the session_id memory is zeroed or when it is used again during second key re-exchange.</p> <p><strong>Affected:</strong> Ubuntu:20.04:LTS: libssh, Ubuntu:22.04:LTS: libssh</p> <p>A flaw has been found in libssh in versions prior to 0.9.6. The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called secret_hash and the other session_id. Initially, both of them are the same, but after key re-exchange, previous session_id is kept and used as an input to new secret_hash. Historically, both of these buffers had shared length variable, which worked as long as these buffers were same. But the key re-exchange operation can also change the key exchange method, which can be based on hash of different size, eventually creating &#34;secret_hash&#34; of different size than the session_id has. This becomes an issue when the session_id memory is zeroed or when it is used again during second key re-exchange.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-3634 https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0001 <p>Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in libssh ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in libssh ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0001