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

  - The OpenSSL DSA signature algorithm has been shown to     be vulnerable to a timing side channel attack. An     attacker could use variations in the signing algorithm     to recover the private key. Fixed in OpenSSL 1.1.1a     (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected     1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected     1.0.2-1.0.2p).(CVE-2018-0734)

  - Normally in OpenSSL EC groups always have a co-factor     present and this is used in side channel resistant code     paths. However, in some cases, it is possible to     construct a group using explicit parameters (instead of     using a named curve). In those cases it is possible     that such a group does not have the cofactor present.
    This can occur even where all the parameters match a     known named curve. If such a curve is used then OpenSSL     falls back to non-side channel resistant code paths     which may result in full key recovery during an ECDSA     signature operation. In order to be vulnerable an     attacker would have to have the ability to time the     creation of a large number of signatures where explicit     parameters with no co-factor present are in use by an     application using libcrypto. For the avoidance of doubt     libssl is not vulnerable because explicit parameters     are never used.(CVE-2019-1547)

  - In situations where an attacker receives automated     notification of the success or failure of a decryption     attempt an attacker, after sending a very large number     of messages to be decrypted, can recover a CMS/PKCS7     transported encryption key or decrypt any RSA encrypted     message that was encrypted with the public RSA key,     using a Bleichenbacher padding oracle attack.
    Applications are not affected if they use a certificate     together with the private RSA key to the CMS_decrypt or     PKCS7_decrypt functions to select the correct recipient     info to decrypt.(CVE-2019-1563)

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.

