The Cryptographic Message Syntax (CMS) implementation in crypto/cms/cms_asn1.c in OpenSSL before 0.9.8o and 1.x before 1.0.0a does not properly handle structures that contain OriginatorInfo, which allows context-dependent attackers to modify invalid memory locations or conduct double-free attacks, and possibly execute arbitrary code, via unspecified vectors.

The remote NewStart CGSL host, running version CORE 5.04 / MAIN 5.04, has openssl packages installed that are affected by multiple vulnerabilities:

  - OpenSSL 1.0.2 (starting from version 1.0.2b) introduced     an error state mechanism. The intent was that if a     fatal error occurred during a handshake then OpenSSL     would move into the error state and would immediately     fail if you attempted to continue the handshake. This     works as designed for the explicit handshake functions     (SSL_do_handshake(), SSL_accept() and SSL_connect()),     however due to a bug it does not work correctly if     SSL_read() or SSL_write() is called directly. In that     scenario, if the handshake fails then a fatal error will     be returned in the initial function call. If     SSL_read()/SSL_write() is subsequently called by the     application for the same SSL object then it will succeed     and the data is passed without being decrypted/encrypted     directly from the SSL/TLS record layer. In order to     exploit this issue an application bug would have to be     present that resulted in a call to     SSL_read()/SSL_write() being issued after having already     received a fatal error. OpenSSL version 1.0.2b-1.0.2m     are affected. Fixed in OpenSSL 1.0.2n. OpenSSL 1.1.0 is     not affected. (CVE-2017-3737)

  - There is an overflow bug in the AVX2 Montgomery     multiplication procedure used in exponentiation with     1024-bit moduli. No EC algorithms are affected. Analysis     suggests that attacks against RSA and DSA as a result of     this defect would be very difficult to perform and are     not believed likely. Attacks against DH1024 are     considered just feasible, because most of the work     necessary to deduce information about a private key may     be performed offline. The amount of resources required     for such an attack would be significant. However, for an     attack on TLS to be meaningful, the server would have to     share the DH1024 private key among multiple clients,     which is no longer an option since CVE-2016-0701. This     only affects processors that support the AVX2 but not     ADX extensions like Intel Haswell (4th generation).
    Note: The impact from this issue is similar to     CVE-2017-3736, CVE-2017-3732 and CVE-2015-3193. OpenSSL     version 1.0.2-1.0.2m and 1.1.0-1.1.0g are affected.
    Fixed in OpenSSL 1.0.2n. Due to the low severity of this     issue we are not issuing a new release of OpenSSL 1.1.0     at this time. The fix will be included in OpenSSL 1.1.0h     when it becomes available. The fix is also available in     commit e502cc86d in the OpenSSL git repository.
    (CVE-2017-3738)

  - There is a carry propagating bug in the x86_64     Montgomery squaring procedure in OpenSSL before 1.0.2m     and 1.1.0 before 1.1.0g. No EC algorithms are affected.
    Analysis suggests that attacks against RSA and DSA as a     result of this defect would be very difficult to perform     and are not believed likely. Attacks against DH are     considered just feasible (although very difficult)     because most of the work necessary to deduce information     about a private key may be performed offline. The amount     of resources required for such an attack would be very     significant and likely only accessible to a limited     number of attackers. An attacker would additionally need     online access to an unpatched system using the target     private key in a scenario with persistent DH parameters     and a private key that is shared between multiple     clients. This only affects processors that support the     BMI1, BMI2 and ADX extensions like Intel Broadwell (5th     generation) and later or AMD Ryzen. (CVE-2017-3736)

  - OpenSSL 0.9.7 before 0.9.7l and 0.9.8 before 0.9.8d     allows remote attackers to cause a denial of service     (infinite loop and memory consumption) via malformed     ASN.1 structures that trigger an improperly handled     error condition. (CVE-2006-2937)

  - OpenSSL 0.9.7 before 0.9.7l, 0.9.8 before 0.9.8d, and     earlier versions allows attackers to cause a denial of     service (CPU consumption) via parasitic public keys with     large (1) public exponent or (2) public modulus     values in X.509 certificates that require extra time to     process when using RSA signature verification.
    (CVE-2006-2940)

  - Buffer overflow in the SSL_get_shared_ciphers function     in OpenSSL 0.9.7 before 0.9.7l, 0.9.8 before 0.9.8d, and     earlier versions has unspecified impact and remote     attack vectors involving a long list of ciphers.
    (CVE-2006-3738)

  - OpenSSL before 0.9.7, 0.9.7 before 0.9.7k, and 0.9.8     before 0.9.8c, when using an RSA key with exponent 3,     removes PKCS-1 padding before generating a hash, which     allows remote attackers to forge a PKCS #1 v1.5     signature that is signed by that RSA key and prevents     OpenSSL from correctly verifying X.509 and other     certificates that use PKCS #1. (CVE-2006-4339)

  - The get_server_hello function in the SSLv2 client code     in OpenSSL 0.9.7 before 0.9.7l, 0.9.8 before 0.9.8d, and     earlier versions allows remote servers to cause a denial     of service (client crash) via unknown vectors that     trigger a null pointer dereference. (CVE-2006-4343)

  - The BN_from_montgomery function in crypto/bn/bn_mont.c     in OpenSSL 0.9.8e and earlier does not properly perform     Montgomery multiplication, which might allow local users     to conduct a side-channel attack and retrieve RSA     private keys. (CVE-2007-3108)

  - Off-by-one error in the DTLS implementation in OpenSSL     0.9.8 before 0.9.8f allows remote attackers to execute     arbitrary code via unspecified vectors. (CVE-2007-4995)

  - Off-by-one error in the SSL_get_shared_ciphers function     in OpenSSL 0.9.7 up to 0.9.7l, and 0.9.8 up to 0.9.8f,     might allow remote attackers to execute arbitrary code     via a crafted packet that triggers a one-byte buffer     underflow. NOTE: this issue was introduced as a result     of a fix for CVE-2006-3738. As of 20071012, it is     unknown whether code execution is possible.
    (CVE-2007-5135)

  - Double free vulnerability in OpenSSL 0.9.8f and 0.9.8g,     when the TLS server name extensions are enabled, allows     remote attackers to cause a denial of service (crash)     via a malformed Client Hello packet. NOTE: some of these     details are obtained from third party information.
    (CVE-2008-0891)

  - OpenSSL 0.9.8f and 0.9.8g allows remote attackers to     cause a denial of service (crash) via a TLS handshake     that omits the Server Key Exchange message and uses     particular cipher suites, which triggers a NULL     pointer dereference. (CVE-2008-1672)

  - The dtls1_buffer_record function in ssl/d1_pkt.c in     OpenSSL 0.9.8k and earlier 0.9.8 versions allows remote     attackers to cause a denial of service (memory     consumption) via a large series of future epoch DTLS     records that are buffered in a queue, aka DTLS record     buffer limitation bug. (CVE-2009-1377)

  - Multiple memory leaks in the     dtls1_process_out_of_seq_message function in     ssl/d1_both.c in OpenSSL 0.9.8k and earlier 0.9.8     versions allow remote attackers to cause a denial of     service (memory consumption) via DTLS records that (1)     are duplicates or (2) have sequence numbers much greater     than current sequence numbers, aka DTLS fragment     handling memory leak. (CVE-2009-1378)

  - Use-after-free vulnerability in the     dtls1_retrieve_buffered_fragment function in     ssl/d1_both.c in OpenSSL 1.0.0 Beta 2 allows remote     attackers to cause a denial of service (openssl s_client     crash) and possibly have unspecified other impact via a     DTLS packet, as demonstrated by a packet from a server     that uses a crafted server certificate. (CVE-2009-1379)

  - The TLS protocol, and the SSL protocol 3.0 and possibly     earlier, as used in Microsoft Internet Information     Services (IIS) 7.0, mod_ssl in the Apache HTTP Server     2.2.14 and earlier, OpenSSL before 0.9.8l, GnuTLS 2.8.5     and earlier, Mozilla Network Security Services (NSS)     3.12.4 and earlier, multiple Cisco products, and other     products, does not properly associate renegotiation     handshakes with an existing connection, which allows     man-in-the-middle attackers to insert data into HTTPS     sessions, and possibly other types of sessions protected     by TLS or SSL, by sending an unauthenticated request     that is processed retroactively by a server in a post-     renegotiation context, related to a plaintext     injection attack, aka the Project Mogul issue.
    (CVE-2009-3555)

  - Memory leak in the zlib_stateful_finish function in     crypto/comp/c_zlib.c in OpenSSL 0.9.8l and earlier and     1.0.0 Beta through Beta 4 allows remote attackers to     cause a denial of service (memory consumption) via     vectors that trigger incorrect calls to the     CRYPTO_cleanup_all_ex_data function, as demonstrated by     use of SSLv3 and PHP with the Apache HTTP Server, a     related issue to CVE-2008-1678. (CVE-2009-4355)

  - The Cryptographic Message Syntax (CMS) implementation in     crypto/cms/cms_asn1.c in OpenSSL before 0.9.8o and 1.x     before 1.0.0a does not properly handle structures that     contain OriginatorInfo, which allows context-dependent     attackers to modify invalid memory locations or conduct     double-free attacks, and possibly execute arbitrary     code, via unspecified vectors. (CVE-2010-0742)

  - RSA verification recovery in the EVP_PKEY_verify_recover     function in OpenSSL 1.x before 1.0.0a, as used by     pkeyutl and possibly other applications, returns     uninitialized memory upon failure, which might allow     context-dependent attackers to bypass intended key     requirements or obtain sensitive information via     unspecified vectors. NOTE: some of these details are     obtained from third party information. (CVE-2010-1633)

  - Multiple race conditions in ssl/t1_lib.c in OpenSSL     0.9.8f through 0.9.8o, 1.0.0, and 1.0.0a, when multi-     threading and internal caching are enabled on a TLS     server, might allow remote attackers to execute     arbitrary code via client data that triggers a heap-     based buffer overflow, related to (1) the TLS server     name extension and (2) elliptic curve cryptography.
    (CVE-2010-3864)

  - OpenSSL before 0.9.8q, and 1.0.x before 1.0.0c, when     SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG is enabled, does     not properly prevent modification of the ciphersuite in     the session cache, which allows remote attackers to     force the downgrade to an unintended cipher via vectors     involving sniffing network traffic to discover a session     identifier. (CVE-2010-4180)

  - ssl/t1_lib.c in OpenSSL 0.9.8h through 0.9.8q and 1.0.0     through 1.0.0c allows remote attackers to cause a denial     of service (crash), and possibly obtain sensitive     information in applications that use OpenSSL, via a     malformed ClientHello handshake message that triggers an     out-of-bounds memory access, aka OCSP stapling     vulnerability. (CVE-2011-0014)

  - crypto/x509/x509_vfy.c in OpenSSL 1.0.x before 1.0.0e     does not initialize certain structure members, which     makes it easier for remote attackers to bypass CRL     validation by using a nextUpdate value corresponding to     a time in the past. (CVE-2011-3207)

  - OpenSSL 0.9.8s and 1.0.0f does not properly support DTLS     applications, which allows remote attackers to cause a     denial of service (crash) via unspecified vectors     related to an out-of-bounds read. NOTE: this     vulnerability exists because of an incorrect fix for     CVE-2011-4108. (CVE-2012-0050)

  - The asn1_d2i_read_bio function in crypto/asn1/a_d2i_fp.c     in OpenSSL before 0.9.8v, 1.0.0 before 1.0.0i, and 1.0.1     before 1.0.1a does not properly interpret integer data,     which allows remote attackers to conduct buffer overflow     attacks, and cause a denial of service (memory     corruption) or possibly have unspecified other impact,     via crafted DER data, as demonstrated by an X.509     certificate or an RSA public key. (CVE-2012-2110)

  - The ssl3_take_mac function in ssl/s3_both.c in OpenSSL     1.0.1 before 1.0.1f allows remote TLS servers to cause a     denial of service (NULL pointer dereference and     application crash) via a crafted Next Protocol     Negotiation record in a TLS handshake. (CVE-2013-4353)

  - The ssl_get_algorithm2 function in ssl/s3_lib.c in     OpenSSL before 1.0.2 obtains a certain version number     from an incorrect data structure, which allows remote     attackers to cause a denial of service (daemon crash)     via crafted traffic from a TLS 1.2 client.
    (CVE-2013-6449)

  - The DTLS retransmission implementation in OpenSSL 1.0.0     before 1.0.0l and 1.0.1 before 1.0.1f does not properly     maintain data structures for digest and encryption     contexts, which might allow man-in-the-middle attackers     to trigger the use of a different context and cause a     denial of service (application crash) by interfering     with packet delivery, related to ssl/d1_both.c and     ssl/t1_enc.c. (CVE-2013-6450)

  - An information disclosure flaw was found in the way     OpenSSL handled TLS and DTLS Heartbeat Extension     packets. A malicious TLS or DTLS client or server could     send a specially crafted TLS or DTLS Heartbeat packet to     disclose a limited portion of memory per request from a     connected client or server. Note that the disclosed     portions of memory could potentially include sensitive     information such as private keys. (CVE-2014-0160)

  - A flaw was found in the way SSL 3.0 handled padding     bytes when decrypting messages encrypted using block     ciphers in cipher block chaining (CBC) mode. This flaw     allows a man-in-the-middle (MITM) attacker to decrypt a     selected byte of a cipher text in as few as 256 tries if     they are able to force a victim application to     repeatedly send the same data over newly created SSL 3.0     connections. (CVE-2014-3566)

  - A flaw was found in the way the DES/3DES cipher was used     as part of the TLS/SSL protocol. A man-in-the-middle     attacker could use this flaw to recover some plaintext     data by capturing large amounts of encrypted traffic     between TLS/SSL server and client if the communication     used a DES/3DES based ciphersuite. (CVE-2016-2183)

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

