New upstream release fixing security issues. Note that SSLv2 was already disabled by default in Fedora OpenSSL.

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

The version of Apple Xcode installed on the remote macOS or Mac OS X host is prior to 8.1. It is, therefore, affected by multiple remote code execution vulnerabilities in the Node.js component of the Xcode Server. An unauthenticated, remote attacker can exploit these vulnerabilities to cause a denial of service condition or the execution of arbitrary code.

The version of OpenSSL installed on the remote host is prior to 1.0.2g. It is, therefore, affected by multiple vulnerabilities as referenced in the 1.0.2g 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 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-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.

Bugs fixed :

  - Avoid running OPENSSL_config twice. This avoids breaking     engine loading. (bsc#952871)

  - 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 digest. (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.

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 :

  - 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 fixes the following bug :

  - Avoid running OPENSSL_config twice. This avoids breaking     engine loading and also fixes a memory leak in libssl.
    (bsc#952871)

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 remote host is running a version of Mac OS X that is prior to 10.13.6 or is not macOS 10.14. It is, therefore, affected by multiple vulnerabilities in the following components :

  - afpserver
  - AppleGraphicsControl
  - Application Firewall
  - App Store
  - APR
  - ATS
  - Auto Unlock
  - Bluetooth
  - CFNetwork
  - CoreFoundation
  - CoreText
  - Crash Reporter
  - CUPS
  - Dictionary
  - Grand Central Dispatch
  - Heimdal
  - Hypervisor
  - iBooks
  - Intel Graphics Driver
  - IOHIDFamily
  - IOKit
  - IOUserEthernet
  - Kernel
  - LibreSSL
  - Login Window
  - mDNSOffloadUserClient
  - MediaRemote
  - Microcode
  - Security
  - Spotlight
  - Symptom Framework
  - Text
  - Wi-Fi

Note that successful exploitation of the most serious issues can result in arbitrary code execution.

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 Kasper 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, CVE-2016-2842     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 (wheezy) 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.

This update for openssl fixes the following issues :

Security issues fixed :

  - CVE-2016-2108: Memory corruption in the ASN.1 encoder     (bsc#977617)

  - CVE-2016-2105: EVP_EncodeUpdate overflow (bsc#977614)

  - CVE-2016-2106: EVP_EncryptUpdate overflow (bsc#977615)

  - CVE-2016-2109: ASN.1 BIO excessive memory allocation     (bsc#976942)

  - CVE-2016-0702: Side channel attack on modular     exponentiation 'CacheBleed' (bsc#968050)

Bugs fixed :

  - fate#320304: build 32bit devel package

  - bsc#976943: Fix buffer overrun in ASN1_parse

  - bsc#973223: allow weak DH groups, vulnerable to the     logjam attack, when environment variable     OPENSSL_ALLOW_LOGJAM_ATTACK is set

  - bsc#889013: Rename README.SuSE to the new spelling

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.

This update for OpenSSL fixes the following security issues :

CVE-2016-2105: EVP_EncodeUpdate overflow (bsc#977614)

CVE-2016-2106: EVP_EncryptUpdate overflow (bsc#977615)

CVE-2016-2108: Memory corruption in the ASN.1 encoder (bsc#977617)

CVE-2016-2109: ASN.1 BIO excessive memory allocation (bsc#976942)

CVE-2016-0702: Side channel attack on modular exponentiation 'CacheBleed' (bsc#968050)

The update package also includes non-security fixes. See advisory for details.

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.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
89499	Fedora 23 : openssl-1.0.2g-2.fc23 (2016-2802690366)	Nessus	Fedora Local Security Checks	2016/3/4	2021/1/11	critical
94935	Apple Xcode < 8.1 Node.js Multiple RCE (macOS)	Nessus	MacOS X Local Security Checks	2016/11/17	2020/5/5	critical
89082	OpenSSL 1.0.2 < 1.0.2g Multiple Vulnerabilities	Nessus	Web Servers	2016/3/2	2024/10/23	critical
89076	SUSE SLED12 / SLES12 Security Update : openssl (SUSE-SU-2016:0617-1) (DROWN)	Nessus	SuSE Local Security Checks	2016/3/2	2021/1/6	critical
89658	SUSE SLED12 / SLES12 Security Update : openssl (SUSE-SU-2016:0641-1) (DROWN)	Nessus	SuSE Local Security Checks	2016/3/4	2021/1/6	critical
118178	macOS < 10.14 Multiple Vulnerabilities	Nessus	MacOS X Local Security Checks	2018/10/18	2026/1/9	critical
89061	Debian DSA-3500-1 : openssl - security update	Nessus	Debian Local Security Checks	2016/3/2	2021/1/11	critical
91158	SUSE SLES11 Security Update : openssl (SUSE-SU-2016:1290-1)	Nessus	SuSE Local Security Checks	2016/5/16	2021/1/19	critical
91282	SUSE SLES10 Security Update : openssl (SUSE-SU-2016:1360-1)	Nessus	SuSE Local Security Checks	2016/5/20	2021/1/6	critical

检测

插件搜索

critical

critical

critical

critical

critical

critical

critical

critical

critical