According to the versions of the compat-openssl10 package installed, the EulerOS Virtualization for ARM 64 installation on the remote host is affected by the following vulnerabilities :

  - The OpenSSL toolkit provides support for secure     communications between machines. This version of     OpenSSL package contains only the libraries and is     provided for compatibility with previous releases and     software that does not support compilation with     OpenSSL-1.1. Security Fix(es):OpenSSL has internal     defaults for a directory tree where it can find a     configuration file as well as certificates used for     verification in TLS. This directory is most commonly     referred to as OPENSSLDIR, and is configurable with the
    --prefix / --openssldir configuration options. For     OpenSSL versions 1.1.0 and 1.1.1, the mingw     configuration targets assume that resulting programs     and libraries are installed in a Unix-like environment     and the default prefix for program installation as well     as for OPENSSLDIR should be '/usr/local'. However,     mingw programs are Windows programs, and as such, find     themselves looking at sub-directories of     'C:/usr/local', which may be world writable, which     enables untrusted users to modify OpenSSL's default     configuration, insert CA certificates, modify (or even     replace) existing engine modules, etc. For OpenSSL     1.0.2, '/usr/local/ssl' is used as default for     OPENSSLDIR on all Unix and Windows targets, including     Visual C builds. However, some build instructions for     the diverse Windows targets on 1.0.2 encourage you to     specify your own --prefix. OpenSSL versions 1.1.1,     1.1.0 and 1.0.2 are affected by this issue. Due to the     limited scope of affected deployments this has been     assessed as low severity and therefore we are not     creating new releases at this time. Fixed in OpenSSL     1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l     (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t     (Affected 1.0.2-1.0.2s).Not found.(CVE-2019-1552)In     situations where an attacker receives automated     notification of the success or failure of a decryption     attempt an attacker, after sending a very large number     of messages to be decrypted, can recover a CMS/PKCS7     transported encryption key or decrypt any RSA encrypted     message that was encrypted with the public RSA key,     using a Bleichenbacher padding oracle attack.
    Applications are not affected if they use a certificate     together with the private RSA key to the CMS_decrypt or     PKCS7_decrypt functions to select the correct recipient     info to decrypt. Fixed in OpenSSL 1.1.1d (Affected     1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected     1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected     1.0.2-1.0.2s).(CVE-2019-1563)Normally in OpenSSL EC     groups always have a co-factor present and this is used     in side channel resistant code paths. However, in some     cases, it is possible to construct a group using     explicit parameters (instead of using a named curve).
    In those cases it is possible that such a group does     not have the cofactor present. This can occur even     where all the parameters match a known named curve. If     such a curve is used then OpenSSL falls back to     non-side channel resistant code paths which may result     in full key recovery during an ECDSA signature     operation. In order to be vulnerable an attacker would     have to have the ability to time the creation of a     large number of signatures where explicit parameters     with no co-factor present are in use by an application     using libcrypto. For the avoidance of doubt libssl is     not vulnerable because explicit parameters are never     used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).
    Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed     in OpenSSL 1.0.2t (Affected     1.0.2-1.0.2s).(CVE-2019-1547)

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.

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

  - In situations where an attacker receives automated     notification of the success or failure of a decryption     attempt an attacker, after sending a very large number     of messages to be decrypted, can recover a CMS/PKCS7     transported encryption key or decrypt any RSA encrypted     message that was encrypted with the public RSA key,     using a Bleichenbacher padding oracle attack.
    Applications are not affected if they use a certificate     together with the private RSA key to the CMS_decrypt or     PKCS7_decrypt functions to select the correct recipient     info to decrypt. Fixed in OpenSSL 1.1.1d (Affected     1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected     1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected     1.0.2-1.0.2s).(CVE-2019-1563)

  - OpenSSL 1.1.1 introduced a rewritten random number     generator (RNG). This was intended to include     protection in the event of a fork() system call in     order to ensure that the parent and child processes did     not share the same RNG state. However this protection     was not being used in the default case. A partial     mitigation for this issue is that the output from a     high precision timer is mixed into the RNG state so the     likelihood of a parent and child process sharing state     is significantly reduced. If an application already     calls OPENSSL_init_crypto() explicitly using     OPENSSL_INIT_ATFORK then this problem does not occur at     all. Fixed in OpenSSL 1.1.1d (Affected     1.1.1-1.1.1c).(CVE-2019-1549)

  - Normally in OpenSSL EC groups always have a co-factor     present and this is used in side channel resistant code     paths. However, in some cases, it is possible to     construct a group using explicit parameters (instead of     using a named curve). In those cases it is possible     that such a group does not have the cofactor present.
    This can occur even where all the parameters match a     known named curve. If such a curve is used then OpenSSL     falls back to non-side channel resistant code paths     which may result in full key recovery during an ECDSA     signature operation. In order to be vulnerable an     attacker would have to have the ability to time the     creation of a large number of signatures where explicit     parameters with no co-factor present are in use by an     application using libcrypto. For the avoidance of doubt     libssl is not vulnerable because explicit parameters     are never used. Fixed in OpenSSL 1.1.1d (Affected     1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected     1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected     1.0.2-1.0.2s).(CVE-2019-1547)

  - OpenSSL has internal defaults for a directory tree     where it can find a configuration file as well as     certificates used for verification in TLS. This     directory is most commonly referred to as OPENSSLDIR,     and is configurable with the --prefix / --openssldir     configuration options. For OpenSSL versions 1.1.0 and     1.1.1, the mingw configuration targets assume that     resulting programs and libraries are installed in a     Unix-like environment and the default prefix for     program installation as well as for OPENSSLDIR should     be '/usr/local'. However, mingw programs are Windows     programs, and as such, find themselves looking at     sub-directories of 'C:/usr/local', which may be world     writable, which enables untrusted users to modify     OpenSSL's default configuration, insert CA     certificates, modify (or even replace) existing engine     modules, etc. For OpenSSL 1.0.2, '/usr/local/ssl' is     used as default for OPENSSLDIR on all Unix and Windows     targets, including Visual C builds. However, some build     instructions for the diverse Windows targets on 1.0.2     encourage you to specify your own --prefix. OpenSSL     versions 1.1.1, 1.1.0 and 1.0.2 are affected by this     issue. Due to the limited scope of affected deployments     this has been assessed as low severity and therefore we     are not creating new releases at this time. Fixed in     OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in     OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in     OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).(CVE-2019-1552)

  - There is an overflow bug in the x64_64 Montgomery     squaring procedure used in exponentiation with 512-bit     moduli. No EC algorithms are affected. Analysis     suggests that attacks against 2-prime RSA1024, 3-prime     RSA1536, and DSA1024 as a result of this defect would     be very difficult to perform and are not believed     likely. Attacks against DH512 are considered just     feasible. However, for an attack the target would have     to re-use the DH512 private key, which is not     recommended anyway. Also applications directly using     the low level API BN_mod_exp may be affected if they     use BN_FLG_CONSTTIME. Fixed in OpenSSL 1.1.1e-dev     (Affected 1.1.1-1.1.1d). Fixed in OpenSSL 1.0.2u-dev     (Affected 1.0.2-1.0.2t).(CVE-2019-1551)

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 remote Ubuntu 16.04 LTS / 18.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-4376-1 advisory.

    Cesar Pereida Garca, Sohaib ul Hassan, Nicola Tuveri, Iaroslav Gridin, Alejandro Cabrera Aldaya, and     Billy Brumley discovered that OpenSSL incorrectly handled ECDSA signatures. An attacker could possibly use     this issue to perform a timing side-channel attack and recover private ECDSA keys. (CVE-2019-1547)

    Matt Caswell discovered that OpenSSL incorrectly handled the random number generator (RNG). This may     result in applications that use the fork() system call sharing the same RNG state between the parent and     the child, contrary to expectations. This issue only affected Ubuntu 18.04 LTS and Ubuntu 19.10.
    (CVE-2019-1549)

    Guido Vranken discovered that OpenSSL incorrectly performed the x86_64 Montgomery squaring procedure.
    While unlikely, a remote attacker could possibly use this issue to recover private keys. (CVE-2019-1551)

    Bernd Edlinger discovered that OpenSSL incorrectly handled certain decryption functions. In certain     scenarios, a remote attacker could possibly use this issue to perform a padding oracle attack and decrypt     traffic. (CVE-2019-1563)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

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

