The function `OCSP_basic_verify` verifies the signer certificate on an OCSP response. In the case where the (non-default) flag OCSP_NOCHECKS is used then the response will be positive (meaning a successful verification) even in the case where the response signing certificate fails to verify. It is anticipated that most users of `OCSP_basic_verify` will not use the OCSP_NOCHECKS flag. In this case the `OCSP_basic_verify` function will return a negative value (indicating a fatal error) in the case of a certificate verification failure. The normal expected return value in this case would be 0. This issue also impacts the command line OpenSSL "ocsp" application. When verifying an ocsp response with the "-no_cert_checks" option the command line application will report that the verification is successful even though it has in fact failed. In this case the incorrect successful response will also be accompanied by error messages showing the failure and contradicting the apparently successful result. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2).

An update of the openssl package has been released.

The remote CentOS Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the openssl-3.0.7-18.el9 build changelog.

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

  - The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop     forever for non-prime moduli. Internally this function is used when parsing certificates that contain     elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point     encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has     invalid explicit curve parameters. Since certificate parsing happens prior to verification of the     certificate signature, any process that parses an externally supplied certificate may thus be subject to a     denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they     can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients     consuming server certificates - TLS servers consuming client certificates - Hosting providers taking     certificates or private keys from customers - Certificate authorities parsing certification requests from     subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that     use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS     issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate     which makes it slightly harder to trigger the infinite loop. However any operation which requires the     public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-     signed certificate to trigger the loop during verification of the certificate signature. This issue     affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the     15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected     1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc). (CVE-2022-0778)

  - c_rehash script allows command injection (CVE-2022-1292)

  - Signer certificate verification returned inaccurate response when using OCSP_NOCHECKS (CVE-2022-1343)

  - OPENSSL_LH_flush() breaks reuse of memory (CVE-2022-1473)

  - the c_rehash script allows command injection (CVE-2022-2068)

  - AES OCB fails to encrypt some bytes on 32-bit x86 (CVE-2022-2097)

  - X.509 Email Address Buffer Overflow (CVE-2022-3602, CVE-2022-3786)

  - A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occurs after certificate chain signature verification and requires either a CA to     have signed the malicious certificate or for the application to continue certificate verification despite     failure to construct a path to a trusted issuer. The read buffer overrun might result in a crash which     could lead to a denial of service attack. In theory it could also result in the disclosure of private     memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working     exploit leading to memory contents disclosure as of the time of release of this advisory. In a TLS client,     this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the     server requests client authentication and a malicious client connects. (CVE-2022-4203)

  - A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient     to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful     decryption an attacker would have to be able to send a very large number of trial messages for decryption.
    The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS     connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An     attacker that had observed a genuine connection between a client and a server could use this flaw to send     trial messages to the server and record the time taken to process them. After a sufficiently large number     of messages the attacker could recover the pre-master secret used for the original connection and thus be     able to decrypt the application data sent over that connection. (CVE-2022-4304)

  - The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the name (e.g.
    CERTIFICATE), any header data and the payload data. If the function succeeds then the name_out,     header and data arguments are populated with pointers to buffers containing the relevant decoded data.
    The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results     in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate     the header argument with a pointer to a buffer that has already been freed. If the caller also frees this     buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an     attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service     attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and     therefore these functions are also directly affected. These functions are also called indirectly by a     number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file()     which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the     caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations     include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL     asn1parse command line application is also impacted by this issue. (CVE-2022-4450)

  - The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is     primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may     also be called directly by end user applications. The function receives a BIO from the caller, prepends a     new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the     BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid,     the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this     case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal     pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then     a use-after-free will occur. This will most likely result in a crash. This scenario occurs directly in the     internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call     BIO_pop() on the BIO. This internal function is in turn called by the public API functions     PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1,     SMIME_write_CMS and SMIME_write_PKCS7. Other public API functions that may be impacted by this include     i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream. The OpenSSL     cms and smime command line applications are similarly affected. (CVE-2023-0215)

  - An invalid pointer dereference on read can be triggered when an application tries to load malformed PKCS7     data with the d2i_PKCS7(), d2i_PKCS7_bio() or d2i_PKCS7_fp() functions. The result of the dereference is     an application crash which could lead to a denial of service attack. The TLS implementation in OpenSSL     does not call this function however third party applications might call these functions on untrusted data.
    (CVE-2023-0216)

  - An invalid pointer dereference on read can be triggered when an application tries to check a malformed DSA     public key by the EVP_PKEY_public_check() function. This will most likely lead to an application crash.
    This function can be called on public keys supplied from untrusted sources which could allow an attacker     to cause a denial of service attack. The TLS implementation in OpenSSL does not call this function but     applications might call the function if there are additional security requirements imposed by standards     such as FIPS 140-3. (CVE-2023-0217)

  - There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName.
    X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME     incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently     interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL     checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may     allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or     enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate     chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these     inputs, the other input must already contain an X.400 address as a CRL distribution point, which is     uncommon. As such, this vulnerability is most likely to only affect applications which have implemented     their own functionality for retrieving CRLs over a network. (CVE-2023-0286)

  - A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or     signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library     but the implementation of the hash algorithm is not available the digest initialization will fail. There     is a missing check for the return value from the initialization function which later leads to invalid     usage of the digest API most likely leading to a crash. The unavailability of an algorithm can be caused     by using FIPS enabled configuration of providers or more commonly by not loading the legacy provider.
    PKCS7 data is processed by the SMIME library calls and also by the time stamp (TS) library calls. The TLS     implementation in OpenSSL does not call these functions however third party applications would be affected     if they call these functions to verify signatures on untrusted data. (CVE-2023-0401)

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

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2023-051 advisory.

    The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop     forever for non-prime moduli. Internally this function is used when parsing certificates that contain     elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point     encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has     invalid explicit curve parameters. Since certificate parsing happens prior to verification of the     certificate signature, any process that parses an externally supplied certificate may thus be subject to a     denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they     can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients     consuming server certificates - TLS servers consuming client certificates - Hosting providers taking     certificates or private keys from customers - Certificate authorities parsing certification requests from     subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that     use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS     issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate     which makes it slightly harder to trigger the infinite loop. However any operation which requires the     public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-     signed certificate to trigger the loop during verification of the certificate signature. This issue     affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the     15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected     1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc). (CVE-2022-0778) (CVE-2022-0778)

    The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. 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.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n).
    Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd). (CVE-2022-1292)

    The function `OCSP_basic_verify` verifies the signer certificate on an OCSP response. In the case where     the (non-default) flag OCSP_NOCHECKS is used then the response will be positive (meaning a successful     verification) even in the case where the response signing certificate fails to verify. It is anticipated     that most users of `OCSP_basic_verify` will not use the OCSP_NOCHECKS flag. In this case the     `OCSP_basic_verify` function will return a negative value (indicating a fatal error) in the case of a     certificate verification failure. The normal expected return value in this case would be 0. This issue     also impacts the command line OpenSSL ocsp application. When verifying an ocsp response with the
    -no_cert_checks option the command line application will report that the verification is successful even     though it has in fact failed. In this case the incorrect successful response will also be accompanied by     error messages showing the failure and contradicting the apparently successful result. Fixed in OpenSSL     3.0.3 (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1343)

    The OpenSSL 3.0 implementation of the RC4-MD5 ciphersuite incorrectly uses the AAD data as the MAC key.
    This makes the MAC key trivially predictable. An attacker could exploit this issue by performing a man-in-     the-middle attack to modify data being sent from one endpoint to an OpenSSL 3.0 recipient such that the     modified data would still pass the MAC integrity check. Note that data sent from an OpenSSL 3.0 endpoint     to a non-OpenSSL 3.0 endpoint will always be rejected by the recipient and the connection will fail at     that point. Many application protocols require data to be sent from the client to the server first.
    Therefore, in such a case, only an OpenSSL 3.0 server would be impacted when talking to a non-OpenSSL 3.0     client. If both endpoints are OpenSSL 3.0 then the attacker could modify data being sent in both     directions. In this case both clients and servers could be affected, regardless of the application     protocol. Note that in the absence of an attacker this bug means that an OpenSSL 3.0 endpoint     communicating with a non-OpenSSL 3.0 endpoint will fail to complete the handshake when using this     ciphersuite. The confidentiality of data is not impacted by this issue, i.e. an attacker cannot decrypt     data that has been encrypted using this ciphersuite - they can only modify it. In order for this attack to     work both endpoints must legitimately negotiate the RC4-MD5 ciphersuite. This ciphersuite is not compiled     by default in OpenSSL 3.0, and is not available within the default provider or the default ciphersuite     list. This ciphersuite will never be used if TLSv1.3 has been negotiated. In order for an OpenSSL 3.0     endpoint to use this ciphersuite the following must have occurred: 1) OpenSSL must have been compiled with     the (non-default) compile time option enable-weak-ssl-ciphers 2) OpenSSL must have had the legacy provider     explicitly loaded (either through application code or via configuration) 3) The ciphersuite must have been     explicitly added to the ciphersuite list 4) The libssl security level must have been set to 0 (default is     1) 5) A version of SSL/TLS below TLSv1.3 must have been negotiated 6) Both endpoints must negotiate the     RC4-MD5 ciphersuite in preference to any others that both endpoints have in common Fixed in OpenSSL 3.0.3     (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1434)

    The OPENSSL_LH_flush() function, which empties a hash table, contains a bug that breaks reuse of the     memory occuppied by the removed hash table entries. This function is used when decoding certificates or     keys. If a long lived process periodically decodes certificates or keys its memory usage will expand     without bounds and the process might be terminated by the operating system causing a denial of service.
    Also traversing the empty hash table entries will take increasingly more time. Typically such long lived     processes might be TLS clients or TLS servers configured to accept client certificate authentication. The     function was added in the OpenSSL 3.0 version thus older releases are not affected by the issue. Fixed in     OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1473)

    A flaw was found in OpenSSL. The issue in CVE-2022-1292 did not find other places in the `c_rehash` script     where it possibly passed the file names of certificates being hashed to a command executed through the     shell. Some operating systems distribute this script in a manner where it is automatically executed. On     these operating systems, this flaw allows an attacker to execute arbitrary commands with the privileges of     the script. (CVE-2022-2068)

    AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimized implementation will not encrypt     the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was     preexisting in the memory that wasn't written. In the special case of in place encryption, sixteen bytes     of the plaintext would be revealed. (CVE-2022-2097)

    A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occursafter certificate chain signature verification and requires either a CA to     have signed the malicious certificate or for the application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to     overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash     (causing a denial of service) or potentially remote code execution.. (CVE-2022-3602)

    A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occurs after certificate chain signature verification and requires either a CA to     have signed a malicious certificate or for an application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a     certificate to overflow an arbitrary number of bytes containing the . character (decimal 46) on the stack.
    This buffer overflow could result in a crash (causing a denial of service). (CVE-2022-3786)

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 AlmaLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2022:6224 advisory.

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

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2022-2022-195 advisory.

    A flaw was found in OpenSSL. The issue in CVE-2022-1292 did not find other places in the `c_rehash` script     where it possibly passed the file names of certificates being hashed to a command executed through the     shell. Some operating systems distribute this script in a manner where it is automatically executed. On     these operating systems, this flaw allows an attacker to execute arbitrary commands with the privileges of     the script. (CVE-2022-2068)

    AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimized implementation will not encrypt     the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was     preexisting in the memory that wasn't written. In the special case of in place encryption, sixteen bytes     of the plaintext would be revealed. (CVE-2022-2097)

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 version of openssl installed on the remote host is prior to 3.0.3-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2022-2022-104 advisory.

    The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. 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.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n).
    Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd). (CVE-2022-1292)

    The function `OCSP_basic_verify` verifies the signer certificate on an OCSP response. In the case where     the (non-default) flag OCSP_NOCHECKS is used then the response will be positive (meaning a successful     verification) even in the case where the response signing certificate fails to verify. It is anticipated     that most users of `OCSP_basic_verify` will not use the OCSP_NOCHECKS flag. In this case the     `OCSP_basic_verify` function will return a negative value (indicating a fatal error) in the case of a     certificate verification failure. The normal expected return value in this case would be 0. This issue     also impacts the command line OpenSSL ocsp application. When verifying an ocsp response with the
    -no_cert_checks option the command line application will report that the verification is successful even     though it has in fact failed. In this case the incorrect successful response will also be accompanied by     error messages showing the failure and contradicting the apparently successful result. Fixed in OpenSSL     3.0.3 (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1343)

    The OpenSSL 3.0 implementation of the RC4-MD5 ciphersuite incorrectly uses the AAD data as the MAC key.
    This makes the MAC key trivially predictable. An attacker could exploit this issue by performing a man-in-     the-middle attack to modify data being sent from one endpoint to an OpenSSL 3.0 recipient such that the     modified data would still pass the MAC integrity check. Note that data sent from an OpenSSL 3.0 endpoint     to a non-OpenSSL 3.0 endpoint will always be rejected by the recipient and the connection will fail at     that point. Many application protocols require data to be sent from the client to the server first.
    Therefore, in such a case, only an OpenSSL 3.0 server would be impacted when talking to a non-OpenSSL 3.0     client. If both endpoints are OpenSSL 3.0 then the attacker could modify data being sent in both     directions. In this case both clients and servers could be affected, regardless of the application     protocol. Note that in the absence of an attacker this bug means that an OpenSSL 3.0 endpoint     communicating with a non-OpenSSL 3.0 endpoint will fail to complete the handshake when using this     ciphersuite. The confidentiality of data is not impacted by this issue, i.e. an attacker cannot decrypt     data that has been encrypted using this ciphersuite - they can only modify it. In order for this attack to     work both endpoints must legitimately negotiate the RC4-MD5 ciphersuite. This ciphersuite is not compiled     by default in OpenSSL 3.0, and is not available within the default provider or the default ciphersuite     list. This ciphersuite will never be used if TLSv1.3 has been negotiated. In order for an OpenSSL 3.0     endpoint to use this ciphersuite the following must have occurred: 1) OpenSSL must have been compiled with     the (non-default) compile time option enable-weak-ssl-ciphers 2) OpenSSL must have had the legacy provider     explicitly loaded (either through application code or via configuration) 3) The ciphersuite must have been     explicitly added to the ciphersuite list 4) The libssl security level must have been set to 0 (default is     1) 5) A version of SSL/TLS below TLSv1.3 must have been negotiated 6) Both endpoints must negotiate the     RC4-MD5 ciphersuite in preference to any others that both endpoints have in common Fixed in OpenSSL 3.0.3     (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1434)

    The OPENSSL_LH_flush() function, which empties a hash table, contains a bug that breaks reuse of the     memory occuppied by the removed hash table entries. This function is used when decoding certificates or     keys. If a long lived process periodically decodes certificates or keys its memory usage will expand     without bounds and the process might be terminated by the operating system causing a denial of service.
    Also traversing the empty hash table entries will take increasingly more time. Typically such long lived     processes might be TLS clients or TLS servers configured to accept client certificate authentication. The     function was added in the OpenSSL 3.0 version thus older releases are not affected by the issue. Fixed in     OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1473)

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 Oracle Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2022-9751 advisory.

    - CVE-2022-2097: AES OCB fails to encrypt some bytes on 32-bit x86       Resolves: CVE-2022-2097
    - CVE-2022-2068: the c_rehash script allows command injection
    - CVE-2022-1473 openssl: OPENSSL_LH_flush() breaks reuse of memory
    - CVE-2022-1343 openssl: Signer certificate verification returned       inaccurate response when using OCSP_NOCHECKS
    - CVE-2022-1292 openssl: c_rehash script allows command injection

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 remote Oracle Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2022-6224 advisory.

    - CVE-2022-2097: AES OCB fails to encrypt some bytes on 32-bit x86       Resolves: CVE-2022-2097
    - CVE-2022-2068: the c_rehash script allows command injection
    - CVE-2022-1473 openssl: OPENSSL_LH_flush() breaks reuse of memory
    - CVE-2022-1343 openssl: Signer certificate verification returned       inaccurate response when using OCSP_NOCHECKS
    - CVE-2022-1292 openssl: c_rehash script allows command injection

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 remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2022:6224 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: c_rehash script allows command injection (CVE-2022-1292)

    * openssl: Signer certificate verification returns inaccurate response when using OCSP_NOCHECKS     (CVE-2022-1343)

    * openssl: OPENSSL_LH_flush() breaks reuse of memory (CVE-2022-1473)

    * openssl: the c_rehash script allows command injection (CVE-2022-2068)

    * openssl: AES OCB fails to encrypt some bytes (CVE-2022-2097)

    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.

    Bug Fix(es):

    * openssl occasionally sends internal error to gnutls when using FFDHE (BZ#2080323)

    * openssl req defaults to 3DES (BZ#2085499)

    * OpenSSL accepts custom elliptic curve parameters when p is large [rhel-9] (BZ#2085508)

    * OpenSSL mustn't work with ECDSA with explicit curve parameters in FIPS mode (BZ#2085521)

    * openssl s_server -groups secp256k1 in FIPS fails because X25519/X448 (BZ#2086554)

    * Converting FIPS power-on self test to KAT (BZ#2086866)

    * Small RSA keys work for some operations in FIPS mode (BZ#2091938)

    * FIPS provider doesn't block RSA encryption for key transport (BZ#2091977)

    * OpenSSL testsuite certificates expired (BZ#2095696)

    * [IBM 9.1 HW OPT] POWER10 performance enhancements for cryptography: OpenSSL (BZ#2103044)

    * [FIPS lab review] self-test (BZ#2112978)

    * [FIPS lab review] DH tuning (BZ#2115856)

    * [FIPS lab review] EC tuning (BZ#2115857)

    * [FIPS lab review] RSA tuning (BZ#2115858)

    * [FIPS lab review] RAND tuning (BZ#2115859)

    * [FIPS lab review] zeroization (BZ#2115861)

    * [FIPS lab review] HKDF limitations (BZ#2118388)

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 SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:2306-1 advisory.

  - The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. 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.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n).
    Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd). (CVE-2022-1292)

  - The function `OCSP_basic_verify` verifies the signer certificate on an OCSP response. In the case where     the (non-default) flag OCSP_NOCHECKS is used then the response will be positive (meaning a successful     verification) even in the case where the response signing certificate fails to verify. It is anticipated     that most users of `OCSP_basic_verify` will not use the OCSP_NOCHECKS flag. In this case the     `OCSP_basic_verify` function will return a negative value (indicating a fatal error) in the case of a     certificate verification failure. The normal expected return value in this case would be 0. This issue     also impacts the command line OpenSSL ocsp application. When verifying an ocsp response with the
    -no_cert_checks option the command line application will report that the verification is successful even     though it has in fact failed. In this case the incorrect successful response will also be accompanied by     error messages showing the failure and contradicting the apparently successful result. Fixed in OpenSSL     3.0.3 (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1343)

  - The OpenSSL 3.0 implementation of the RC4-MD5 ciphersuite incorrectly uses the AAD data as the MAC key.
    This makes the MAC key trivially predictable. An attacker could exploit this issue by performing a man-in-     the-middle attack to modify data being sent from one endpoint to an OpenSSL 3.0 recipient such that the     modified data would still pass the MAC integrity check. Note that data sent from an OpenSSL 3.0 endpoint     to a non-OpenSSL 3.0 endpoint will always be rejected by the recipient and the connection will fail at     that point. Many application protocols require data to be sent from the client to the server first.
    Therefore, in such a case, only an OpenSSL 3.0 server would be impacted when talking to a non-OpenSSL 3.0     client. If both endpoints are OpenSSL 3.0 then the attacker could modify data being sent in both     directions. In this case both clients and servers could be affected, regardless of the application     protocol. Note that in the absence of an attacker this bug means that an OpenSSL 3.0 endpoint     communicating with a non-OpenSSL 3.0 endpoint will fail to complete the handshake when using this     ciphersuite. The confidentiality of data is not impacted by this issue, i.e. an attacker cannot decrypt     data that has been encrypted using this ciphersuite - they can only modify it. In order for this attack to     work both endpoints must legitimately negotiate the RC4-MD5 ciphersuite. This ciphersuite is not compiled     by default in OpenSSL 3.0, and is not available within the default provider or the default ciphersuite     list. This ciphersuite will never be used if TLSv1.3 has been negotiated. In order for an OpenSSL 3.0     endpoint to use this ciphersuite the following must have occurred: 1) OpenSSL must have been compiled with     the (non-default) compile time option enable-weak-ssl-ciphers 2) OpenSSL must have had the legacy provider     explicitly loaded (either through application code or via configuration) 3) The ciphersuite must have been     explicitly added to the ciphersuite list 4) The libssl security level must have been set to 0 (default is     1) 5) A version of SSL/TLS below TLSv1.3 must have been negotiated 6) Both endpoints must negotiate the     RC4-MD5 ciphersuite in preference to any others that both endpoints have in common Fixed in OpenSSL 3.0.3     (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1434)

  - The OPENSSL_LH_flush() function, which empties a hash table, contains a bug that breaks reuse of the     memory occuppied by the removed hash table entries. This function is used when decoding certificates or     keys. If a long lived process periodically decodes certificates or keys its memory usage will expand     without bounds and the process might be terminated by the operating system causing a denial of service.
    Also traversing the empty hash table entries will take increasingly more time. Typically such long lived     processes might be TLS clients or TLS servers configured to accept client certificate authentication. The     function was added in the OpenSSL 3.0 version thus older releases are not affected by the issue. Fixed in     OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1473)

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

  - AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt     the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was     preexisting in the memory that wasn't written. In the special case of in place encryption, sixteen bytes     of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and     DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q     (Affected 1.1.1-1.1.1p). (CVE-2022-2097)

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 18.04 LTS / 20.04 LTS / 22.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-5402-1 advisory.

    Elison Niven discovered that OpenSSL incorrectly handled the c_rehash script. A local attacker could     possibly use this issue to execute arbitrary commands when c_rehash is run. (CVE-2022-1292)

    Raul Metsma discovered that OpenSSL incorrectly verified certain response signing certificates. A remote     attacker could possibly use this issue to spoof certain response signing certificates. This issue only     affected Ubuntu 22.04 LTS. (CVE-2022-1343)

    Tom Colley discovered that OpenSSL used the incorrect MAC key in the RC4-MD5 ciphersuite. In non-default     configurations were RC4-MD5 is enabled, a remote attacker could possibly use this issue to modify     encrypted communications. This issue only affected Ubuntu 22.04 LTS. (CVE-2022-1434)

    Aliaksei Levin discovered that OpenSSL incorrectly handled resources when decoding certificates and keys.
    A remote attacker could possibly use this issue to cause OpenSSL to consume resources, leading to a denial     of service. This issue only affected Ubuntu 22.04 LTS. (CVE-2022-1473)

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 version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the fceb2b08-cb76-11ec-a06f-d4c9ef517024 advisory.

  - The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. 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.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n).
    Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd). (CVE-2022-1292)

  - The function `OCSP_basic_verify` verifies the signer certificate on an OCSP response. In the case where     the (non-default) flag OCSP_NOCHECKS is used then the response will be positive (meaning a successful     verification) even in the case where the response signing certificate fails to verify. It is anticipated     that most users of `OCSP_basic_verify` will not use the OCSP_NOCHECKS flag. In this case the     `OCSP_basic_verify` function will return a negative value (indicating a fatal error) in the case of a     certificate verification failure. The normal expected return value in this case would be 0. This issue     also impacts the command line OpenSSL ocsp application. When verifying an ocsp response with the
    -no_cert_checks option the command line application will report that the verification is successful even     though it has in fact failed. In this case the incorrect successful response will also be accompanied by     error messages showing the failure and contradicting the apparently successful result. Fixed in OpenSSL     3.0.3 (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1343)

  - The OpenSSL 3.0 implementation of the RC4-MD5 ciphersuite incorrectly uses the AAD data as the MAC key.
    This makes the MAC key trivially predictable. An attacker could exploit this issue by performing a man-in-     the-middle attack to modify data being sent from one endpoint to an OpenSSL 3.0 recipient such that the     modified data would still pass the MAC integrity check. Note that data sent from an OpenSSL 3.0 endpoint     to a non-OpenSSL 3.0 endpoint will always be rejected by the recipient and the connection will fail at     that point. Many application protocols require data to be sent from the client to the server first.
    Therefore, in such a case, only an OpenSSL 3.0 server would be impacted when talking to a non-OpenSSL 3.0     client. If both endpoints are OpenSSL 3.0 then the attacker could modify data being sent in both     directions. In this case both clients and servers could be affected, regardless of the application     protocol. Note that in the absence of an attacker this bug means that an OpenSSL 3.0 endpoint     communicating with a non-OpenSSL 3.0 endpoint will fail to complete the handshake when using this     ciphersuite. The confidentiality of data is not impacted by this issue, i.e. an attacker cannot decrypt     data that has been encrypted using this ciphersuite - they can only modify it. In order for this attack to     work both endpoints must legitimately negotiate the RC4-MD5 ciphersuite. This ciphersuite is not compiled     by default in OpenSSL 3.0, and is not available within the default provider or the default ciphersuite     list. This ciphersuite will never be used if TLSv1.3 has been negotiated. In order for an OpenSSL 3.0     endpoint to use this ciphersuite the following must have occurred: 1) OpenSSL must have been compiled with     the (non-default) compile time option enable-weak-ssl-ciphers 2) OpenSSL must have had the legacy provider     explicitly loaded (either through application code or via configuration) 3) The ciphersuite must have been     explicitly added to the ciphersuite list 4) The libssl security level must have been set to 0 (default is     1) 5) A version of SSL/TLS below TLSv1.3 must have been negotiated 6) Both endpoints must negotiate the     RC4-MD5 ciphersuite in preference to any others that both endpoints have in common Fixed in OpenSSL 3.0.3     (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1434)

  - The OPENSSL_LH_flush() function, which empties a hash table, contains a bug that breaks reuse of the     memory occuppied by the removed hash table entries. This function is used when decoding certificates or     keys. If a long lived process periodically decodes certificates or keys its memory usage will expand     without bounds and the process might be terminated by the operating system causing a denial of service.
    Also traversing the empty hash table entries will take increasingly more time. Typically such long lived     processes might be TLS clients or TLS servers configured to accept client certificate authentication. The     function was added in the OpenSSL 3.0 version thus older releases are not affected by the issue. Fixed in     OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1473)

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 3.0.3. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.0.3 advisory.

  - The OPENSSL_LH_flush() function, which empties a hash table, contains a bug that breaks reuse of the     memory occuppied by the removed hash table entries. This function is used when decoding certificates or     keys. If a long lived process periodically decodes certificates or keys its memory usage will expand     without bounds and the process might be terminated by the operating system causing a denial of service.
    Also traversing the empty hash table entries will take increasingly more time. Typically such long lived     processes might be TLS clients or TLS servers configured to accept client certificate authentication. The     function was added in the OpenSSL 3.0 version thus older releases are not affected by the issue. Fixed in     OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1473)

  - The OpenSSL 3.0 implementation of the RC4-MD5 ciphersuite incorrectly uses the AAD data as the MAC key.
    This makes the MAC key trivially predictable. An attacker could exploit this issue by performing a man-in-     the-middle attack to modify data being sent from one endpoint to an OpenSSL 3.0 recipient such that the     modified data would still pass the MAC integrity check. Note that data sent from an OpenSSL 3.0 endpoint     to a non-OpenSSL 3.0 endpoint will always be rejected by the recipient and the connection will fail at     that point. Many application protocols require data to be sent from the client to the server first.
    Therefore, in such a case, only an OpenSSL 3.0 server would be impacted when talking to a non-OpenSSL 3.0     client. If both endpoints are OpenSSL 3.0 then the attacker could modify data being sent in both     directions. In this case both clients and servers could be affected, regardless of the application     protocol. Note that in the absence of an attacker this bug means that an OpenSSL 3.0 endpoint     communicating with a non-OpenSSL 3.0 endpoint will fail to complete the handshake when using this     ciphersuite. The confidentiality of data is not impacted by this issue, i.e. an attacker cannot decrypt     data that has been encrypted using this ciphersuite - they can only modify it. In order for this attack to     work both endpoints must legitimately negotiate the RC4-MD5 ciphersuite. This ciphersuite is not compiled     by default in OpenSSL 3.0, and is not available within the default provider or the default ciphersuite     list. This ciphersuite will never be used if TLSv1.3 has been negotiated. In order for an OpenSSL 3.0     endpoint to use this ciphersuite the following must have occurred: 1) OpenSSL must have been compiled with     the (non-default) compile time option enable-weak-ssl-ciphers 2) OpenSSL must have had the legacy provider     explicitly loaded (either through application code or via configuration) 3) The ciphersuite must have been     explicitly added to the ciphersuite list 4) The libssl security level must have been set to 0 (default is     1) 5) A version of SSL/TLS below TLSv1.3 must have been negotiated 6) Both endpoints must negotiate the     RC4-MD5 ciphersuite in preference to any others that both endpoints have in common Fixed in OpenSSL 3.0.3     (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1434)

  - The function `OCSP_basic_verify` verifies the signer certificate on an OCSP response. In the case where     the (non-default) flag OCSP_NOCHECKS is used then the response will be positive (meaning a successful     verification) even in the case where the response signing certificate fails to verify. It is anticipated     that most users of `OCSP_basic_verify` will not use the OCSP_NOCHECKS flag. In this case the     `OCSP_basic_verify` function will return a negative value (indicating a fatal error) in the case of a     certificate verification failure. The normal expected return value in this case would be 0. This issue     also impacts the command line OpenSSL ocsp application. When verifying an ocsp response with the
    -no_cert_checks option the command line application will report that the verification is successful even     though it has in fact failed. In this case the incorrect successful response will also be accompanied by     error messages showing the failure and contradicting the apparently successful result. Fixed in OpenSSL     3.0.3 (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1343)

  - The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. 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.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n).
    Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd). (CVE-2022-1292)

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	Severity
203159	Photon OS 4.0: Openssl PHSA-2022-4.0-0185	Nessus	PhotonOS Local Security Checks	critical
193921	CentOS 9 : openssl-3.0.7-18.el9	Nessus	CentOS Local Security Checks	critical
173139	Amazon Linux 2023 : openssl, openssl-devel, openssl-libs (ALAS2023-2023-051)	Nessus	Amazon Linux Local Security Checks	critical
167697	AlmaLinux 9 : openssl (ALSA-2022:6224)	Nessus	Alma Linux Local Security Checks	critical
167019	Amazon Linux 2022 : openssl, openssl-devel, openssl-libs (ALAS2022-2022-195)	Nessus	Amazon Linux Local Security Checks	critical
164775	Amazon Linux 2022 : openssl (ALAS2022-2022-104)	Nessus	Amazon Linux Local Security Checks	critical
164537	Oracle Linux 9 : openssl (ELSA-2022-9751)	Nessus	Oracle Linux Local Security Checks	critical
164518	Oracle Linux 9 : openssl (ELSA-2022-6224)	Nessus	Oracle Linux Local Security Checks	critical
164507	RHEL 9 : openssl (RHSA-2022:6224)	Nessus	Red Hat Local Security Checks	critical
162965	SUSE SLED15 / SLES15 Security Update : openssl-3 (SUSE-SU-2022:2306-1)	Nessus	SuSE Local Security Checks	critical
160502	Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS : OpenSSL vulnerabilities (USN-5402-1)	Nessus	Ubuntu Local Security Checks	critical
160481	FreeBSD : OpenSSL -- Multiple vulnerabilities (fceb2b08-cb76-11ec-a06f-d4c9ef517024)	Nessus	FreeBSD Local Security Checks	critical
160473	OpenSSL 3.0.0 < 3.0.3 Multiple Vulnerabilities	Nessus	Web Servers	critical

Detections

Analytics

CVE-2022-1343

medium

Tenable Plugins

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical