The remote Oracle Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2020-1840 advisory.

    - fix CVE-2019-1547 - side-channel weak encryption vulnerability
    - fix CVE-2019-1563 - padding oracle in CMS API
    - fix CVE-2019-1549 - ensure fork safety of the DRBG

Tenable has extracted the preceding description block directly from the Oracle 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.

Minor update release 1.1.1d with low impact security fixes.

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.

Minor update release 1.1.1d with low impact security fixes.

----

Fix for TLS non-compliance causing server interoperability problems with golang TLS client.

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.

This update for openssl-1_1 fixes the following issues :

Security issue fixed :

CVE-2019-1551: Fixed an overflow bug in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli (bsc#1158809).

CVE-2019-1563: Fixed bleichenbacher attack against cms/pkcs7 encryptioon transported key (bsc#1150250).

CVE-2019-1551: Fixed integer overflow in RSAZ modular exponentiation on x86_64 (bsc#1158809).

CVE-2019-1549: Fixed fork problem with random generator (bsc#1150247).

CVE-2019-1547: Fixed EC_GROUP_set_generator side channel attack avoidance (bsc#1150003).

Bug fixes :

Ship the openssl 1.1.1 binary as openssl-1_1, and make it installable in parallel with the system openssl (bsc#1140277).

Update to 1.1.1d (bsc#1133925, jsc#SLE-6430).

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 version of openssl11 installed on the remote host is prior to 1.1.1c-15. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2020-1456 advisory.

    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)

    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)

Tenable has extracted the preceding description block directly from the tested product 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 Redhat Enterprise Linux 6 / 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2020:1337 advisory.

    This release adds the new Apache HTTP Server 2.4.37 Service Pack 2 packages that are part of the JBoss     Core Services offering.

    This release serves as a replacement for Red Hat JBoss Core Services Pack Apache Server 2.4.37 Service     Pack 1 and includes bug fixes and enhancements. Refer to the Release Notes for information on the most     significant bug fixes and enhancements included in this release.

    Security Fix(es):

    * openssl: side-channel weak encryption vulnerability (CVE-2019-1547)

    * httpd: memory corruption on early pushes (CVE-2019-10081)

    * httpd: read-after-free in h2 connection shutdown (CVE-2019-10082)

    * httpd: null-pointer dereference in mod_remoteip (CVE-2019-10097)

    * openssl: information disclosure in fork() (CVE-2019-1549)

    * openssl: information disclosure in PKCS7_dataDecode and CMS_decrypt_set1_pkey (CVE-2019-1563)

    * httpd: limited cross-site scripting in mod_proxy error page (CVE-2019-10092)

    * httpd: mod_rewrite potential open redirect (CVE-2019-10098)

    * httpd: mod_rewrite configurations vulnerable to open redirect(CVE-2020-1927)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise 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 OpenSSL project reports :

ECDSA remote timing attack (CVE-2019-1547) [Low]

Fork Protection (CVE-2019-1549) [Low] (OpenSSL 1.1.1 only)

The version of OpenSSL installed on the remote host is prior to 1.1.1d. It is, therefore, affected by multiple vulnerabilities as referenced in the 1.1.1d advisory.

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

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

An update of the nxtgn package has been released.

The remote CentOS Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the CESA-2020:1840 advisory.

  - openssl: side-channel weak encryption vulnerability (CVE-2019-1547)

  - openssl: information disclosure in fork() (CVE-2019-1549)

  - openssl: information disclosure in PKCS7_dataDecode and CMS_decrypt_set1_pkey (CVE-2019-1563)

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 installation on the remote host is affected by the following vulnerabilities :

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

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

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

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 MiracleLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the AXSA:2020-289:02 advisory.

    * openssl: side-channel weak encryption vulnerability (CVE-2019-1547)
      * openssl: information disclosure in fork() (CVE-2019-1549)
      * openssl: information disclosure in PKCS7_dataDecode and CMS_decrypt_set1_pkey (CVE-2019-1563)

Tenable has extracted the preceding description block directly from the MiracleLinux 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 Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2020:1840 advisory.

    OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS)     protocols, as well as a full-strength general-purpose cryptography library.

    Security Fix(es):

    * openssl: side-channel weak encryption vulnerability (CVE-2019-1547)

    * openssl: information disclosure in fork() (CVE-2019-1549)

    * openssl: information disclosure in PKCS7_dataDecode and CMS_decrypt_set1_pkey (CVE-2019-1563)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 8.2 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise 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, 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	名称	产品	系列	发布时间	最近更新时间	严重程度
180920	Oracle Linux 8 : openssl (ELSA-2020-1840)	Nessus	Oracle Linux Local Security Checks	2023/9/7	2024/11/1	medium
129327	Fedora 30 : 1:openssl (2019-d15aac6c4e)	Nessus	Fedora Local Security Checks	2019/9/25	2024/4/23	medium
129513	Fedora 29 : 1:openssl (2019-d51641f152)	Nessus	Fedora Local Security Checks	2019/10/2	2024/4/22	medium
132926	SUSE SLED12 / SLES12 Security Update : openssl-1_1 (SUSE-SU-2020:0099-1)	Nessus	SuSE Local Security Checks	2020/1/15	2024/3/29	medium
138622	Amazon Linux 2 : openssl11 (ALAS-2020-1456)	Nessus	Amazon Linux Local Security Checks	2020/7/20	2024/12/11	medium
135235	RHEL 6 / 7 : Red Hat JBoss Core Services Apache HTTP Server 2.4.37 SP2 (RHSA-2020:1337)	Nessus	Red Hat Local Security Checks	2020/4/6	2024/11/7	critical
128746	FreeBSD : OpenSSL -- Multiple vulnerabilities (9e0c6f7a-d46d-11e9-a1c7-b499baebfeaf)	Nessus	FreeBSD Local Security Checks	2019/9/12	2024/4/26	medium
128116	OpenSSL 1.1.1 < 1.1.1d Multiple Vulnerabilities	Nessus	Web Servers	2019/8/23	2024/10/23	medium
130110	Photon OS 3.0: Nxtgn PHSA-2019-3.0-0033	Nessus	PhotonOS Local Security Checks	2019/10/22	2024/7/23	medium
129635	Fedora 31 : 1:openssl (2019-9ab7ee6309)	Nessus	Fedora Local Security Checks	2019/10/7	2024/4/19	medium
145975	CentOS 8 : openssl (CESA-2020:1840)	Nessus	CentOS Local Security Checks	2021/2/1	2021/3/23	medium
130806	EulerOS 2.0 SP8 : openssl (EulerOS-SA-2019-2097)	Nessus	Huawei Local Security Checks	2019/11/12	2024/4/12	medium
293934	MiracleLinux 8 : openssl-1.1.1c-15.el8 (AXSA:2020-289:02)	Nessus	Miracle Linux Local Security Checks	2026/1/20	2026/1/20	medium
143010	RHEL 8 : openssl (RHSA-2020:1840)	Nessus	Red Hat Local Security Checks	2020/11/18	2024/11/7	medium
266257	NewStart CGSL MAIN 6.06 : openssl Multiple Vulnerabilities (NS-SA-2025-0211)	Nessus	NewStart CGSL Local Security Checks	2025/9/30	2026/1/21	high

检测

插件搜索

medium

medium

medium

medium

medium

critical

medium

medium

medium

medium

medium

medium

medium

medium

high