The remote Alibaba Cloud Linux 3 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALINUX3-SA-2022:0025 advisory.

    Package updates are available for Alibaba Cloud Linux 3 that fix the following vulnerabilities:

    CVE-2019-1543:
    ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC     7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce     length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly     allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any     additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are     unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and     integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then     makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then     such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored     bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that     relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any     OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long     nonce value. However user applications that use this cipher directly and set a non-default nonce length to     be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue.
    Due to the limited scope of affected deployments this has been assessed as low severity and therefore we     are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in     OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

    CVE-2019-1547:
    Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant     code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead     of using a named curve). In those cases it is possible that such a group does not have the cofactor     present. This can occur even where all the parameters match a known named curve. If such a curve is used     then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery     during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability     to time the creation of a large number of signatures where explicit parameters with no co-factor present     are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because     explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL     1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

    CVE-2019-1549:
    OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include     protection in the event of a fork() system call in order to ensure that the parent and child processes did     not share the same RNG state. However this protection was not being used in the default case. A partial     mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so     the likelihood of a parent and child process sharing state is significantly reduced. If an application     already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur     at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

    CVE-2019-1563:
    In situations where an attacker receives automated notification of the success or failure of a decryption     attempt an attacker, after sending a very large number of messages to be decrypted, can recover a     CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the     public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a     certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the     correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL     1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

    CVE-2021-3712:
    ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a     buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings     which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not     a strict requirement, ASN.1 strings that are parsed using OpenSSL's own d2i functions (and other similar     parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will     additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for     applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array     by directly setting the data and length fields in the ASN1_STRING array. This can also happen by using     the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to     assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for     strings that have been directly constructed. Where an application requests an ASN.1 structure to be     printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the     application without NUL terminating the data field, then a read buffer overrun can occur. The same thing     can also occur during name constraints processing of certificates (for example if a certificate has been     directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the     certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the     X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an     application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL     functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack).
    It could also result in the disclosure of private memory contents (such as private keys, or sensitive     plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected     1.0.2-1.0.2y).

    CVE-2022-0778:
    The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop     forever for non-prime moduli. Internally this function is used when parsing certificates that contain     elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point     encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has     invalid explicit curve parameters. Since certificate parsing happens prior to verification of the     certificate signature, any process that parses an externally supplied certificate may thus be subject to a     denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they     can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients     consuming server certificates - TLS servers consuming client certificates - Hosting providers taking     certificates or private keys from customers - Certificate authorities parsing certification requests from     subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that     use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS     issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate     which makes it slightly harder to trigger the infinite loop. However any operation which requires the     public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-     signed certificate to trigger the loop during verification of the certificate signature. This issue     affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the     15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected     1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc).

Tenable has extracted the preceding description block directly from the Alibaba Cloud Linux security advisory.

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

