The version of OpenSSL installed on the remote host is prior to 1.1.0k. It is, therefore, affected by a vulnerability as referenced in the 1.1.0k advisory.

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

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

Joran Dirk Greef discovered that overly long nonces used with ChaCha20-Poly1305 were incorrectly processed and could result in nonce reuse. This doesn't affect OpenSSL-internal uses of ChaCha20-Poly1305 such as TLS.

The version of Oracle VM VirtualBox running on the remote host is 5.2.x prior to 5.2.32 or 6.0.x prior to 6.0.10. It is, therefore, affected by multiple vulnerabilities as noted in the July 2019 Critical Patch Update advisory:

  - An unspecified vulnerabilities in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core),     which could allow an authenticated, local attacker to takeover Oracle VM VirtualBox. (CVE-2019-2859, CVE-2019-2863,     CVE-2019-2866, CVE-2019-2867) 

  - An unspecified vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core     (OpenSSL)), which could allow an unauthenticated, remote attacker to create, delete of modify critical data Oracle     VM VirtualBox. (CVE-2019-1543)

  - An unspecified vulnerabilities in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core),     which could allow an authenticated, local attacker to cause a hang or repeatable crach (DoS) of Oracle VM     VirtualBox. (CVE-2019-2848, CVE-2019-2873, CVE-2019-2874, CVE-2019-2875, CVE-2019-2876, CVE-2019-2877)

This update for virtualbox to version 6.0.10 fixes the following issues :

Security issues fixed :

  - CVE-2019-2859 CVE-2019-2867 CVE-2019-2866 CVE-2019-2864     CVE-2019-2865 CVE-2019-1543 CVE-2019-2863 CVE-2019-2848     CVE-2019-2877 CVE-2019-2873 CVE-2019-2874 CVE-2019-2875     CVE-2019-2876 CVE-2019-2850 (boo#1141801)

Patch for CVE-2018-0737, CVE-2018-0732, CVE-2018-0734, CVE-2019-1552, CVE-2019-1559.

https://www.openssl.org/news/vulnerabilities.html

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

According to the version of the openssl110f packages installed, the EulerOS installation on the remote host is affected by the following vulnerability :

  - 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.(CVE-2019-1543)

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 version of OpenSSL installed on the remote host is prior to 1.1.1c. It is, therefore, affected by a vulnerability as referenced in the 1.1.1c advisory.

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

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

Oracle reports :

This Critical Patch Update contains 31 new security fixes for Oracle MySQL. 6 of these vulnerabilities may be remotely exploitable without authentication, i.e., may be exploited over a network without requiring user credentials.

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.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
125642	OpenSSL 1.1.0 < 1.1.0k Vulnerability	Nessus	Web Servers	2019/6/3	2025/3/4	high
126392	Debian DSA-4475-1 : openssl - security update	Nessus	Debian Local Security Checks	2019/7/2	2025/2/25	high
126778	Oracle VM VirtualBox 5.2.x < 5.2.32 / 6.0.x < 6.0.10 (Jul 2019 CPU)	Nessus	Misc.	2019/7/18	2022/5/19	high
127734	openSUSE Security Update : virtualbox (openSUSE-2019-1814)	Nessus	SuSE Local Security Checks	2019/8/12	2020/9/23	critical
129319	Fedora 30 : 1:compat-openssl10 (2019-00c25b9379)	Nessus	Fedora Local Security Checks	2019/9/25	2025/2/24	high
124614	EulerOS 2.0 SP3 : openssl110f (EulerOS-SA-2019-1328)	Nessus	Huawei Local Security Checks	2019/5/6	2025/3/13	high
125641	OpenSSL 1.1.1 < 1.1.1c Vulnerability	Nessus	Web Servers	2019/6/3	2025/3/4	high
130496	FreeBSD : MySQL -- Multiple vulerabilities (fc91f2ef-fd7b-11e9-a1c7-b499baebfeaf)	Nessus	FreeBSD Local Security Checks	2019/11/4	2024/4/16	high
129653	Fedora 31 : 1:compat-openssl10 (2019-db06efdea1)	Nessus	Fedora Local Security Checks	2019/10/7	2025/2/24	high
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

检测

插件搜索

high

high

high

critical

high

high

high

high

high

high