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

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

Two security vulnerabilities were found in OpenSSL, the Secure Sockets Layer toolkit.

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.

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.

For Debian 8 'Jessie', these problems have been fixed in version 1.0.1t-1+deb8u12.

We recommend that you upgrade your openssl packages.

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

Two security issues were discovered in OpenSSL: A timing attack against ECDSA and a padding oracle in PKCS7_dataDecode() and CMS_decrypt_set1_pkey().

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

OpenSSL Security Advisory [10 September 2019]

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

CVE-2019-1563: Fixed Bleichenbacher attack against cms/pkcs7 encryption transported key (bsc#1150250)

In addition fixed invalid curve attacks by validating that an EC point lies on the curve (bsc#1131291).

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.

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.

The remote Ubuntu 16.04 LTS / 18.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-4504-1 advisory.

    Robert Merget, Marcus Brinkmann, Nimrod Aviram, and Juraj Somorovsky discovered that certain Diffie-     Hellman ciphersuites in the TLS specification and implemented by OpenSSL contained a flaw. A remote     attacker could possibly use this issue to eavesdrop on encrypted communications. This was fixed in this     update by removing the insecure ciphersuites from OpenSSL. (CVE-2020-1968)

    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. This issue only     affected Ubuntu 18.04 LTS. (CVE-2019-1547)

    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. This issue only     affected Ubuntu 18.04 LTS. (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. This issue only affected Ubuntu 18.04 LTS. (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 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.

ID	名前	製品	ファミリー	公開日	更新日	深刻度
128115	OpenSSL 1.0.2 < 1.0.2t Multiple Vulnerabilities	Nessus	Web Servers	2019/8/23	2024/10/23	medium
128117	OpenSSL 1.1.0 < 1.1.0l Multiple Vulnerabilities	Nessus	Web Servers	2019/8/23	2024/10/23	medium
129362	Debian DLA-1932-1 : openssl security update	Nessus	Debian Local Security Checks	2019/9/26	2024/4/23	medium
129507	Debian DSA-4540-1 : openssl1.0 - security update	Nessus	Debian Local Security Checks	2019/10/2	2024/4/22	medium
129528	SUSE SLED12 / SLES12 Security Update : openssl-1_0_0 (SUSE-SU-2019:2504-1)	Nessus	SuSE Local Security Checks	2019/10/2	2022/5/19	medium
129635	Fedora 31 : 1:openssl (2019-9ab7ee6309)	Nessus	Fedora Local Security Checks	2019/10/7	2024/4/19	medium
129676	SUSE SLED15 / SLES15 Security Update : openssl-1_0_0 (SUSE-SU-2019:2561-1)	Nessus	SuSE Local Security Checks	2019/10/7	2022/5/19	medium
140645	Ubuntu 16.04 LTS / 18.04 LTS : OpenSSL vulnerabilities (USN-4504-1)	Nessus	Ubuntu Local Security Checks	2020/9/17	2025/9/3	medium
145975	CentOS 8 : openssl (CESA-2020:1840)	Nessus	CentOS Local Security Checks	2021/2/1	2021/3/23	medium

検出

プラグインの検索

medium

medium

medium

medium

medium

medium

medium

medium

medium