The version of Tencent Linux installed on the remote TencentOS Server 3 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2022:0025 advisory.

    Package updates are available for TencentOS Server 3 that fix the following vulnerabilities:

    CVE-2019-1547:
    Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant     code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead     of using a named curve). In those cases it is possible that such a group does not have the cofactor     present. This can occur even where all the parameters match a known named curve. If such a curve is used     then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery     during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability     to time the creation of a large number of signatures where explicit parameters with no co-factor present     are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because     explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL     1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

    CVE-2019-1549:
    OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include     protection in the event of a fork() system call in order to ensure that the parent and child processes did     not share the same RNG state. However this protection was not being used in the default case. A partial     mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so     the likelihood of a parent and child process sharing state is significantly reduced. If an application     already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur     at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

    CVE-2019-1563:
    In situations where an attacker receives automated notification of the success or failure of a decryption     attempt an attacker, after sending a very large number of messages to be decrypted, can recover a     CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the     public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a     certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the     correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL     1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

    CVE-2021-3712:
    ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a     buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings     which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not     a strict requirement, ASN.1 strings that are parsed using OpenSSL's own d2i functions (and other similar     parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will     additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for     applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array     by directly setting the data and length fields in the ASN1_STRING array. This can also happen by using     the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to     assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for     strings that have been directly constructed. Where an application requests an ASN.1 structure to be     printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the     application without NUL terminating the data field, then a read buffer overrun can occur. The same thing     can also occur during name constraints processing of certificates (for example if a certificate has been     directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the     certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the     X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an     application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL     functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack).
    It could also result in the disclosure of private memory contents (such as private keys, or sensitive     plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected     1.0.2-1.0.2y).

    CVE-2022-0778:
    The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop     forever for non-prime moduli. Internally this function is used when parsing certificates that contain     elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point     encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has     invalid explicit curve parameters. Since certificate parsing happens prior to verification of the     certificate signature, any process that parses an externally supplied certificate may thus be subject to a     denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they     can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients     consuming server certificates - TLS servers consuming client certificates - Hosting providers taking     certificates or private keys from customers - Certificate authorities parsing certification requests from     subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that     use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS     issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate     which makes it slightly harder to trigger the infinite loop. However any operation which requires the     public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-     signed certificate to trigger the loop during verification of the certificate signature. This issue     affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the     15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected     1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc).

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

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

The remote NewStart CGSL host, running version MAIN 6.06 (SP), has openssl packages installed that are affected by multiple vulnerabilities:

  - In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances     where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection     were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other     places in the script where the file names of certificates being hashed were possibly passed to a command     executed through the shell. This script is distributed by some operating systems in a manner where it is     automatically executed. On such operating systems, an attacker could execute arbitrary commands with the     privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the     OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in     OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze). (CVE-2022-2068)

  - The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat     Extension packets, which allows remote attackers to obtain sensitive information from process memory via     crafted packets that trigger a buffer over-read, as demonstrated by reading private keys, related to     d1_both.c and t1_lib.c, aka the Heartbleed bug. (CVE-2014-0160)

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

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
130680	EulerOS 2.0 SP5 : openssl110h (EulerOS-SA-2019-2218)	Nessus	Huawei Local Security Checks	2019/11/8	2022/5/18	medium
132815	EulerOS Virtualization for ARM 64 3.0.5.0 : compat-openssl10 (EulerOS-SA-2020-1061)	Nessus	Huawei Local Security Checks	2020/1/13	2022/5/18	medium
132817	EulerOS Virtualization for ARM 64 3.0.5.0 : openssl (EulerOS-SA-2020-1063)	Nessus	Huawei Local Security Checks	2020/1/13	2024/4/1	medium
136967	Ubuntu 16.04 LTS / 18.04 LTS : OpenSSL vulnerabilities (USN-4376-1)	Nessus	Ubuntu Local Security Checks	2020/5/29	2025/9/3	medium
236517	Alibaba Cloud Linux 3 : 0025: openssl (ALINUX3-SA-2022:0025)	Nessus	Alibaba Cloud Linux Local Security Checks	2025/5/14	2025/5/14	high
239220	TencentOS Server 3: openssl (TSSA-2022:0025)	Nessus	Tencent Local Security Checks	2025/6/16	2025/11/20	high
301194	NewStart CGSL MAIN 6.06 (SP) : openssl Multiple Vulnerabilities (NS-SA-2026-0004)	Nessus	NewStart CGSL Local Security Checks	2026/3/6	2026/3/10	high

检测

插件搜索

medium

medium

medium

medium

high

high

high