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.

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)

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

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.

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.

This update for openssl 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).

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.

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.

This update for openssl-1_1 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)

This update was imported from the SUSE:SLE-15:Update update project.

The version of MySQL running on the remote host is 8.0.x prior to 8.0.19. It is, therefore, affected by multiple vulnerabilities, as noted in the January 2020 Critical Patch Update advisory:

  - Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Compiling (cURL)). Supported   versions that are affected are 5.7.28 and prior and 8.0.18 and prior. This easily exploitable vulnerability allows   unauthenticated attacker with network access via multiple protocols to compromise MySQL Server. Successful   attacks of this vulnerability can result in takeover of MySQL Server (CVE-2019-5482).

  - Vulnerability in the MySQL Client product of Oracle MySQL (component: C API). Supported versions that are   affected are 5.6.46 and prior, 5.7.28 and prior and 8.0.18 and prior. Difficult to exploit vulnerability allows   unauthenticated attacker with network access via multiple protocols to compromise MySQL Client. Successful   attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash   (complete DOS) of MySQL Client. (CVE-2020-2573)

  - Vulnerability in the MySQL Client product of Oracle MySQL (component: C API). Supported versions that are   affected are 5.6.46 and prior, 5.7.28 and prior and 8.0.18 and prior. Difficult to exploit vulnerability allows   unauthenticated attacker with network access via multiple protocols to compromise MySQL Client. Successful   attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash   (complete DOS) of MySQL Client. (CVE-2020-2574)

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 IBM Cognos Analytics installed on the remote host is prior to 11.1.7 FP8, 11.2.4 FP3, or 12.0.2. It is, therefore, affected by multiple vulnerabilities as referenced in the IBM Security Bulletin No. 7123154, including the following:

  - When deserializing untrusted or corrupted data, it is possible for a reader to consume memory beyond the   allowed constraints and thus lead to out of memory on the system. This issue affects Java applications using   Apache Avro Java SDK up to and including 1.11.2. Users should update to apache-avro version 1.11.3 which   addresses this issue. (CVE-2023-39410)

  - In order to decrypt SM2 encrypted data an application is expected to call the API function   EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the   'out' parameter can be NULL and, on exit, the 'outlen' parameter is populated with the buffer size required   to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call   EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the 'out' parameter. A bug in the   implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the   plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by   the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a   second time with a buffer that is too small. A malicious attacker who is able present SM2 content for   decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of   62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour   or causing the application to crash. The location of the buffer is application dependent but is typically   heap allocated. Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). (CVE-2021-3711)

  - SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization.
  Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using   SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization. We recommend   upgrading to version 2.0 and beyond. (CVE-2022-1471)

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

ID	Name	Product	Family	Published	Updated	Severity
132926	SUSE SLED12 / SLES12 Security Update : openssl-1_1 (SUSE-SU-2020:0099-1)	Nessus	SuSE Local Security Checks	1/15/2020	3/29/2024	medium
134510	EulerOS Virtualization for ARM 64 3.0.2.0 : openssl (EulerOS-SA-2020-1221)	Nessus	Huawei Local Security Checks	3/13/2020	5/18/2022	medium
136967	Ubuntu 16.04 LTS / 18.04 LTS : OpenSSL vulnerabilities (USN-4376-1)	Nessus	Ubuntu Local Security Checks	5/29/2020	8/27/2024	medium
140645	Ubuntu 16.04 LTS / 18.04 LTS : OpenSSL vulnerabilities (USN-4504-1)	Nessus	Ubuntu Local Security Checks	9/17/2020	8/27/2024	medium
145975	CentOS 8 : openssl (CESA-2020:1840)	Nessus	CentOS Local Security Checks	2/1/2021	3/23/2021	medium
180920	Oracle Linux 8 : openssl (ELSA-2020-1840)	Nessus	Oracle Linux Local Security Checks	9/7/2023	11/1/2024	medium
128115	OpenSSL 1.0.2 < 1.0.2t Multiple Vulnerabilities	Nessus	Web Servers	8/23/2019	10/23/2024	medium
128117	OpenSSL 1.1.0 < 1.1.0l Multiple Vulnerabilities	Nessus	Web Servers	8/23/2019	10/23/2024	medium
129155	SUSE SLES12 Security Update : openssl (SUSE-SU-2019:2413-1)	Nessus	SuSE Local Security Checks	9/23/2019	5/19/2022	medium
129362	Debian DLA-1932-1 : openssl security update	Nessus	Debian Local Security Checks	9/26/2019	4/23/2024	medium
129380	openSUSE Security Update : openssl-1_1 (openSUSE-2019-2189)	Nessus	SuSE Local Security Checks	9/26/2019	4/22/2024	medium
132958	MySQL 8.0.x < 8.0.19 Multiple Vulnerabilities (Jan 2020 CPU)	Nessus	Databases	1/16/2020	4/18/2025	critical
193868	IBM Cognos Analytics 11.1.1 < 11.1.7 FP8 / 11.2.x < 11.2.4 FP3 / 12.0.x < 12.0.2 (7123154)	Nessus	CGI abuses	4/25/2024	12/18/2024	critical

Detections

Analytics

Plugins Search

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

critical

critical