[SECURITY] [DSA 3500-1] openssl security update
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
- -------------------------------------------------------------------------
Debian Security Advisory DSA-3500-1 security@debian.org
https://www.debian.org/security/ Alessandro Ghedini
March 01, 2016 https://www.debian.org/security/faq
- -------------------------------------------------------------------------
Package : openssl
CVE ID : CVE-2016-0702 CVE-2016-0705 CVE-2016-0797 CVE-2016-0798
CVE-2016-0799
Several vulnerabilities were discovered in OpenSSL, a Secure Socket Layer
toolkit.
CVE-2016-0702
Yuval Yarom from the University of Adelaide and NICTA, Daniel Genkin
from Technion and Tel Aviv University, and Nadia Heninger from the
University of Pennsylvania discovered a side-channel attack which
makes use of cache-bank conflicts on the Intel Sandy-Bridge
microarchitecture. This could allow local attackers to recover RSA
private keys.
CVE-2016-0705
Adam Langley from Google discovered a double free bug when parsing
malformed DSA private keys. This could allow remote attackers to
cause a denial of service or memory corruption in applications
parsing DSA private keys received from untrusted sources.
CVE-2016-0797
Guido Vranken discovered an integer overflow in the BN_hex2bn and
BN_dec2bn functions that can lead to a NULL pointer dereference and
heap corruption. This could allow remote attackers to cause a denial
of service or memory corruption in applications processing hex or
dec data received from untrusted sources.
CVE-2016-0798
Emilia Käsper of the OpenSSL development team discovered a memory
leak in the SRP database lookup code. To mitigate the memory leak,
the seed handling in SRP_VBASE_get_by_user is now disabled even if
the user has configured a seed. Applications are advised to migrate
to the SRP_VBASE_get1_by_user function.
CVE-2016-0799
Guido Vranken discovered an integer overflow in the BIO_*printf
functions that could lead to an OOB read when printing very long
strings. Additionally the internal doapr_outch function can attempt
to write to an arbitrary memory location in the event of a memory
allocation failure. These issues will only occur on platforms where
sizeof(size_t) > sizeof(int) like many 64 bit systems. This could
allow remote attackers to cause a denial of service or memory
corruption in applications that pass large amounts of untrusted data
to the BIO_*printf functions.
Additionally the EXPORT and LOW ciphers were disabled since thay could
be used as part of the DROWN (CVE-2016-0800) and SLOTH (CVE-2015-7575)
attacks, but note that the oldstable (wheezye) and stable (jessie)
distributions are not affected by those attacks since the SSLv2 protocol
has already been dropped in the openssl package version 1.0.0c-2.
For the oldstable distribution (wheezy), these problems have been fixed
in version 1.0.1e-2+deb7u20.
For the stable distribution (jessie), these problems have been fixed in
version 1.0.1k-3+deb8u4.
For the unstable distribution (sid), these problems will be fixed shortly.
We recommend that you upgrade your openssl packages.
Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/
Mailing list: debian-security-announce@lists.debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJW1ah7AAoJEK+lG9bN5XPLwZAQAIC8QcmipL7pZmkkn2k3w0w2
HvaHZEFOnbMXLRqKquu1L+RC57TemNqVZ/0kH4qlrXZs5W+Y2ZAEcvBCFEC8OFEJ
yuz6GPnmZLqNeIIrnlJS4p9JiB06KEfadwACm4+y8YcWde8651CYavbZzlJAybOk
K48rdvG5A1h0VGaz9PUSdfMmesnHyJCixSANOSmgZ6i9FKLMLuU/+bZu4hHOwnWl
e4oHFv4XEvc2C5CxKiDDVhIu5J+Mx2lnFXQ+DBcau0JNqphx2zCulM6+ZLDMGK4P
LrxLf0IuLpQ+s5CNhiOttkP3XgCaC8iMSOXx1cOx73qRRDki5MnQuCu7t5WYMuw7
vXDWdCq8uqukXF3H0pZWGieOIa1v1cqocWZa+eH2Al5nIET3593ARgDXV+XzosUX
3cYMMh7dsJWFpaGFgnhpsE80843aE8Q4eVFAjLw83nBTtyg5hJ2qEqGs5L/gLUXR
4F+eKBLnEn79LwC5XeLq0N5o7xCnYlpuMluOH/AQi+AHF29Z1UQ7ZmMkR/iqvt0D
J+8MzDfwnlUqZrvSNgrQvIBI+Lu7cxdm8B1GSD/nUqiQDV4CHe2tc++Wfbqgl4F9
LrHZWA/j1wGuGMT/vDjXQWRSl8lIhRvAMm/FMoyBiGndNTh5TK5I9Tykazb/xp++
kW1cZiPsdcvSgmhPVjD7
=nYQh
-----END PGP SIGNATURE-----
Reply to: