The version of OpenSSL installed on the remote host is prior to 3.0.14. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.0.14 advisory.

  - Issue summary: Checking excessively long DSA keys or parameters may be very slow. Impact summary:
    Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA     public key or DSA parameters may experience long delays. Where the key or parameters that are being     checked have been obtained from an untrusted source this may lead to a Denial of Service. The functions     EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those     computations take a long time if the modulus (`p` parameter) is too large. Trying to use a very large     modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in     length for signature verification. However the key and parameter check functions do not limit the modulus     size when performing the checks. An application that calls EVP_PKEY_param_check() or     EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be     vulnerable to a Denial of Service attack. These functions are not called by OpenSSL itself on untrusted     DSA keys so only applications that directly call these functions may be vulnerable. Also vulnerable are     the OpenSSL pkey and pkeyparam command line applications when using the `-check` option. The OpenSSL     SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are affected     by this issue. (CVE-2024-4603)

  - Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when     processing TLSv1.3 sessions Impact summary: An attacker may exploit certain server configurations to     trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3     if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured     and the default anti-replay protection is in use). In this case, under certain conditions, the session     cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache     will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario     for this failure to force a Denial of Service. It may also happen by accident in normal operation. This     issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in     3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
    (CVE-2024-2511)

  - Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was     previously freed in some situations Impact summary: A use after free can have a range of potential     consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only     applications that directly call the SSL_free_buffers function are affected by this issue. Applications     that do not call this function are not vulnerable. Our investigations indicate that this function is     rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer     used when processing an incoming record from the network. The call is only expected to succeed if the     buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even     when still in use. The first scenario occurs where a record header has been received from the network and     processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers     will succeed even though a record has only been partially processed and the buffer is still in use. The     second scenario occurs where a full record containing application data has been received and processed by     OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed     even though the buffer is still in use. While these scenarios could occur accidentally during normal     operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware     of this issue being actively exploited. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this     issue. Found by William Ahern (Akamai). Fix developed by Matt Caswell. Fix developed by Watson Ladd     (Akamai). Fixed in OpenSSL 3.3.1 (Affected since 3.3.0). (CVE-2024-4741)

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 a vulnerability as referenced in the b88aa380-1442-11ef-a490-84a93843eb75 advisory.

  - Issue summary: Checking excessively long DSA keys or parameters may be very slow. Impact summary:
    Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA     public key or DSA parameters may experience long delays. Where the key or parameters that are being     checked have been obtained from an untrusted source this may lead to a Denial of Service. The functions     EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those     computations take a long time if the modulus (`p` parameter) is too large. Trying to use a very large     modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in     length for signature verification. However the key and parameter check functions do not limit the modulus     size when performing the checks. An application that calls EVP_PKEY_param_check() or     EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be     vulnerable to a Denial of Service attack. These functions are not called by OpenSSL itself on untrusted     DSA keys so only applications that directly call these functions may be vulnerable. Also vulnerable are     the OpenSSL pkey and pkeyparam command line applications when using the `-check` option. The OpenSSL     SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are affected     by this issue. (CVE-2024-4603)

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

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2024:1789-1 advisory.

    - CVE-2024-4603: Fixed DSA parameter checks for excessive sizes before validating (bsc#1224388).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for this issue 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.2.2. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.2.2 advisory.

  - Issue summary: Checking excessively long DSA keys or parameters may be very slow. Impact summary:
    Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA     public key or DSA parameters may experience long delays. Where the key or parameters that are being     checked have been obtained from an untrusted source this may lead to a Denial of Service. The functions     EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those     computations take a long time if the modulus (`p` parameter) is too large. Trying to use a very large     modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in     length for signature verification. However the key and parameter check functions do not limit the modulus     size when performing the checks. An application that calls EVP_PKEY_param_check() or     EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be     vulnerable to a Denial of Service attack. These functions are not called by OpenSSL itself on untrusted     DSA keys so only applications that directly call these functions may be vulnerable. Also vulnerable are     the OpenSSL pkey and pkeyparam command line applications when using the `-check` option. The OpenSSL     SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are affected     by this issue. (CVE-2024-4603)

  - Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when     processing TLSv1.3 sessions Impact summary: An attacker may exploit certain server configurations to     trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3     if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured     and the default anti-replay protection is in use). In this case, under certain conditions, the session     cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache     will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario     for this failure to force a Denial of Service. It may also happen by accident in normal operation. This     issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in     3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
    (CVE-2024-2511)

  - Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was     previously freed in some situations Impact summary: A use after free can have a range of potential     consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only     applications that directly call the SSL_free_buffers function are affected by this issue. Applications     that do not call this function are not vulnerable. Our investigations indicate that this function is     rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer     used when processing an incoming record from the network. The call is only expected to succeed if the     buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even     when still in use. The first scenario occurs where a record header has been received from the network and     processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers     will succeed even though a record has only been partially processed and the buffer is still in use. The     second scenario occurs where a full record containing application data has been received and processed by     OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed     even though the buffer is still in use. While these scenarios could occur accidentally during normal     operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware     of this issue being actively exploited. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this     issue. Found by William Ahern (Akamai). Fix developed by Matt Caswell. Fix developed by Watson Ladd     (Akamai). Fixed in OpenSSL 3.3.1 (Affected since 3.3.0). (CVE-2024-4741)

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

  - Issue summary: Checking excessively long DSA keys or parameters may be very slow. Impact summary:
    Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA     public key or DSA parameters may experience long delays. Where the key or parameters that are being     checked have been obtained from an untrusted source this may lead to a Denial of Service. The functions     EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those     computations take a long time if the modulus (`p` parameter) is too large. Trying to use a very large     modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in     length for signature verification. However the key and parameter check functions do not limit the modulus     size when performing the checks. An application that calls EVP_PKEY_param_check() or     EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be     vulnerable to a Denial of Service attack. These functions are not called by OpenSSL itself on untrusted     DSA keys so only applications that directly call these functions may be vulnerable. Also vulnerable are     the OpenSSL pkey and pkeyparam command line applications when using the `-check` option. The OpenSSL     SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are affected     by this issue. (CVE-2024-4603)

  - Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when     processing TLSv1.3 sessions Impact summary: An attacker may exploit certain server configurations to     trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3     if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured     and the default anti-replay protection is in use). In this case, under certain conditions, the session     cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache     will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario     for this failure to force a Denial of Service. It may also happen by accident in normal operation. This     issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in     3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
    (CVE-2024-2511)

  - Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was     previously freed in some situations Impact summary: A use after free can have a range of potential     consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only     applications that directly call the SSL_free_buffers function are affected by this issue. Applications     that do not call this function are not vulnerable. Our investigations indicate that this function is     rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer     used when processing an incoming record from the network. The call is only expected to succeed if the     buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even     when still in use. The first scenario occurs where a record header has been received from the network and     processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers     will succeed even though a record has only been partially processed and the buffer is still in use. The     second scenario occurs where a full record containing application data has been received and processed by     OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed     even though the buffer is still in use. While these scenarios could occur accidentally during normal     operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware     of this issue being actively exploited. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this     issue. Found by William Ahern (Akamai). Fix developed by Matt Caswell. Fix developed by Watson Ladd     (Akamai). Fixed in OpenSSL 3.3.1 (Affected since 3.3.0). (CVE-2024-4741)

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

  - Issue summary: Checking excessively long DSA keys or parameters may be very slow. Impact summary:
    Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA     public key or DSA parameters may experience long delays. Where the key or parameters that are being     checked have been obtained from an untrusted source this may lead to a Denial of Service. The functions     EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those     computations take a long time if the modulus (`p` parameter) is too large. Trying to use a very large     modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in     length for signature verification. However the key and parameter check functions do not limit the modulus     size when performing the checks. An application that calls EVP_PKEY_param_check() or     EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be     vulnerable to a Denial of Service attack. These functions are not called by OpenSSL itself on untrusted     DSA keys so only applications that directly call these functions may be vulnerable. Also vulnerable are     the OpenSSL pkey and pkeyparam command line applications when using the `-check` option. The OpenSSL     SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are affected     by this issue. (CVE-2024-4603)

  - Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was     previously freed in some situations Impact summary: A use after free can have a range of potential     consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only     applications that directly call the SSL_free_buffers function are affected by this issue. Applications     that do not call this function are not vulnerable. Our investigations indicate that this function is     rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer     used when processing an incoming record from the network. The call is only expected to succeed if the     buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even     when still in use. The first scenario occurs where a record header has been received from the network and     processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers     will succeed even though a record has only been partially processed and the buffer is still in use. The     second scenario occurs where a full record containing application data has been received and processed by     OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed     even though the buffer is still in use. While these scenarios could occur accidentally during normal     operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware     of this issue being actively exploited. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this     issue. Found by William Ahern (Akamai). Fix developed by Matt Caswell. Fix developed by Watson Ladd     (Akamai). Fixed in OpenSSL 3.1.6 (Affected since 3.1.0). (CVE-2024-4741)

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 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the openssl-3.2.2-1.el9 build changelog.

  - Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when     processing TLSv1.3 sessions Impact summary: An attacker may exploit certain server configurations to     trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3     if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured     and the default anti-replay protection is in use). In this case, under certain conditions, the session     cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache     will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario     for this failure to force a Denial of Service. It may also happen by accident in normal operation. This     issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in     3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
    (CVE-2024-2511)

  - Issue summary: Checking excessively long DSA keys or parameters may be very slow. Impact summary:
    Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA     public key or DSA parameters may experience long delays. Where the key or parameters that are being     checked have been obtained from an untrusted source this may lead to a Denial of Service. The functions     EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those     computations take a long time if the modulus (`p` parameter) is too large. Trying to use a very large     modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in     length for signature verification. However the key and parameter check functions do not limit the modulus     size when performing the checks. An application that calls EVP_PKEY_param_check() or     EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be     vulnerable to a Denial of Service attack. These functions are not called by OpenSSL itself on untrusted     DSA keys so only applications that directly call these functions may be vulnerable. Also vulnerable are     the OpenSSL pkey and pkeyparam command line applications when using the `-check` option. The OpenSSL     SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are affected     by this issue. (CVE-2024-4603)

  - Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was     previously freed in some situations Impact summary: A use after free can have a range of potential     consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only     applications that directly call the SSL_free_buffers function are affected by this issue. Applications     that do not call this function are not vulnerable. Our investigations indicate that this function is     rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer     used when processing an incoming record from the network. The call is only expected to succeed if the     buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even     when still in use. The first scenario occurs where a record header has been received from the network and     processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers     will succeed even though a record has only been partially processed and the buffer is still in use. The     second scenario occurs where a full record containing application data has been received and processed by     OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed     even though the buffer is still in use. While these scenarios could occur accidentally during normal     operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware     of this issue being actively exploited. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this     issue. Found by William Ahern (Akamai). Fix developed by Matt Caswell. Fix developed by Watson Ladd     (Akamai). Fixed in OpenSSL 3.3.1 (Affected since 3.3.0). (CVE-2024-4741)

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-2024-677 advisory.

    Issue summary: Checking excessively long DSA keys or parameters may be veryslow.

    Impact summary: Applications that use the functions EVP_PKEY_param_check()or EVP_PKEY_public_check() to     check a DSA public key or DSA parameters mayexperience long delays. Where the key or parameters that are     being checkedhave been obtained from an untrusted source this may lead to a Denial ofService.

    The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() performvarious checks on DSA parameters.
    Some of those computations take a long timeif the modulus (`p` parameter) is too large.

    Trying to use a very large modulus is slow and OpenSSL will not allow usingpublic keys with a modulus     which is over 10,000 bits in length for signatureverification. However the key and parameter check     functions do not limitthe modulus size when performing the checks.

    An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check()and supplies a key or     parameters obtained from an untrusted source could bevulnerable to a Denial of Service attack.

    These functions are not called by OpenSSL itself on untrusted DSA keys soonly applications that directly     call these functions may be vulnerable.

    Also vulnerable are the OpenSSL pkey and pkeyparam command line applicationswhen using the `-check`     option.

    The OpenSSL SSL/TLS implementation is not affected by this issue.

    The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue. (CVE-2024-4603)

    openssl: Use After Free with SSL_free_buffers (CVE-2024-4741)

    Issue summary: Calling the OpenSSL API function SSL_select_next_proto with anempty supported client     protocols buffer may cause a crash or memory contents tobe sent to the peer.

    Impact summary: A buffer overread can have a range of potential consequencessuch as unexpected application     beahviour or a crash. In particular this issuecould result in up to 255 bytes of arbitrary private data     from memory being sentto the peer leading to a loss of confidentiality. However, only applicationsthat     directly call the SSL_select_next_proto function with a 0 length list ofsupported client protocols are     affected by this issue. This would normally neverbe a valid scenario and is typically not under attacker     control but may occur byaccident in the case of a configuration or programming error in the     callingapplication.

    The OpenSSL API function SSL_select_next_proto is typically used by TLSapplications that support ALPN     (Application Layer Protocol Negotiation) or NPN(Next Protocol Negotiation). NPN is older, was never     standardised andis deprecated in favour of ALPN. We believe that ALPN is significantly morewidely deployed     than NPN. The SSL_select_next_proto function accepts a list ofprotocols from the server and a list of     protocols from the client and returnsthe first protocol that appears in the server list that also appears     in theclient list. In the case of no overlap between the two lists it returns thefirst item in the client     list. In either case it will signal whether an overlapbetween the two lists was found. In the case where     SSL_select_next_proto iscalled with a zero length client list it fails to notice this condition andreturns     the memory immediately following the client list pointer (and reportsthat there was no overlap in the     lists).

    This function is typically called from a server side application callback forALPN or a client side     application callback for NPN. In the case of ALPN the listof protocols supplied by the client is     guaranteed by libssl to never be zero inlength. The list of server protocols comes from the application     and should nevernormally be expected to be of zero length. In this case if theSSL_select_next_proto     function has been called as expected (with the listsupplied by the client passed in the client/client_len     parameters), then theapplication will not be vulnerable to this issue. If the application hasaccidentally     been configured with a zero length server list, and hasaccidentally passed that zero length server list in     the client/client_lenparameters, and has additionally failed to correctly handle a no overlapresponse     (which would normally result in a handshake failure in ALPN) then itwill be vulnerable to this problem.

    In the case of NPN, the protocol permits the client to opportunistically selecta protocol when there is no     overlap. OpenSSL returns the first client protocolin the no overlap case in support of this. The list of     client protocols comesfrom the application and should never normally be expected to be of zero     length.However if the SSL_select_next_proto function is accidentally called with aclient_len of 0 then an     invalid memory pointer will be returned instead. If theapplication uses this output as the opportunistic     protocol then the loss ofconfidentiality will occur.

    This issue has been assessed as Low severity because applications are mostlikely to be vulnerable if they     are using NPN instead of ALPN - but NPN is notwidely used. It also requires an application configuration     or programming error.Finally, this issue would not typically be under attacker control making     activeexploitation unlikely.

    The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

    Due to the low severity of this issue we are not issuing new releases ofOpenSSL at this time. The fix will     be included in the next releases when theybecome available. (CVE-2024-5535)

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

    Security issues fixed:

    - CVE-2024-4603: Check DSA parameters for excessive sizes before validating (bsc#1224388)
    - CVE-2024-4741: Fixed a use-after-free with SSL_free_buffers. (bsc#1225551)

    Other issues fixed:

    - Enable livepatching support (bsc#1223428)
    - Fix HDKF key derivation (bsc#1225291, gh#openssl/openssl#23448, +  gh#openssl/openssl#23456)

Tenable has extracted the preceding description block directly from the SUSE 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 versions of Oracle Database Server installed on the remote host are affected by multiple vulnerabilities as referenced in the July 2024 CPU advisory.

  - Netty project is an event-driven asynchronous network application framework. In versions prior to     4.1.86.Final, a StackOverflowError can be raised when parsing a malformed crafted message due to an     infinite recursion. This issue is patched in version 4.1.86.Final. There is no workaround, except using a     custom HaProxyMessageDecoder. (CVE-2022-41881)

  - Netty project is an event-driven asynchronous network application framework. Starting in version     4.1.83.Final and prior to 4.1.86.Final, when calling `DefaultHttpHeadesr.set` with an _iterator_ of     values, header value validation was not performed, allowing malicious header values in the iterator to     perform HTTP Response Splitting. This issue has been patched in version 4.1.86.Final. Integrators can work     around the issue by changing the `DefaultHttpHeaders.set(CharSequence, Iterator<?>)` call, into a     `remove()` call, and call `add()` in a loop over the iterator of values. (CVE-2022-41915)

  - A defect was discovered in the Python ssl module where there is a memory race condition with the     ssl.SSLContext methods cert_store_stats() and get_ca_certs(). The race condition can be triggered if     the methods are called at the same time as certificates are loaded into the SSLContext, such as during the     TLS handshake with a certificate directory configured. This issue is fixed in CPython 3.10.14, 3.11.9,     3.12.3, and 3.13.0a5. (CVE-2024-0397)

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

    It was discovered that OpenSSL incorrectly handled TLSv1.3 sessions when certain non-default TLS server     configurations were in use. A remote attacker could possibly use this issue to cause OpenSSL to consume     resources, leading to a denial of service. (CVE-2024-2511)

    It was discovered that OpenSSL incorrectly handled checking excessively long DSA keys or parameters. 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 and Ubuntu 24.04 LTS. (CVE-2024-4603)

    William Ahern discovered that OpenSSL incorrectly handled certain memory operations in a rarely-used API.
    A remote attacker could use this issue to cause OpenSSL to crash, resulting in a denial of service, or     possibly execute arbitrary code. (CVE-2024-4741)

    Joseph Birr-Pixton discovered that OpenSSL incorrectly handled calling a certain API with an empty     supported client protocols buffer. A remote attacker could possibly use this issue to obtain sensitive     information, or cause OpenSSL to crash, resulting in a denial of service. (CVE-2024-5535)

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 cloud-hypervisor-cvm / nodejs18 / openssl / nodejs installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-4603 advisory.

  - Issue summary: Checking excessively long DSA keys or parameters May be very slow. Impact summary:
    Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA     public key or DSA parameters May experience long delays. Where the key or parameters that are being     checked have been obtained from an untrusted source this May lead to a Denial of Service. The functions     EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those     computations take a long time if the modulus (`p` parameter) is too large. Trying to use a very large     modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in     length for signature verification. However the key and parameter check functions do not limit the modulus     size when performing the checks. An application that calls EVP_PKEY_param_check() or     EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be     vulnerable to a Denial of Service attack. These functions are not called by OpenSSL itself on untrusted     DSA keys so only applications that directly call these functions May be vulnerable. Also vulnerable are     the OpenSSL pkey and pkeyparam command line applications when using the `-check` option. The OpenSSL     SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are affected     by this issue. (CVE-2024-4603)

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

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:1947-1 advisory.

    - CVE-2024-2511: Fixed unconstrained session cache growth in TLSv1.3 (bsc#1222548).
    - CVE-2024-4603: Fixed DSA parameter checks for excessive sizes before validating (bsc#1224388).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

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
192966	OpenSSL 3.0.0 < 3.0.14 Multiple Vulnerabilities	Nessus	Web Servers	4/8/2024	10/7/2024	medium
197494	FreeBSD : OpenSSL -- Denial of Service vulnerability (b88aa380-1442-11ef-a490-84a93843eb75)	Nessus	FreeBSD Local Security Checks	5/18/2024	8/14/2024	medium
197945	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : openssl-3 (SUSE-SU-2024:1789-1)	Nessus	SuSE Local Security Checks	5/28/2024	5/28/2024	medium
192967	OpenSSL 3.2.0 < 3.2.2 Multiple Vulnerabilities	Nessus	Web Servers	4/8/2024	10/7/2024	medium
192974	OpenSSL 3.1.0 < 3.1.6 Multiple Vulnerabilities	Nessus	Web Servers	4/8/2024	10/7/2024	medium
197189	OpenSSL 3.3.0 < 3.3.1 Multiple Vulnerabilities	Nessus	Web Servers	5/16/2024	10/7/2024	medium
200325	CentOS 9 : openssl-3.2.2-1.el9	Nessus	CentOS Local Security Checks	6/11/2024	9/6/2024	medium
205110	Amazon Linux 2023 : openssl, openssl-devel, openssl-libs (ALAS2023-2024-677)	Nessus	Amazon Linux Local Security Checks	8/6/2024	9/6/2024	critical
200711	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : openssl-3 (SUSE-SU-2024:2066-1)	Nessus	SuSE Local Security Checks	6/19/2024	6/19/2024	high
202724	Oracle Database Server (Jul 2024 CPU)	Nessus	Databases	7/19/2024	7/23/2024	high
204924	Ubuntu 20.04 LTS / 22.04 LTS / 24.04 LTS : OpenSSL vulnerabilities (USN-6937-1)	Nessus	Ubuntu Local Security Checks	7/31/2024	9/6/2024	critical
201625	CBL Mariner 2.0 Security Update: cloud-hypervisor-cvm / nodejs18 / openssl / nodejs (CVE-2024-4603)	Nessus	MarinerOS Local Security Checks	7/3/2024	10/15/2024	medium
200236	SUSE SLES15 Security Update : openssl-3 (SUSE-SU-2024:1947-1)	Nessus	SuSE Local Security Checks	6/8/2024	6/8/2024	medium

Detections

Analytics

Plugins Search

medium

medium

medium

medium

medium

medium

medium

critical

high

high

critical

medium

medium