Synopsis
The remote service is affected by multiple vulnerabilities.
Description
The version of OpenSSL installed on the remote host is prior to 3.0.1. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.0.1 advisory.
  - There is a carry propagation bug in the MIPS32 and MIPS64 squaring procedure. Many EC algorithms are     affected, including some of the TLS 1.3 default curves. Impact was not analyzed in detail, because the     pre-requisites for attack are considered unlikely and include reusing private keys. Analysis suggests that     attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not     believed likely. Attacks against DH are considered just feasible (although very difficult) because most of     the work necessary to deduce information about a private key may be performed offline. The amount of     resources required for such an attack would be significant. However, for an attack on TLS to be     meaningful, the server would have to share the DH private key among multiple clients, which is no longer     an option since CVE-2016-0701. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0.0. It was     addressed in the releases of 1.1.1m and 3.0.1 on the 15th of December 2021. For the 1.0.2 release it is     addressed in git commit 6fc1aaaf3 that is available to premium support customers only. It will be made     available in 1.0.2zc when it is released. The issue only affects OpenSSL on MIPS platforms. Fixed in     OpenSSL 3.0.1 (Affected 3.0.0). Fixed in OpenSSL 1.1.1m (Affected 1.1.1-1.1.1l). Fixed in OpenSSL 1.0.2zc-     dev (Affected 1.0.2-1.0.2zb). (CVE-2021-4160)
  - Internally libssl in OpenSSL calls X509_verify_cert() on the client side to verify a certificate supplied     by a server. That function may return a negative return value to indicate an internal error (for example     out of memory). Such a negative return value is mishandled by OpenSSL and will cause an IO function (such     as SSL_connect() or SSL_do_handshake()) to not indicate success and a subsequent call to SSL_get_error()     to return the value SSL_ERROR_WANT_RETRY_VERIFY. This return value is only supposed to be returned by     OpenSSL if the application has previously called SSL_CTX_set_cert_verify_callback(). Since most     applications do not do this the SSL_ERROR_WANT_RETRY_VERIFY return value from SSL_get_error() will be     totally unexpected and applications may not behave correctly as a result. The exact behaviour will depend     on the application but it could result in crashes, infinite loops or other similar incorrect responses.
    This issue is made more serious in combination with a separate bug in OpenSSL 3.0 that will cause     X509_verify_cert() to indicate an internal error when processing a certificate chain. This will occur     where a certificate does not include the Subject Alternative Name extension but where a Certificate     Authority has enforced name constraints. This issue can occur even with valid chains. By combining the two     issues an attacker could induce incorrect, application dependent behaviour. Fixed in OpenSSL 3.0.1     (Affected 3.0.0). (CVE-2021-4044)
Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.
Solution
Upgrade to OpenSSL version 3.0.1 or later.
Plugin Details
File Name: openssl_3_0_1.nasl
Agent: windows, macosx, unix
Configuration: Enable thorough checks (optional)
Supported Sensors: Nessus Agent, Continuous Assessment, Nessus
Risk Information
Vector: CVSS2#AV:N/AC:M/Au:N/C:P/I:N/A:N
Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C
Vulnerability Information
CPE: cpe:/a:openssl:openssl
Required KB Items: installed_sw/OpenSSL
Exploit Ease: No known exploits are available
Patch Publication Date: 12/14/2021
Vulnerability Publication Date: 12/14/2021