Summary
It was discovered that libssh2 mishandled certain input. If libssh2 were
used to connect to a malicious or compromised SSH server, a remote,
unauthenticated attacker could possibly execute arbitrary code on the client
system. (CVE-2019-3855)
It was discovered that libssh2 incorrectly handled prompt requests. A
remote attacker could possibly use this issue to execute arbitrary code.
(CVE-2019-3856)
It was discovered that libssh2 incorrectly handled SSH_MSG_CHANNEL_REQUEST
packets. A remote attacker could possibly use this issue to execute
arbitrary code, cause a denial of service, or obtain sensitive information.
(CVE-2019-3857, CVE-2019-3862)
It was discovered that libssh2 incorrectly handled specially crafted SFTP
packets. A remote attacker could possibly use this issue to cause a denial
of service or obtain sensitive information. (CVE-2019-3858)
It was discovered that libssh2 incorrectly handled certain specially
crafted packets. A remote attacker could possibly use this issue to cause a
denial of service or obtain sensitive information. (CVE-2019-3859)
It was discovered that libssh2 incorrectly handled SFTP packets with empty
payloads. A remote attacker could possibly use this issue to cause a denial
of service or obtain sensitive information. (CVE-2019-3860)
It was discovered that libssh2 incorrectly handled padding values in SSH
packets. A remote attacker could possibly use this issue to cause a denial
of service or obtain sensitive information. (CVE-2019-3861)
It was discovered that libssh2 incorrectly handled interactive response
messages length. A remote attacker could possibly use this issue to execute
arbitrary code. (CVE-2019-3863)
It was discovered that libssh2 incorrectly handled the Diffie Hellman key
exchange. A remote attacker could possibly use this issue to cause a denial
of service or obtain sensitive information. (CVE-2019-13115)
It was discovered that libssh2 incorrectly handled bound checks in
SSH_MSG_DISCONNECT. A remote attacker could possibly use this issue to
cause a denial of service or obtain sensitive information. (CVE-2019-17498)
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| Ubuntu · Pro 16.04 LTS Pro:16.04:LTS | libssh2 | 1.5.0-2ubuntu0.1+esm1 |
Vulnerabilities 11
-
High 7.5
An integer overflow flaw which could lead to an out of bounds write was discovered in libssh2 before 1.8.1 in the way p…
-
High 7.5
An integer overflow flaw, which could lead to an out of bounds write, was discovered in libssh2 before 1.8.1 in the way…
-
High 7.5
An integer overflow flaw which could lead to an out of bounds write was discovered in libssh2 before 1.8.1 in the way S…
-
High 7.5
A flaw was found in libssh2 before 1.8.1 creating a vulnerability on the SSH client side. A server could send a multipl…
-
High 7.3
An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SSH_MSG_CHANNEL_REQUEST packets with an ex…
-
Medium 5.0
An out of bounds read flaw was discovered in libssh2 before 1.8.1 when a specially crafted SFTP packet is received from…
-
Medium 5.0
An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the _libssh2_packet_require and _libssh2_packet_re…
-
Medium 5.0
An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SFTP packets with empty payloads are parse…
-
Medium 5.0
An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SSH packets with a padding length value gr…
-
Unscored —
In libssh2 before 1.9.0, kex_method_diffie_hellman_group_exchange_sha256_key_exchange in kex.c has an integer overflow …
-
Unscored —CVE-2019-17498 Public exploit
In libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an integer overflow in a bounds ch…
References
-
report
https://ubuntu.com/security/CVE-2019-3855
-
report
https://ubuntu.com/security/CVE-2019-3856
-
report
https://ubuntu.com/security/CVE-2019-3857
-
report
https://ubuntu.com/security/CVE-2019-3858
-
report
https://ubuntu.com/security/CVE-2019-3859
-
report
https://ubuntu.com/security/CVE-2019-3860
-
report
https://ubuntu.com/security/CVE-2019-3861
-
report
https://ubuntu.com/security/CVE-2019-3862
-
report
https://ubuntu.com/security/CVE-2019-3863
-
report
https://ubuntu.com/security/CVE-2019-13115
-
report
https://ubuntu.com/security/CVE-2019-17498