This update for openssl fixes various security issues :

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-0702 aka the 'CacheBleed' attack. (bsc#968050)     Various changes in the modular exponentation code were     added that make sure that it is not possible to recover     RSA secret keys by analyzing cache-bank conflicts on the     Intel Sandy-Bridge microarchitecture.

    Note that this was only exploitable if the malicious     code was running on the same hyper threaded Intel Sandy     Bridge processor as the victim thread performing     decryptions.

  - CVE-2016-0705 (bnc#968047): A double free() bug in the     DSA ASN1 parser code was fixed that could be abused to     facilitate a denial-of-service attack.

  - 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-0798 (bnc#968265) The SRP user database lookup     method SRP_VBASE_get_by_user() had a memory leak that     attackers could abuse to facility DoS attacks. To     mitigate the issue, the seed handling in     SRP_VBASE_get_by_user() was disabled even if the user     has configured a seed. Applications are advised to     migrate to SRP_VBASE_get1_by_user().

  - 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 :

  - CVE-2016-0703 (bsc#968051): This issue only affected     versions of OpenSSL prior to March 19th 2015 at which     time the code was refactored to address vulnerability     CVE-2015-0293. It would have made the above 'DROWN'     attack much easier.

  - CVE-2016-0704 (bsc#968053): 'Bleichenbacher oracle in     SSLv2' This issue only affected versions of OpenSSL     prior to March 19th 2015 at which time the code was     refactored to address vulnerability CVE-2015-0293. It     would have made the above 'DROWN' attack much easier.

Also the following bug was fixed :

  - Ensure that OpenSSL doesn't fall back to the default     digest algorithm (SHA1) in case a non-FIPS algorithm was     negotiated while running in FIPS mode. Instead, OpenSSL     will refuse the session. (bnc#958501)

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The version of OpenSSL installed on the remote host is prior to 1.0.1s. It is, therefore, affected by multiple vulnerabilities as referenced in the 1.0.1s advisory.

  - The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires     a server to send a ServerVerify message before establishing that a client possesses certain plaintext RSA     data, which makes it easier for remote attackers to decrypt TLS ciphertext data by leveraging a     Bleichenbacher RSA padding oracle, aka a DROWN attack. (CVE-2016-0800)

  - The fmtstr function in crypto/bio/b_print.c in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g     improperly calculates string lengths, which allows remote attackers to cause a denial of service (overflow     and out-of-bounds read) or possibly have unspecified other impact via a long string, as demonstrated by a     large amount of ASN.1 data, a different vulnerability than CVE-2016-2842. (CVE-2016-0799)

  - Memory leak in the SRP_VBASE_get_by_user implementation in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before     1.0.2g allows remote attackers to cause a denial of service (memory consumption) by providing an invalid     username in a connection attempt, related to apps/s_server.c and crypto/srp/srp_vfy.c. (CVE-2016-0798)

  - Multiple integer overflows in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g allow remote attackers     to cause a denial of service (heap memory corruption or NULL pointer dereference) or possibly have     unspecified other impact via a long digit string that is mishandled by the (1) BN_dec2bn or (2) BN_hex2bn     function, related to crypto/bn/bn.h and crypto/bn/bn_print.c. (CVE-2016-0797)

  - Double free vulnerability in the dsa_priv_decode function in crypto/dsa/dsa_ameth.c in OpenSSL 1.0.1     before 1.0.1s and 1.0.2 before 1.0.2g allows remote attackers to cause a denial of service (memory     corruption) or possibly have unspecified other impact via a malformed DSA private key. (CVE-2016-0705)

  - The MOD_EXP_CTIME_COPY_FROM_PREBUF function in crypto/bn/bn_exp.c in OpenSSL 1.0.1 before 1.0.1s and 1.0.2     before 1.0.2g does not properly consider cache-bank access times during modular exponentiation, which     makes it easier for local users to discover RSA keys by running a crafted application on the same Intel     Sandy Bridge CPU core as a victim and leveraging cache-bank conflicts, aka a CacheBleed attack.
    (CVE-2016-0702)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

This update for openssl fixes various security issues :

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-0702 aka the 'CacheBleed' attack. (bsc#968050)     Various changes in the modular exponentation code were     added that make sure that it is not possible to recover     RSA secret keys by analyzing cache-bank conflicts on the     Intel Sandy-Bridge microarchitecture.

    Note that this was only exploitable if the malicious     code was running on the same hyper threaded Intel Sandy     Bridge processor as the victim thread performing     decryptions.

  - CVE-2016-0705 (bnc#968047): A double free() bug in the     DSA ASN1 parser code was fixed that could be abused to     facilitate a denial-of-service attack.

  - 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-0798 (bnc#968265) The SRP user database lookup     method SRP_VBASE_get_by_user() had a memory leak that     attackers could abuse to facility DoS attacks. To     mitigate the issue, the seed handling in     SRP_VBASE_get_by_user() was disabled even if the user     has configured a seed. Applications are advised to     migrate to SRP_VBASE_get1_by_user().

  - 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 :

  - CVE-2016-0703 (bsc#968051): This issue only affected     versions of OpenSSL prior to March 19th 2015 at which     time the code was refactored to address vulnerability     CVE-2015-0293. It would have made the above 'DROWN'     attack much easier.

  - CVE-2016-0704 (bsc#968053): 'Bleichenbacher oracle in     SSLv2' This issue only affected versions of OpenSSL     prior to March 19th 2015 at which time the code was     refactored to address vulnerability CVE-2015-0293. It     would have made the above 'DROWN' attack much easier.

Also the following bug was fixed :

  - Ensure that OpenSSL doesn't fall back to the default     digest algorithm (SHA1) in case a non-FIPS algorithm was     negotiated while running in FIPS mode. Instead, OpenSSL     will refuse the session. (bnc#958501)

This update was imported from the SUSE:SLE-12-SP1:Update update project.

ID	Name	Product	Family	Published	Updated	Severity
89077	SUSE SLED12 / SLES12 Security Update : openssl (SUSE-SU-2016:0620-1) (DROWN)	Nessus	SuSE Local Security Checks	3/2/2016	1/6/2021	critical
89081	OpenSSL 1.0.1 < 1.0.1s Multiple Vulnerabilities	Nessus	Web Servers	3/2/2016	10/23/2024	critical
89091	openSUSE Security Update : openssl (openSUSE-2016-289) (DROWN)	Nessus	SuSE Local Security Checks	3/3/2016	1/19/2021	critical

Detections

Analytics

Plugins Search

critical

critical

critical