According to the versions of the openssl packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - A NULL pointer dereference flaw was found in OpenSSL's     X.509 certificate handling implementation. A specially     crafted X.509 certificate could cause an application     using OpenSSL to crash if the application attempted to     convert the certificate to a certificate     request.(CVE-2015-0288)

  - Off-by-one error in the DTLS implementation in OpenSSL     0.9.8 before 0.9.8f allows remote attackers to execute     arbitrary code via unspecified vectors.(CVE-2007-4995)

  - An integer underflow flaw, leading to a buffer     overflow, was found in the way OpenSSL decoded     malformed Base64-encoded inputs. An attacker able to     make an application using OpenSSL decode a specially     crafted Base64-encoded input (such as a PEM file) could     use this flaw to cause the application to crash. Note:
    this flaw is not exploitable via the TLS/SSL protocol     because the data being transferred is not     Base64-encoded.(CVE-2015-0292)

  - OpenSSL before 0.9.8q, and 1.0.x before 1.0.0c, when     SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG is enabled,     does not properly prevent modification of the     ciphersuite in the session cache, which allows remote     attackers to force the downgrade to an unintended     cipher via vectors involving sniffing network traffic     to discover a session identifier.(CVE-2010-4180)

  - OpenSSL before 0.9.8m does not check for a NULL return     value from bn_wexpand function calls in (1)     crypto/bn/bn_div.c, (2) crypto/bn/bn_gf2m.c, (3)     crypto/ec/ec2_smpl.c, and (4) engines/e_ubsec.c, which     has unspecified impact and context-dependent attack     vectors.(CVE-2009-3245)

  - The Cryptographic Message Syntax (CMS) implementation     in crypto/cms/cms_asn1.c in OpenSSL before 0.9.8o and     1.x before 1.0.0a does not properly handle structures     that contain OriginatorInfo, which allows     context-dependent attackers to modify invalid memory     locations or conduct double-free attacks, and possibly     execute arbitrary code, via unspecified     vectors.(CVE-2010-0742)

  - Race condition in the ssl3_read_bytes function in     s3_pkt.c in OpenSSL through 1.0.1g, when     SSL_MODE_RELEASE_BUFFERS is enabled, allows remote     attackers to inject data across sessions or cause a     denial of service (use-after-free and parsing error)     via an SSL connection in a multithreaded     environment.(CVE-2010-5298)

  - The BN_from_montgomery function in crypto/bn/bn_mont.c     in OpenSSL 0.9.8e and earlier does not properly perform     Montgomery multiplication, which might allow local     users to conduct a side-channel attack and retrieve RSA     private keys.(CVE-2007-3108)

  - A memory leak flaw was found in the way an OpenSSL     handled failed session ticket integrity checks. A     remote attacker could exhaust all available memory of     an SSL/TLS or DTLS server by sending a large number of     invalid session tickets to that server.(CVE-2014-3567)

  - It was discovered that OpenSSL would perform an ECDH     key exchange with a non-ephemeral key even when the     ephemeral ECDH cipher suite was selected. A malicious     server could make a TLS/SSL client using OpenSSL use a     weaker key exchange method than the one requested by     the user.(CVE-2014-3572)

  - A denial of service flaw was found in the way OpenSSL     handled certain DTLS ServerHello requests. A specially     crafted DTLS handshake packet could cause a DTLS client     using OpenSSL to crash.(CVE-2014-0221)

  - A NULL pointer dereference was found in the way OpenSSL     handled certain PKCS#7 inputs. An attacker able to make     an application using OpenSSL verify, decrypt, or parse     a specially crafted PKCS#7 input could cause that     application to crash. TLS/SSL clients and servers using     OpenSSL were not affected by this flaw.(CVE-2015-1790)

  - The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0     and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and     other products, do not properly consider timing     side-channel attacks on a MAC check requirement during     the processing of malformed CBC padding, which allows     remote attackers to conduct distinguishing attacks and     plaintext-recovery attacks via statistical analysis of     timing data for crafted packets, aka the 'Lucky     Thirteen' issue.(CVE-2013-0169)

  - OpenSSL 0.9.8i and earlier does not properly check the     return value from the EVP_VerifyFinal function, which     allows remote attackers to bypass validation of the     certificate chain via a malformed SSL/TLS signature for     DSA and ECDSA keys.(CVE-2008-5077)

  - The TLS protocol, and the SSL protocol 3.0 and possibly     earlier, as used in Microsoft Internet Information     Services (IIS) 7.0, mod_ssl in the Apache HTTP Server     2.2.14 and earlier, OpenSSL before 0.9.8l, GnuTLS 2.8.5     and earlier, Mozilla Network Security Services (NSS)     3.12.4 and earlier, multiple Cisco products, and other     products, does not properly associate renegotiation     handshakes with an existing connection, which allows     man-in-the-middle attackers to insert data into HTTPS     sessions, and possibly other types of sessions     protected by TLS or SSL, by sending an unauthenticated     request that is processed retroactively by a server in     a post-renegotiation context, related to a 'plaintext     injection' attack, aka the 'Project Mogul'     issue.(CVE-2009-3555)

  - Multiple memory leaks in the     dtls1_process_out_of_seq_message function in     ssl/d1_both.c in OpenSSL 0.9.8k and earlier 0.9.8     versions allow remote attackers to cause a denial of     service (memory consumption) via DTLS records that (1)     are duplicates or (2) have sequence numbers much     greater than current sequence numbers, aka 'DTLS     fragment handling memory leak.'(CVE-2009-1378)

  - The dtls1_retrieve_buffered_fragment function in     ssl/d1_both.c in OpenSSL before 1.0.0 Beta 2 allows     remote attackers to cause a denial of service (NULL     pointer dereference and daemon crash) via an     out-of-sequence DTLS handshake message, related to a     'fragment bug.'(CVE-2009-1387)

  - There is a carry propagating bug in the x86_64     Montgomery squaring procedure in OpenSSL before 1.0.2m     and 1.1.0 before 1.1.0g. No EC algorithms are affected.
    Analysis suggests that attacks against RSA and DSA as a     result of this defect would be very difficult to     perform and are not believed likely. Attacks against DH     are considered just feasible (although very difficult)     because most of the work necessary to deduce     information about a private key may be performed     offline. The amount of resources required for such an     attack would be very significant and likely only     accessible to a limited number of attackers. An     attacker would additionally need online access to an     unpatched system using the target private key in a     scenario with persistent DH parameters and a private     key that is shared between multiple clients. This only     affects processors that support the BMI1, BMI2 and ADX     extensions like Intel Broadwell (5th generation) and     later or AMD Ryzen.(CVE-2017-3736)

  - A flaw was discovered in the way OpenSSL handled DTLS     packets. A remote attacker could use this flaw to cause     a DTLS server or client using OpenSSL to crash or use     excessive amounts of memory.(CVE-2014-3505)

  - The dtls1_reassemble_fragment function in d1_both.c in     OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1     before 1.0.1h does not properly validate fragment     lengths in DTLS ClientHello messages, which allows     remote attackers to execute arbitrary code or cause a     denial of service (buffer overflow and application     crash) via a long non-initial fragment.(CVE-2014-0195)

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

