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.

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)

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.

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

According to the versions of the shim package installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - While parsing an IPAddressFamily extension in an X.509 certificate, it is possible to do a one-byte     overread. This would result in an incorrect text display of the certificate. This bug has been present     since 2006 and is present in all versions of OpenSSL before 1.0.2m and 1.1.0g. (CVE-2017-3735)

  - OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an 'error state' mechanism. The intent was that if     a fatal error occurred during a handshake then OpenSSL would move into the error state and would     immediately fail if you attempted to continue the handshake. This works as designed for the explicit     handshake functions (SSL_do_handshake(), SSL_accept() and SSL_connect()), however due to a bug it does not     work correctly if SSL_read() or SSL_write() is called directly. In that scenario, if the handshake fails     then a fatal error will be returned in the initial function call. If SSL_read()/SSL_write() is     subsequently called by the application for the same SSL object then it will succeed and the data is passed     without being decrypted/encrypted directly from the SSL/TLS record layer. In order to exploit this issue     an application bug would have to be present that resulted in a call to SSL_read()/SSL_write() being issued     after having already received a fatal error. OpenSSL version 1.0.2b-1.0.2m are affected. Fixed in OpenSSL     1.0.2n. OpenSSL 1.1.0 is not affected. (CVE-2017-3737)

  - During key agreement in a TLS handshake using a DH(E) based ciphersuite a malicious server can send a very     large prime value to the client. This will cause the client to spend an unreasonably long period of time     generating a key for this prime resulting in a hang until the client has finished. This could be exploited     in a Denial Of Service attack. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h). Fixed in OpenSSL     1.0.2p-dev (Affected 1.0.2-1.0.2o). (CVE-2018-0732)

  - The OpenSSL RSA Key generation algorithm has been shown to be vulnerable to a cache timing side channel     attack. An attacker with sufficient access to mount cache timing attacks during the RSA key generation     process could recover the private key. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h). Fixed in     OpenSSL 1.0.2p-dev (Affected 1.0.2b-1.0.2o). (CVE-2018-0737)

  - Constructed ASN.1 types with a recursive definition (such as can be found in PKCS7) could eventually     exceed the stack given malicious input with excessive recursion. This could result in a Denial Of Service     attack. There are no such structures used within SSL/TLS that come from untrusted sources so this is     considered safe. Fixed in OpenSSL 1.1.0h (Affected 1.1.0-1.1.0g). Fixed in OpenSSL 1.0.2o (Affected     1.0.2b-1.0.2n). (CVE-2018-0739)

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

  - The X.509 GeneralName type is a generic type for representing different types of names. One of those name     types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different     instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both     GENERAL_NAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may occur leading to a     possible denial of service attack. OpenSSL itself uses the GENERAL_NAME_cmp function for two purposes: 1)     Comparing CRL distribution point names between an available CRL and a CRL distribution point embedded in     an X509 certificate 2) When verifying that a timestamp response token signer matches the timestamp     authority name (exposed via the API functions TS_RESP_verify_response and TS_RESP_verify_token) If an     attacker can control both items being compared then that attacker could trigger a crash. For example if     the attacker can trick a client or server into checking a malicious certificate against a malicious CRL     then this may occur. Note that some applications automatically download CRLs based on a URL embedded in a     certificate. This checking happens prior to the signatures on the certificate and CRL being verified.
    OpenSSL's s_server, s_client and verify tools have support for the '-crl_download' option which implements     automatic CRL downloading and this attack has been demonstrated to work against those tools. Note that an     unrelated bug means that affected versions of OpenSSL cannot parse or construct correct encodings of     EDIPARTYNAME. However it is possible to construct a malformed EDIPARTYNAME that OpenSSL's parser will     accept and hence trigger this attack. All OpenSSL 1.1.1 and 1.0.2 versions are affected by this issue.
    Other OpenSSL releases are out of support and have not been checked. Fixed in OpenSSL 1.1.1i (Affected     1.1.1-1.1.1h). Fixed in OpenSSL 1.0.2x (Affected 1.0.2-1.0.2w). (CVE-2020-1971)

  - Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument     in some cases where the input length is close to the maximum permissable length for an integer on the     platform. In such cases the return value from the function call will be 1 (indicating success), but the     output length value will be negative. This could cause applications to behave incorrectly or crash.
    OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to     OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out     of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should     upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i).
    Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x). (CVE-2021-23840)

  - The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based     on the issuer and serial number data contained within an X509 certificate. However it fails to correctly     handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is     maliciously constructed). This may subsequently result in a NULL pointer deref and a crash leading to a     potential denial of service attack. The function X509_issuer_and_serial_hash() is never directly called by     OpenSSL itself so applications are only vulnerable if they use this function directly and they use it on     certificates that may have been obtained from untrusted sources. OpenSSL versions 1.1.1i and below are     affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x     and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving     public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should     upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected     1.0.2-1.0.2x). (CVE-2021-23841)

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

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 Redhat Enterprise Linux 8 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched.

  - openssl: Read buffer overruns processing ASN.1 strings (CVE-2021-3712)

  - Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to     timing attacks via a side-channel timing attack on 'port contention'. (CVE-2018-5407)

  - 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 Nessus has not tested for these issues but has instead relied on the package manager's report that the package is installed.

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.

ID	Name	Product	Family	Published	Updated	Severity
129635	Fedora 31 : 1:openssl (2019-9ab7ee6309)	Nessus	Fedora Local Security Checks	10/7/2019	4/19/2024	medium
130726	EulerOS 2.0 SP3 : openssl (EulerOS-SA-2019-2264)	Nessus	Huawei Local Security Checks	11/8/2019	5/18/2022	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
145975	CentOS 8 : openssl (CESA-2020:1840)	Nessus	CentOS Local Security Checks	2/1/2021	3/23/2021	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
155496	EulerOS Virtualization 2.9.0 : shim (EulerOS-SA-2021-2785)	Nessus	Huawei Local Security Checks	11/17/2021	11/23/2023	high
199379	RHEL 8 : openssl (Unpatched Vulnerability)	Nessus	Red Hat Local Security Checks	6/3/2024	6/15/2024	high
128115	OpenSSL 1.0.2 < 1.0.2t Multiple Vulnerabilities	Nessus	Web Servers	8/23/2019	6/7/2024	medium
128117	OpenSSL 1.1.0 < 1.1.0l Multiple Vulnerabilities	Nessus	Web Servers	8/23/2019	6/7/2024	medium

Detections

Analytics

Plugins Search

medium

medium

medium

medium

medium

medium

medium

high

high

medium

medium