Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients. RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server's RPK fails to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER. Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2. The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

The 8.2.0.0.0 and 12.2.1.4.0 versions of Oracle Business Intelligence Enterprise Edition installed on the remote host are affected by multiple vulnerabilities as referenced in the October 2025 CPU advisory.

  - Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics     (component: Analytics Web Administration). Supported versions that are affected are 7.6.0.0.0 and     8.2.0.0.0. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP     to compromise Oracle Business Intelligence Enterprise Edition. Successful attacks require human     interaction from a person other than the attacker and while the vulnerability is in Oracle Business     Intelligence Enterprise Edition, attacks may significantly impact additional products (scope change).
    Successful attacks of this vulnerability can result in takeover of Oracle Business Intelligence Enterprise     Edition. (CVE-2025-53049)

  - Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics     (component: Platform Security (Apache Commons FileUpload)). Supported versions that are affected are     7.6.0.0.0, 8.2.0.0.0 and 12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated attacker with     network access via HTTP to compromise Oracle Business Intelligence Enterprise Edition. Successful attacks     of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash     (complete DOS) of Oracle Business Intelligence Enterprise Edition. (CVE-2025-48976)

  - Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics     (component: Analytics Server (Cryptography)). Supported versions that are affected are 7.6.0.0.0 and     8.2.0.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP     to compromise Oracle Business Intelligence Enterprise Edition. Successful attacks require human     interaction from a person other than the attacker. Successful attacks of this vulnerability can result in     unauthorized update, insert or delete access to some of Oracle Business Intelligence Enterprise Edition     accessible data as well as unauthorized read access to a subset of Oracle Business Intelligence Enterprise     Edition accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of     Oracle Business Intelligence Enterprise Edition. (CVE-2024-12797)

  - Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics     (component: Analytics Server (Apache Commons IO)). Supported versions that are affected are 7.6.0.0.0,     8.2.0.0.0 and 12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network     access via HTTP to compromise Oracle Business Intelligence Enterprise Edition. Successful attacks require     human interaction from a person other than the attacker. Successful attacks of this vulnerability can     result in unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Business     Intelligence Enterprise Edition. (CVE-2024-47554)

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 Oracle Business Intelligence Enterprise Edition (OAS) 7.6.0.0.0 installed on the remote host is affected by multiple vulnerabilities as referenced in the October 2025 CPU advisory.

  - Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics     (component: Analytics Web Administration). Supported versions that are affected are 7.6.0.0.0 and     8.2.0.0.0. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP     to compromise Oracle Business Intelligence Enterprise Edition. Successful attacks require human     interaction from a person other than the attacker and while the vulnerability is in Oracle Business     Intelligence Enterprise Edition, attacks may significantly impact additional products (scope change).
    Successful attacks of this vulnerability can result in takeover of Oracle Business Intelligence Enterprise     Edition. (CVE-2025-53049)

  - Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice     that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER     verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable     to man-in-middle attacks when server authentication failure is not detected by clients. RPKs are disabled     by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable     RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate     chain. The affected clients are those that then rely on the handshake to fail when the server's RPK fails     to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER. Clients     that enable server-side raw public keys can still find out that raw public key verification failed by     calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This     issue was introduced in the initial implementation of RPK support in OpenSSL 3.2. The FIPS modules in 3.4,     3.3, 3.2, 3.1 and 3.0 are not affected by this issue. (CVE-2024-12797)

  - Uncontrolled Resource Consumption vulnerability in Apache Commons IO. The     org.apache.commons.io.input.XmlStreamReader class may excessively consume CPU resources when processing     maliciously crafted input. This issue affects Apache Commons IO: from 2.0 before 2.14.0. Users are     recommended to upgrade to version 2.14.0 or later, which fixes the issue. (CVE-2024-47554)

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 Oracle Business Intelligence Enterprise Edition (OAS) 8.2.0.0.0 installed on the remote host is affected by multiple vulnerabilities as referenced in the October 2025 CPU advisory.

  - Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics     (component: Analytics Web Administration). Supported versions that are affected are 7.6.0.0.0 and     8.2.0.0.0. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP     to compromise Oracle Business Intelligence Enterprise Edition. Successful attacks require human     interaction from a person other than the attacker and while the vulnerability is in Oracle Business     Intelligence Enterprise Edition, attacks may significantly impact additional products (scope change).
    Successful attacks of this vulnerability can result in takeover of Oracle Business Intelligence Enterprise     Edition. (CVE-2025-53049)

  - Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice     that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER     verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable     to man-in-middle attacks when server authentication failure is not detected by clients. RPKs are disabled     by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable     RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate     chain. The affected clients are those that then rely on the handshake to fail when the server's RPK fails     to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER. Clients     that enable server-side raw public keys can still find out that raw public key verification failed by     calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This     issue was introduced in the initial implementation of RPK support in OpenSSL 3.2. The FIPS modules in 3.4,     3.3, 3.2, 3.1 and 3.0 are not affected by this issue. (CVE-2024-12797)

  - Uncontrolled Resource Consumption vulnerability in Apache Commons IO. The     org.apache.commons.io.input.XmlStreamReader class may excessively consume CPU resources when processing     maliciously crafted input. This issue affects Apache Commons IO: from 2.0 before 2.14.0. Users are     recommended to upgrade to version 2.14.0 or later, which fixes the issue. (CVE-2024-47554)

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 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-2025:02042-1 advisory.

    - CVE-2025-27587: timing side-channel vulnerability in the P-384 implementation when used with ECDSA     (bsc#1243459).
    - CVE-2024-12797: Fixed that RFC7250 handshakes with unauthenticated servers don't abort as expected.
    (bsc#1236599)
    - CVE-2024-13176: Fixed timing side-channel in ECDSA signature computation (bsc#1236136)

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 version of the Tenable Identity Exposure running on the remote host is prior to 3.77.11. It is, therefore, affected by multiple vulnerabilities according to advisory TNS-2025-07, including the following:

  - Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice     that the server was not authenticated, because handshakes don't abort as expected when the     SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections using raw public keys     may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients.     RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients     explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of     an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when     the server's RPK fails to match one of the expected public keys, by setting the verification mode to     SSL_VERIFY_PEER. Clients that enable server-side raw public keys can still find out that raw public key     verification failed by calling SSL_get_verify_result(), and those that do, and take appropriate action,     are not affected. This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2.     The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. (CVE-2024-12797)

  - Issue summary: A timing side-channel which could potentially allow recovering the private key exists in     the ECDSA signature computation. Impact summary: A timing side-channel in ECDSA signature computations     could allow recovering the private key by an attacker. However, measuring the timing would require either     local access to the signing application or a very fast network connection with low latency. There is a     timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero.     This can happen with significant probability only for some of the supported elliptic curves. In     particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must     either be located in the same physical computer or must have a very fast network connection with low     latency. For that reason the severity of this vulnerability is Low. The FIPS modules in 3.4, 3.3, 3.2,     3.1 and 3.0 are affected by this issue. (CVE-2024-13176)

  - Erlang/OTP is a set of libraries for the Erlang programming language. Prior to versions OTP-27.3.3,     OTP-26.2.5.11, and OTP-25.3.2.20, a SSH server may allow an attacker to perform unauthenticated remote     code execution (RCE). By exploiting a flaw in SSH protocol message handling, a malicious actor could gain     unauthorized access to affected systems and execute arbitrary commands without valid credentials. This     issue is patched in versions OTP-27.3.3, OTP-26.2.5.11, and OTP-25.3.2.20. A temporary workaround     involves disabling the SSH server or to prevent access via firewall rules. (CVE-2025-32433)

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

The remote RockyLinux 9 host has packages installed that are affected by a vulnerability as referenced in the RLSA-2025:1330 advisory.

    * openssl: RFC7250 handshakes with unauthenticated servers don't abort as expected (CVE-2024-12797)

Tenable has extracted the preceding description block directly from the RockyLinux 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 remote Fedora 40 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2025-becf280371 advisory.

    Rebase to 3.2.4

Tenable has extracted the preceding description block directly from the Fedora 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 cloud-hypervisor-cvm / openssl installed on the remote Azure Linux 3.0 host is prior to tested version.
It is, therefore, affected by a vulnerability as referenced in the CVE-2024-12797 advisory.

  - Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server May fail to notice     that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER     verification mode is set. Impact summary: TLS and DTLS connections using raw public keys May be vulnerable     to man-in-middle attacks when server authentication failure is not detected by clients. RPKs are disabled     by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable     RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate     chain. The affected clients are those that then rely on the handshake to fail when the server's RPK fails     to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER. Clients     that enable server-side raw public keys can still find out that raw public key verification failed by     calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This     issue was introduced in the initial implementation of RPK support in OpenSSL 3.2. The FIPS modules in 3.4,     3.3, 3.2, 3.1 and 3.0 are not affected by this issue. (CVE-2024-12797)

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 cloud-hypervisor-cvm / openssl 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-12797 advisory.

  - Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server May fail to notice     that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER     verification mode is set. Impact summary: TLS and DTLS connections using raw public keys May be vulnerable     to man-in-middle attacks when server authentication failure is not detected by clients. RPKs are disabled     by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable     RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate     chain. The affected clients are those that then rely on the handshake to fail when the server's RPK fails     to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER. Clients     that enable server-side raw public keys can still find out that raw public key verification failed by     calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This     issue was introduced in the initial implementation of RPK support in OpenSSL 3.2. The FIPS modules in 3.4,     3.3, 3.2, 3.1 and 3.0 are not affected by this issue. (CVE-2024-12797)

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

The remote Fedora 41 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2025-e0e44b1b98 advisory.

    Rebase to 3.2.4, fix CVE-2024-12797

Tenable has extracted the preceding description block directly from the Fedora 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 remote AlmaLinux 9 host has packages installed that are affected by a vulnerability as referenced in the ALSA-2025:1330 advisory.

    * openssl: RFC7250 handshakes with unauthenticated servers don't abort as expected (CVE-2024-12797)

Tenable has extracted the preceding description block directly from the AlmaLinux 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 remote Oracle Linux 9 host has packages installed that are affected by a vulnerability as referenced in the ELSA-2025-1330 advisory.

    [3.2.2-6.0.1.1]
    - Enable openssl-fips-provider dependency [Orabug: 36504822]
    - Temporary disable openssl-fips-provider dependency [Orabug: 36504822]
    - Replace upstream references [Orabug: 34340177]

    [1:3.2.2-6.1]
    - RFC7250 handshakes with unauthenticated servers don't abort as expected (CVE-2024-12797)       Resolves: RHEL-76755

Tenable has extracted the preceding description block directly from the Oracle Linux 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 remote Ubuntu 24.10 host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-7264-1 advisory.

    It was discovered that OpenSSL clients incorrectly handled authenticating servers using RFC7250 Raw Public     Keys. In certain cases, the connection will not abort as expected, possibly causing the communication to     be intercepted. (CVE-2024-12797)

    George Pantelakis and Alicja Kario discovered that OpenSSL had a timing side-channel when performing ECDSA     signature computations. A remote attacker could possibly use this issue to recover private data.
    (CVE-2024-13176)

    It was discovered that OpenSSL incorrectly handled certain memory operations when using low-level GF(2^m)     elliptic curve APIs with untrusted explicit values for the field polynomial. When being used in this     uncommon fashion, 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-9143)

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 a vulnerability as referenced in the a64761a1-e895-11ef-873e-8447094a420f advisory.

    The OpenSSL project reports:
    RFC7250 handshakes with unauthenticated servers don't abort as expected (High).
                Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that     the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER     verification mode is set.

Tenable has extracted the preceding description block directly from the FreeBSD 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 remote Redhat Enterprise Linux 9 host has packages installed that are affected by a vulnerability as referenced in the RHSA-2025:1330 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: RFC7250 handshakes with unauthenticated servers don't abort as expected (CVE-2024-12797)

    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.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

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

ID	Name	Product	Family	Severity
275601	Oracle Business Intelligence Enterprise Edition (October 2025 CPU)	Nessus	Misc.	high
271383	Oracle Business Intelligence Enterprise Edition (OAS 7.6) (October 2025 CPU)	Nessus	Misc.	high
271382	Oracle Business Intelligence Enterprise Edition (OAS 8.2) (October 2025 CPU)	Nessus	Misc.	high
242811	NewStart CGSL MAIN 7.02 : openssl Multiple Vulnerabilities (NS-SA-2025-0124)	Nessus	NewStart CGSL Local Security Checks	high
240596	SUSE SLED15 / SLES15 Security Update : openssl-3 (SUSE-SU-2025:02042-1)	Nessus	SuSE Local Security Checks	medium
235471	Tenable Identity Exposure < 3.77.11 Multiple Vulnerabilities (TNS-2025-07)	Nessus	Windows	critical
232947	RockyLinux 9 : openssl (RLSA-2025:1330)	Nessus	Rocky Linux Local Security Checks	medium
216838	Fedora 40 : openssl (2025-becf280371)	Nessus	Fedora Local Security Checks	medium
216786	Azure Linux 3.0 Security Update: cloud-hypervisor-cvm / openssl (CVE-2024-12797)	Nessus	Azure Linux Local Security Checks	medium
216627	CBL Mariner 2.0 Security Update: cloud-hypervisor-cvm / openssl (CVE-2024-12797)	Nessus	MarinerOS Local Security Checks	medium
216257	Fedora 41 : openssl (2025-e0e44b1b98)	Nessus	Fedora Local Security Checks	medium
216246	AlmaLinux 9 : openssl (ALSA-2025:1330)	Nessus	Alma Linux Local Security Checks	medium
216215	Oracle Linux 9 : openssl (ELSA-2025-1330)	Nessus	Oracle Linux Local Security Checks	medium
216159	Ubuntu 24.10 : OpenSSL vulnerabilities (USN-7264-1)	Nessus	Ubuntu Local Security Checks	high
216145	FreeBSD : OpenSSL -- Man-in-the-Middle vulnerability (a64761a1-e895-11ef-873e-8447094a420f)	Nessus	FreeBSD Local Security Checks	medium
216104	RHEL 9 : openssl (RHSA-2025:1330)	Nessus	Red Hat Local Security Checks	medium

Detections

Analytics

CVE-2024-12797

medium

Tenable Plugins

high

high

high

high

medium

critical

medium

medium

medium

medium

medium

medium

medium

high

medium

medium