blob: 385fd4f80f5347713052ad9df416717077c848a8 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<glsa id="201606-12">
<title>libssh and libssh2: Multiple vulnerabilities</title>
<synopsis>Multiple vulnerabilities have been found in libssh and libssh2, the
worst of which allows remote attackers to cause Denial of Service.
<product type="ebuild"></product>
<announced>June 26, 2016</announced>
<revised>June 26, 2016: 1</revised>
<package name="net-libs/libssh" auto="yes" arch="*">
<unaffected range="ge">0.7.3</unaffected>
<vulnerable range="lt">0.7.3</vulnerable>
<package name="net-libs/libssh2" auto="yes" arch="*">
<unaffected range="ge">1.7.0</unaffected>
<vulnerable range="lt">1.7.0</vulnerable>
<p>libssh is a mulitplatform C library implementing the SSHv2 and SSHv1
protocol on client and server side.
<p>libssh and libssh2 both have a bits/bytes confusion bug and generate an
abnormaly short ephemeral secret for the diffie-hellman-group1 and
diffie-hellman-group14 key exchange methods. The resulting secret is 128
bits long, instead of the recommended sizes of 1024 and 2048 bits
<p>Additionally, a double free on dangling pointers in initial key exchange
packets within libssh could leave dangling pointers in the session crypto
structures. It is possible to send a malicious kexinit package to
eventually cause a server to do a double-free before this fix. This could
be used for a Denial of Service attack.
<impact type="normal">
<p>Remote attackers may gain access to confidential information due to the
short keysize generated by libssh and libssh2, or cause a Denial of
Service condition.
<p>There is no known workaround at this time.</p>
<p>All libssh users should upgrade to the latest version:</p>
# emerge --sync
# emerge --ask --oneshot --verbose "&gt;=net-libs/libssh-0.7.3"
<p>All libssh2 users should upgrade to the latest version:</p>
# emerge --sync
# emerge --ask --oneshot --verbose "&gt;=net-libs/libssh2-1.7.0"
<uri link="">CVE-2014-8132</uri>
<uri link="">CVE-2016-0739</uri>
<uri link="">CVE-2016-0787</uri>
<metadata tag="requester" timestamp="Tue, 30 Jun 2015 22:23:55 +0000">
<metadata tag="submitter" timestamp="Sun, 26 Jun 2016 12:56:59 +0000">b-man</metadata>