Lucene search

K
suseSuseOPENSUSE-SU-2016:0640-1
HistoryMar 03, 2016 - 2:11 p.m.

Security update for libopenssl0_9_8 (important)

2016-03-0314:11:44
lists.opensuse.org
37

0.975 High

EPSS

Percentile

100.0%

This update for libopenssl0_9_8 fixes the following issues:

  • 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.

  • The package was updated to 0.9.8zh:

    • fixes many security vulnerabilities (not seperately listed):
      CVE-2015-3195, CVE-2015-1788, CVE-2015-1789, CVE-2015-1790,
      CVE-2015-1792, CVE-2015-1791, CVE-2015-0286, CVE-2015-0287,
      CVE-2015-0289, CVE-2015-0293, CVE-2015-0209, CVE-2015-0288,
      CVE-2014-3571, CVE-2014-3569, CVE-2014-3572, CVE-2015-0204,
      CVE-2014-8275, CVE-2014-3570, CVE-2014-3567, CVE-2014-3568,
      CVE-2014-3566, CVE-2014-3510, CVE-2014-3507, CVE-2014-3506,
      CVE-2014-3505, CVE-2014-3508, CVE-2014-0224, CVE-2014-0221,
      CVE-2014-0195, CVE-2014-3470, CVE-2014-0076, CVE-2013-0169,
      CVE-2013-0166
  • avoid running OPENSSL_config twice. This avoids breaking engine loading.
    (boo#952871, boo#967787)

  • fix CVE-2015-3197 (boo#963415)

    • SSLv2 doesn’t block disabled ciphers