The Cryptographic Message Syntax (CMS) implementation in crypto/cms/cms_asn1.c in OpenSSL before 0.9.8o and 1.x before 1.0.0a does not properly handle structures that contain OriginatorInfo, which allows context-dependent attackers to modify invalid memory locations or conduct double-free attacks, and possibly execute arbitrary code, via unspecified vectors. (CVE-2010-0742)

Impact

A locally authenticated user, with a role that allowsadvanced shell (bash) access, may be able to exploit OpenSSL to modify invalid memory locations or conduct double-free attacks, and execute arbitrary code.
However, affected F5 products that contain the vulnerable software component do not use the components in a way that exposes this vulnerability. There are no remote access vectors for this issue, and there is no data plane exposure.

The remote host is affected by the vulnerability described in GLSA-201110-01 (OpenSSL: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in OpenSSL. Please review       the CVE identifiers referenced below for details.
  Impact :

    A context-dependent attacker could cause a Denial of Service, possibly       execute arbitrary code, bypass intended key requirements, force the       downgrade to unintended ciphers, bypass the need for knowledge of shared       secrets and successfully authenticate, bypass CRL validation, or obtain       sensitive information in applications that use OpenSSL.
  Workaround :

    There is no known workaround at this time.

Minor update from upstream fixing two security vulnerabilities - CVE-2010-0742 and CVE-2010-1633. It is fully ABI compatible with openssl-1.0.0.

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.

Fix for an important security vulnerability CVE-2010-0742.

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.

According to its banner, the remote web server is running a version of OpenSSL older than 0.9.8o / 1.0.0a.  Such versions have the following vulnerabilities :

  - The mishandling of Cryptographic Message Syntax     structures containing an OriginatorInfo element can     lead to data being written to invalid memory addresses     or memory being freed up twice. (CVE-2010-0742)

  - An uninitialized buffer of undefined length is returned     when verification recovery fails for RSA keys. This     allows an attacker to bypass key checks in applications     calling the function EVP_PKEY_verify_recover(). Note     this function is not used by OpenSSLcode itself.     (CVE-2010-1633)

Versions of OpenSSL earlier than 0.9.8o and 1.0.0a are potentially affected by multiple vulnerabilities :

  - CMS structures containing 'OriginatorInfo' are mishandled which can cause the application to write to invalid memory addresses or free up memory twice.  Note that this only affects OpenSSL with CMS code present. (CVE-2010-0742)

  - When verification recovery fails for RSA keys, an uninitialized buffer with an undefined length is returned instead of an error code. Note that this only affects OpenSSL 1.0.0. (CVE-2010-1633)

ID	Name	Product	Family	Severity
127201	NewStart CGSL CORE 5.04 / MAIN 5.04 : openssl Multiple Vulnerabilities (NS-SA-2019-0033)	Nessus	NewStart CGSL Local Security Checks	high
125000	EulerOS Virtualization 3.0.1.0 : openssl (EulerOS-SA-2019-1547)	Nessus	Huawei Local Security Checks	medium
85890	F5 Networks BIG-IP : OpenSSL vulnerability (K17248)	Nessus	F5 Networks Local Security Checks	high
56425	GLSA-201110-01 : OpenSSL: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	critical
47546	Fedora 12 : openssl-1.0.0a-1.fc12 (2010-9639)	Nessus	Fedora Local Security Checks	high
47542	Fedora 13 : openssl-1.0.0a-1.fc13 (2010-9574)	Nessus	Fedora Local Security Checks	high
47534	Fedora 11 : openssl-0.9.8n-2.fc11 (2010-9421)	Nessus	Fedora Local Security Checks	high
46801	OpenSSL < 0.9.8o / 1.0.0a Multiple Vulnerabilities	Nessus	Web Servers	high
801057	OpenSSL < 0.9.8o / 1.0.0a Multiple Vulnerabilities	Log Correlation Engine	Web Servers	high
5559	OpenSSL < 0.9.8o / 1.0.0a Multiple Vulnerabilities	Nessus Network Monitor	Web Servers	high

Detections

Analytics

CVE-2010-0742

critical

Tenable Plugins

high

medium

high

critical

high

high

high

high

high

high