CVE-2020-16135
libssh 0.9.4 has a NULL pointer dereference in tftpserver.c if ssh_buffer_new returns NULL.
- Update to 0.8.0~20170825.94fa1e38-1ubuntu0.7
Published Updated
PatchFirst · Latest vulnerabilities
libssh vulnerabilities
Vulnerabilities published for libssh in the last 30 days: 0. Listed in the KEV catalogue: 0.
Vulnerabilities: 5
CVE-2020-1730
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.
- Update to 0.8.0~20170825.94fa1e38-1ubuntu0.6
Published UpdatedCVE-2019-14889
A flaw was found with the libssh API function ssh_scp_new() in versions before 0.9.3 and before 0.8.8. When the libssh SCP client connects to a server, the scp command, which includes a user-provided path, is executed on the server-side. In case the library is used in a way where users can influence the third parameter of the function, it would become possible for an attacker to inject arbitrary commands, leading to a compromise of the remote target.
- Update to 0.8.0~20170825.94fa1e38-1ubuntu0.5
Published Updatedlibssh regression
USN-3795-1 and USN-3795-2 fixed a vulnerability in libssh. The upstream fix introduced a regression. This update fixes the problem. Original advisory details: Peter Winter-Smith discovered that libssh incorrectly handled authentication when being used as a server. A remote attacker could use this issue to bypass authentication without any credentials.
- Update to 0.8.0~20170825.94fa1e38-1ubuntu0.2
Published UpdatedCVE-2018-10933
A vulnerability was found in libssh's server-side state machine before versions 0.7.6 and 0.8.4. A malicious client could create channels without first performing authentication, resulting in unauthorized access.
- Update to 0.8.0~20170825.94fa1e38-1ubuntu0.1
Published Updated
Check your server
Check your installed stack and versions against the current vulnerability feeds.