This update for compat-openssl098 fixes various security issues and bugs:
Security issues fixed:
CVE-2016-0800 aka the "DROWN" attack (bsc#968046): OpenSSL was
vulnerable to a cross-protocol attack that could lead to decryption of
TLS sessions by using a server supporting SSLv2 and EXPORT cipher suites
as a Bleichenbacher RSA padding oracle.
This update changes the openssl library to:
Disable SSLv2 protocol support by default.
This can be overridden by setting the environment variable
"OPENSSL_ALLOW_SSL2" or by using SSL_CTX_clear_options using the
SSL_OP_NO_SSLv2 flag.
Note that various services and clients had already disabled SSL
protocol 2 by default previously.
Disable all weak EXPORT ciphers by default. These can be reenabled if
required by old legacy software using the environment variable
"OPENSSL_ALLOW_EXPORT".
CVE-2016-0797 (bnc#968048): The BN_hex2bn() and BN_dec2bn() functions
had a bug that could result in an attempt to de-reference a NULL pointer
leading to crashes. This could have security consequences if these
functions were ever called by user applications with large untrusted
hex/decimal data. Also, internal usage of these functions in OpenSSL
uses data from config files
or application command line arguments. If user developed applications
generated config file data based on untrusted data, then this could
have had security consequences as well.
CVE-2016-0799 (bnc#968374) On many 64 bit systems, the internal fmtstr()
and doapr_outch() functions could miscalculate the length of a string
and attempt to access out-of-bounds memory locations. These problems
could have enabled attacks where large amounts of untrusted data is
passed to the BIO_*printf functions. If applications use these functions
in this way then they could have been vulnerable. OpenSSL itself uses
these functions when printing out human-readable dumps of ASN.1 data.
Therefore applications that print this data could have been vulnerable
if the data is from untrusted sources. OpenSSL command line applications
could also have been vulnerable when they print out ASN.1 data, or if
untrusted data is passed as command line arguments. Libssl is not
considered directly vulnerable.
CVE-2015-3197 (bsc#963415): The SSLv2 protocol did not block disabled
ciphers.
Note that the March 1st 2016 release also references following CVEs that
were fixed by us with CVE-2015-0293 in 2015:
Also fixes the following bug: