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.

It is, therefore, affected by a vulnerability as referenced in the ALAS2-2024-2539 advisory.

    Issue summary: Some non-default TLS server configurations can cause unboundedmemory growth when processing     TLSv1.3 sessions

    Impact summary: An attacker may exploit certain server configurations to triggerunbounded 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 isbeing used (but not if     early_data support is also configured and the defaultanti-replay protection is in use). In this case,     under certain conditions, thesession cache can get into an incorrect state and it will fail to flush     properlyas it fills. The session cache will continue to grow in an unbounded manner. Amalicious client     could deliberately create the scenario for this failure toforce 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 TLSclients.

    The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL1.0.2 is also not affected by     this issue. (CVE-2024-2511)

Tenable has extracted the preceding description block directly from the tested product 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 IBM MQ Server running on the remote host is affected by a vulnerability as referenced in the 7167211 advisory.

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

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 openssl11 installed on the remote host is prior to 1.1.1g-12. It is, therefore, affected by a vulnerability as referenced in the ALAS2-2024-2564 advisory.

    Issue summary: Some non-default TLS server configurations can cause unboundedmemory growth when processing     TLSv1.3 sessions

    Impact summary: An attacker may exploit certain server configurations to triggerunbounded 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 isbeing used (but not if     early_data support is also configured and the defaultanti-replay protection is in use). In this case,     under certain conditions, thesession cache can get into an incorrect state and it will fail to flush     properlyas it fills. The session cache will continue to grow in an unbounded manner. Amalicious client     could deliberately create the scenario for this failure toforce 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 TLSclients.

    The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL1.0.2 is also not affected by     this issue. (CVE-2024-2511)

Tenable has extracted the preceding description block directly from the tested product 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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

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

Note that Nessus relies on the presence of the package as reported by the vendor.

The version of openssl installed on the remote host is prior to 1.1.1za. It is, therefore, affected by multiple vulnerabilities as referenced in the SSA:2024-199-01 advisory.

    New openssl packages are available for Slackware 15.0 and -current to fix security issues.

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

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

The remote Ubuntu 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 remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:9333 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: Unbounded memory growth with session handling in TLSv1.3 (CVE-2024-2511)

    * openssl: Excessive time spent checking DSA keys and parameters (CVE-2024-4603)

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

    * openssl: SSL_select_next_proto buffer overread (CVE-2024-5535)

    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.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 9.5 Release Notes     linked from the References section.

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 NewStart CGSL host, running version MAIN 7.02, has openssl packages installed that are affected by multiple vulnerabilities:

  - Issue summary: A bug has been identified in the processing of key and initialisation vector (IV) lengths.
    This can lead to potential truncation or overruns during the initialisation of some symmetric ciphers.
    Impact summary: A truncation in the IV can result in non-uniqueness, which could result in loss of     confidentiality for some cipher modes. When calling EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() or     EVP_CipherInit_ex2() the provided OSSL_PARAM array is processed after the key and IV have been     established. Any alterations to the key length, via the keylen parameter or the IV length, via the     ivlen parameter, within the OSSL_PARAM array will not take effect as intended, potentially causing     truncation or overreading of these values. The following ciphers and cipher modes are impacted: RC2, RC4,     RC5, CCM, GCM and OCB. For the CCM, GCM and OCB cipher modes, truncation of the IV can result in loss of     confidentiality. For example, when following NIST's SP 800-38D section 8.2.1 guidance for constructing a     deterministic IV for AES in GCM mode, truncation of the counter portion could lead to IV reuse. Both     truncations and overruns of the key and overruns of the IV will produce incorrect results and could, in     some cases, trigger a memory exception. However, these issues are not currently assessed as security     critical. Changing the key and/or IV lengths is not considered to be a common operation and the vulnerable     API was recently introduced. Furthermore it is likely that application developers will have spotted this     problem during testing since decryption would fail unless both peers in the communication were similarly     vulnerable. For these reasons we expect the probability of an application being vulnerable to this to be     quite low. However if an application is vulnerable then this issue is considered very serious. For these     reasons we have assessed this issue as Moderate severity overall. The OpenSSL SSL/TLS implementation is     not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this because the     issue lies outside of the FIPS provider boundary. OpenSSL 3.1 and 3.0 are vulnerable to this issue.
    (CVE-2023-5363)

  - Issue summary: Checking excessively long DH keys or parameters may be very slow. Impact summary:
    Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key     or DH 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 function DH_check() performs     various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too     large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is     over 10,000 bits in length. However the DH_check() function checks numerous aspects of the key or     parameters that have been supplied. Some of those checks use the supplied modulus value even if it has     already been found to be too large. An application that calls DH_check() and supplies a key or parameters     obtained from an untrusted source could be vulernable to a Denial of Service attack. The function     DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those     other functions may similarly be affected. The other functions affected by this are DH_check_ex() and     EVP_PKEY_param_check(). Also vulnerable are the OpenSSL dhparam 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 not affected by this issue. (CVE-2023-3446)

  - Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or     parameters may be very slow. Impact summary: Applications that use the functions DH_generate_key() to     generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(),     DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH 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. While DH_check() performs all the necessary checks     (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable     for excessively large P and Q parameters. Likewise, while DH_generate_key() performs a check for an     excessively large P, it doesn't check for an excessively large Q. An application that calls     DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source     could be vulnerable to a Denial of Service attack. DH_generate_key() and DH_check_pub_key() are also     called by a number of other OpenSSL functions. An application calling any of those other functions may     similarly be affected. The other functions affected by this are DH_check_pub_key_ex(),     EVP_PKEY_public_check(), and EVP_PKEY_generate(). Also vulnerable are the OpenSSL pkey command line     application when using the -pubcheck option, as well as the OpenSSL genpkey command line application.
    The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers     are not affected by this issue. (CVE-2023-5678)

  - Issue summary: The POLY1305 MAC (message authentication code) implementation contains a bug that might     corrupt the internal state of applications running on PowerPC CPU based platforms if the CPU provides     vector instructions. Impact summary: If an attacker can influence whether the POLY1305 MAC algorithm is     used, the application state might be corrupted with various application dependent consequences. The     POLY1305 MAC (message authentication code) implementation in OpenSSL for PowerPC CPUs restores the     contents of vector registers in a different order than they are saved. Thus the contents of some of these     vector registers are corrupted when returning to the caller. The vulnerable code is used only on newer     PowerPC processors supporting the PowerISA 2.07 instructions. The consequences of this kind of internal     application state corruption can be various - from no consequences, if the calling application does not     depend on the contents of non-volatile XMM registers at all, to the worst consequences, where the attacker     could get complete control of the application process. However unless the compiler uses the vector     registers for storing pointers, the most likely consequence, if any, would be an incorrect result of some     application dependent calculations or a crash leading to a denial of service. The POLY1305 MAC algorithm     is most frequently used as part of the CHACHA20-POLY1305 AEAD (authenticated encryption with associated     data) algorithm. The most common usage of this AEAD cipher is with TLS protocol versions 1.2 and 1.3. If     this cipher is enabled on the server a malicious client can influence whether this AEAD cipher is used.
    This implies that TLS server applications using OpenSSL can be potentially impacted. However we are     currently not aware of any concrete application that would be affected by this issue therefore we consider     this a Low severity security issue. (CVE-2023-6129)

  - Issue summary: Checking excessively long invalid RSA public keys may take a long time. Impact summary:
    Applications that use the function EVP_PKEY_public_check() to check RSA public keys may experience long     delays. Where the key that is being checked has been obtained from an untrusted source this may lead to a     Denial of Service. When function EVP_PKEY_public_check() is called on RSA public keys, a computation is     done to confirm that the RSA modulus, n, is composite. For valid RSA keys, n is a product of two or more     large primes and this computation completes quickly. However, if n is an overly large prime, then this     computation would take a long time. An application that calls EVP_PKEY_public_check() and supplies an RSA     key obtained from an untrusted source could be vulnerable to a Denial of Service attack. The function     EVP_PKEY_public_check() is not called from other OpenSSL functions however it is called from the OpenSSL     pkey command line application. For that reason that application is also vulnerable if used with the     '-pubin' and '-check' options on untrusted data. 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-2023-6237)

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 HTTP Server installed on the remote host are affected by multiple vulnerabilities as referenced in the October 2024 CPU advisory.

  - Vulnerability in the Oracle HTTP Server product of Oracle Fusion Middleware (component: Web Listener     (OpenSSL)). The supported version that is affected is 12.2.1.4.0. Easily exploitable vulnerability allows     unauthenticated attacker with network access via TLS to compromise Oracle HTTP Server. Successful attacks     of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash     (complete DOS) of Oracle HTTP Server. (CVE-2024-2511, CVE-2024-4603, CVE-2024-4741)

  - Vulnerability in the Oracle HTTP Server product of Oracle Fusion Middleware (component: Plugins (Nghttp2)).     The supported version that is affected is 14.1.1.0.0. Easily exploitable vulnerability allows     unauthenticated attacker with network access via HTTP/2 to compromise Oracle HTTP Server.     Successful attacks of this vulnerability can result in unauthorized ability to cause a partial     denial of service (partial DOS) of Oracle HTTP Server. (CVE-2024-28182)

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
192967	OpenSSL 3.2.0 < 3.2.2 Multiple Vulnerabilities	Nessus	Web Servers	4/8/2024	11/14/2024	high
197110	Amazon Linux 2 : edk2 (ALAS-2024-2539)	Nessus	Amazon Linux Local Security Checks	5/15/2024	3/31/2025	medium
206688	IBM MQ 9.0 < 9.0.0.27 LTS / 9.1 < 9.1.0.23 LTS / 9.2 < 9.2.0.27 LTS / 9.3 < 9.3.0.21 LTS / 9.4 < 9.4.0.5 LTS (7167211)	Nessus	Misc.	9/5/2024	3/31/2025	medium
200379	Amazon Linux 2 : openssl11 (ALAS-2024-2564)	Nessus	Amazon Linux Local Security Checks	6/12/2024	3/31/2025	medium
257049	Linux Distros Unpatched Vulnerability : CVE-2024-2511	Nessus	Misc.	8/27/2025	12/1/2025	medium
202581	Slackware Linux 15.0 / current openssl Multiple Vulnerabilities (SSA:2024-199-01)	Nessus	Slackware Local Security Checks	7/17/2024	4/14/2025	medium
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/3/2025	critical
210793	RHEL 9 : openssl and openssl-fips-provider (RHSA-2024:9333)	Nessus	Red Hat Local Security Checks	11/12/2024	4/14/2025	critical
242811	NewStart CGSL MAIN 7.02 : openssl Multiple Vulnerabilities (NS-SA-2025-0124)	Nessus	NewStart CGSL Local Security Checks	7/25/2025	7/25/2025	high
209278	Oracle HTTP Server (October 2024 CPU)	Nessus	Web Servers	10/18/2024	4/17/2025	high

Detections

Analytics

Plugins Search

high

medium

medium

medium

medium

medium

critical

critical

high

high