According to the versions of the openssl packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the     field polynomial can lead to out-of-bounds memory reads or writes.Impact summary: Out of bound memory     writes can lead to an application crash or even a possibility of a remote code execution, however, in all     the protocols involving Elliptic Curve Cryptography that we're aware of, either only 'named curves' are     supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary     (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a     vulnerable application is low.  In particular, the X9.62 encoding is used for ECC keys in X.509     certificates, so problematic inputs cannot occur in the context of processing X.509 certificates.  Any     problematic use-cases would have to be using an 'exotic' curve encoding.  The affected APIs include:
    EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.
    Applications working with 'exotic' explicit binary (GF(2^m)) curve parameters, that make it possible to     represent invalid field polynomials with a zero constant term, via the above or similar APIs, may     terminate abruptly as a result of reading or writing outside of array bounds.  Remote code execution     cannot easily be ruled out.  The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this     issue.(CVE-2024-9143)

Tenable has extracted the preceding description block directly from the EulerOS openssl 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 hvloader / 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-9143 advisory.

  - Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial     can lead to out-of-bounds memory reads or writes. (CVE-2024-9143)

  - Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the     field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory     writes can lead to an application crash or even a possibility of a remote code execution, however, in all     the protocols involving Elliptic Curve Cryptography that we're aware of, either only named curves are     supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary     (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a     vulnerable application is low. In particular, the X9.62 encoding is used for ECC keys in X.509     certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any     problematic use-cases would have to be using an exotic curve encoding. The affected APIs include:
    EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.
    Applications working with exotic explicit binary (GF(2^m)) curve parameters, that make it possible to     represent invalid field polynomials with a zero constant term, via the above or similar APIs, may     terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot     easily be ruled out. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
    (CVE-2024-9143)

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

According to the versions of the openssl packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

    Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the     field polynomial can lead to out-of-bounds memory reads or writes.  Impact summary: Out of bound memory     writes can lead to an application crash or even a possibility of a remote code execution, however, in all     the protocols involving Elliptic Curve Cryptography that we're aware of, either only 'named curves' are     supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary     (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a     vulnerable application is low.  In particular, the X9.62 encoding is used for ECC keys in X.509     certificates, so problematic inputs cannot occur in the context of processing X.509 certificates.  Any     problematic use-cases would have to be using an 'exotic' curve encoding.  The affected APIs include:
    EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.
    Applications working with 'exotic' explicit binary (GF(2^m)) curve parameters, that make it possible to     represent invalid field polynomials with a zero constant term, via the above or similar APIs, may     terminate abruptly as a result of reading or writing outside of array bounds.  Remote code execution     cannot easily be ruled out.  The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this     issue.(CVE-2024-9143)

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

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

According to the versions of the openssl packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the     field polynomial can lead to out-of-bounds memory reads or writes.  Impact summary: Out of bound memory     writes can lead to an application crash or even a possibility of a remote code execution, however, in all     the protocols involving Elliptic Curve Cryptography that we're aware of, either only 'named curves' are     supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary     (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a     vulnerable application is low.  In particular, the X9.62 encoding is used for ECC keys in X.509     certificates, so problematic inputs cannot occur in the context of processing X.509 certificates.  Any     problematic use-cases would have to be using an 'exotic' curve encoding.  The affected APIs include:
    EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.
    Applications working with 'exotic' explicit binary (GF(2^m)) curve parameters, that make it possible to     represent invalid field polynomials with a zero constant term, via the above or similar APIs, may     terminate abruptly as a result of reading or writing outside of array bounds.  Remote code execution     cannot easily be ruled out.(CVE-2024-9143)

Tenable has extracted the preceding description block directly from the EulerOS openssl 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 AHV installed on the remote host is prior to 20230302.102005. It is, therefore, affected by multiple vulnerabilities as referenced in the NXSA-AHV-20230302.101060 advisory.

  - In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option>     elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods     (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
    (CVE-2020-11023)

  - A flaw was found in rsync. When using the `--safe-links` option, the rsync client fails to properly verify     if a symbolic link destination sent from the server contains another symbolic link within it. This results     in a path traversal vulnerability, which may lead to arbitrary file write outside the desired directory.
    (CVE-2024-12088)

  - A vulnerability was found in Unbound due to incorrect default permissions, allowing any process outside     the unbound group to modify the unbound runtime configuration. If a process can connect over localhost to     port 8953, it can alter the configuration of unbound.service. This flaw allows an unprivileged attacker to     manipulate a running instance, potentially altering forwarders, allowing them to track all queries     forwarded by the local resolver, and, in some cases, disrupting resolving altogether. (CVE-2024-1488)

  - NLnet Labs Unbound up to and including version 1.21.0 contains a vulnerability when handling replies with     very large RRsets that it needs to perform name compression for. Malicious upstreams responses with very     large RRsets can cause Unbound to spend a considerable time applying name compression to downstream     replies. This can lead to degraded performance and eventually denial of service in well orchestrated     attacks. The vulnerability can be exploited by a malicious actor querying Unbound for the specially     crafted contents of a malicious zone with very large RRsets. Before Unbound replies to the query it will     try to apply name compression which was an unbounded operation that could lock the CPU until the whole     packet was complete. Unbound version 1.21.1 introduces a hard limit on the number of name compression     calculations it is willing to do per packet. Packets that need more compression will result in semi-     compressed packets or truncated packets, even on TCP for huge messages, to avoid locking the CPU for long.
    This change should not affect normal DNS traffic. (CVE-2024-8508)

  - A path traversal vulnerability exists in rsync. It stems from behavior enabled by the `--inc-recursive`     option, a default-enabled option for many client options and can be enabled by the server even if not     explicitly enabled by the client. When using the `--inc-recursive` option, a lack of proper symlink     verification coupled with deduplication checks occurring on a per-file-list basis could allow a server to     write files outside of the client's intended destination directory. A malicious server could write     malicious files to arbitrary locations named after valid directories/paths on the client. (CVE-2024-12087)

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 AHV installed on the remote host is prior to 20230302.102005. It is, therefore, affected by multiple vulnerabilities as referenced in the NXSA-AHV-20230302.103032 advisory.

  - In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option>     elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods     (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
    (CVE-2020-11023)

  - A flaw was found in rsync. When using the `--safe-links` option, the rsync client fails to properly verify     if a symbolic link destination sent from the server contains another symbolic link within it. This results     in a path traversal vulnerability, which may lead to arbitrary file write outside the desired directory.
    (CVE-2024-12088)

  - A vulnerability was found in Unbound due to incorrect default permissions, allowing any process outside     the unbound group to modify the unbound runtime configuration. If a process can connect over localhost to     port 8953, it can alter the configuration of unbound.service. This flaw allows an unprivileged attacker to     manipulate a running instance, potentially altering forwarders, allowing them to track all queries     forwarded by the local resolver, and, in some cases, disrupting resolving altogether. (CVE-2024-1488)

  - NLnet Labs Unbound up to and including version 1.21.0 contains a vulnerability when handling replies with     very large RRsets that it needs to perform name compression for. Malicious upstreams responses with very     large RRsets can cause Unbound to spend a considerable time applying name compression to downstream     replies. This can lead to degraded performance and eventually denial of service in well orchestrated     attacks. The vulnerability can be exploited by a malicious actor querying Unbound for the specially     crafted contents of a malicious zone with very large RRsets. Before Unbound replies to the query it will     try to apply name compression which was an unbounded operation that could lock the CPU until the whole     packet was complete. Unbound version 1.21.1 introduces a hard limit on the number of name compression     calculations it is willing to do per packet. Packets that need more compression will result in semi-     compressed packets or truncated packets, even on TCP for huge messages, to avoid locking the CPU for long.
    This change should not affect normal DNS traffic. (CVE-2024-8508)

  - A path traversal vulnerability exists in rsync. It stems from behavior enabled by the `--inc-recursive`     option, a default-enabled option for many client options and can be enabled by the server even if not     explicitly enabled by the client. When using the `--inc-recursive` option, a lack of proper symlink     verification coupled with deduplication checks occurring on a per-file-list basis could allow a server to     write files outside of the client's intended destination directory. A malicious server could write     malicious files to arbitrary locations named after valid directories/paths on the client. (CVE-2024-12087)

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

遠端主機上安裝的 Oracle Essbase 版本缺少 2025 年 4 月重大修補程式更新 (CPU) 的安全性修補程式。因此，此應用程式會受到以下弱點影響：

  - Oracle Essbase (元件：Web Platform (OpenSSL)) 中的弱點。受影響的支援版本是 21.7.1.0.0。容易受到惡意利用的弱點允許實體存取來危害 Oracle Essbase。成功攻擊此弱點可導致未經授權地更新、插入或刪除某些可供存取之 Oracle Essbase 資料的存取權，未經授權地讀取 Oracle Essbase 可存取資料子集的存取權，以及未經授權地造成部分拒絕服務的能力 (部分 DOS) Oracle Essbase 的 版。 (CVE-2024-9143、 CVE-2024-13176)

  - Oracle Essbase 中的 Security-in-Depth 問題 (元件：Web Platform (RequireJS))。無法在此產品的內容中惡意利用此弱點。(CVE-2024-38999)

  - Oracle Essbase (元件：市場 (jackson-databind)) 中的 Security-in-Depth 問題。無法在此產品的內容中惡意利用此弱點。 (CVE-2021-42575) 請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼。

遠端主機上安裝的 AHV 低於 20230302.102005 版。因此會受到 NXSA-AHV-20230302.101060 公告中提及的多個弱點影響。

  - 在 jQuery 1.0.3 或之後版本以及 3.5.0 之前版本中，將包含非受信任來源之 <option> 元素的 HTML (即使是在清理後) 傳送至 jQuery 的其中一個 DOM 操控方法 (即.html()、.append() 等)，可能會執行未受信任的程式碼。此問題已在 jQuery (3.5.0) 中得到修補。
    (CVE-2020-11023)

  - 在 rsync 中發現一個瑕疵。使用 `--safe-links` 選項時rsync 用戶端無法正確驗證從伺服器傳送的符號連結目的地中是否含有另一個符號連結。這會導致一個路徑遊走弱點其可導致所需目錄之外的任意檔案寫入。
    (CVE-2024-12088)

  - 在 Unbound 中發現一個弱點，這是由於預設權限不正確所致，可允許 unbound 群組之外的任何處理程序修改 unbound 執行階段設定。如果處理程序可透過 localhost 連線至連接埠 8953，則可變更 unbound.service 的設定。無權限的攻擊者可利用此缺陷操控執行中的執行個體，進而可能變更轉送工具，追踪本機解析器轉送的所有查詢，且在某些情況下，甚至會一起中斷解析。(CVE-2024-1488)

  - NLnet Labs Unbound 1.21.0 版及其之前的版本在處理含有非常大的 RRset (需要執行名稱壓縮) 的回覆時含有一個弱點。具有非常大 RRset 的惡意上游回應可導致 Unbound 花費大量時間，將名稱壓縮套用至下游回覆。這可導致效能降低，並最終在精心策劃的攻擊中造成拒絕服務。惡意執行者可利用此弱點，向 Unbound 查詢具有極大 RRset 之惡意區域的特製內容。在 Unbound 回覆查詢之前，它會嘗試套用名稱壓縮。名稱壓縮是一種會鎖定 CPU 的無限製作業，直到完成整個封包為止。Unbound 版本 1.21.1 對其願意針對每個封包執行的名稱壓縮計算次數引入了硬性限制。需要進一步壓縮的封包將導致封包半壓縮或截斷，即使對於大型訊息的 TCP 也是如此，以避免長時間鎖定 CPU。
    此變更不應影響正常的 DNS 流量。(CVE-2024-8508)

  - rsync 中包含路徑遊走弱點。此問題源於「--inc-recursive」選項啟用的行為，這是許多用戶端選項預設啟用的行為，並且即使用戶端未明確啟用，也可由伺服器啟用。使用「--inc-recursive」選項時，如果缺少適當的符號連結驗證，再加上針對每個檔案清單進行的重複資料刪除檢查，伺服器即可在用戶端的預定目的地目錄之外寫入檔案。惡意伺服器可將惡意檔案寫入以用戶端上有效目錄/路徑命名的任意位置。(CVE-2024-12087)

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

遠端主機上安裝的 AHV 低於 20230302.102005 版。因此會受到 NXSA-AHV-20230302.103032 公告中提及的多個弱點影響。

  - 在 jQuery 1.0.3 或之後版本以及 3.5.0 之前版本中，將包含非受信任來源之 <option> 元素的 HTML (即使是在清理後) 傳送至 jQuery 的其中一個 DOM 操控方法 (即.html()、.append() 等)，可能會執行未受信任的程式碼。此問題已在 jQuery (3.5.0) 中得到修補。
    (CVE-2020-11023)

  - 在 rsync 中發現一個瑕疵。使用 `--safe-links` 選項時rsync 用戶端無法正確驗證從伺服器傳送的符號連結目的地中是否含有另一個符號連結。這會導致一個路徑遊走弱點其可導致所需目錄之外的任意檔案寫入。
    (CVE-2024-12088)

  - 在 Unbound 中發現一個弱點，這是由於預設權限不正確所致，可允許 unbound 群組之外的任何處理程序修改 unbound 執行階段設定。如果處理程序可透過 localhost 連線至連接埠 8953，則可變更 unbound.service 的設定。無權限的攻擊者可利用此缺陷操控執行中的執行個體，進而可能變更轉送工具，追踪本機解析器轉送的所有查詢，且在某些情況下，甚至會一起中斷解析。(CVE-2024-1488)

  - NLnet Labs Unbound 1.21.0 版及其之前的版本在處理含有非常大的 RRset (需要執行名稱壓縮) 的回覆時含有一個弱點。具有非常大 RRset 的惡意上游回應可導致 Unbound 花費大量時間，將名稱壓縮套用至下游回覆。這可導致效能降低，並最終在精心策劃的攻擊中造成拒絕服務。惡意執行者可利用此弱點，向 Unbound 查詢具有極大 RRset 之惡意區域的特製內容。在 Unbound 回覆查詢之前，它會嘗試套用名稱壓縮。名稱壓縮是一種會鎖定 CPU 的無限製作業，直到完成整個封包為止。Unbound 版本 1.21.1 對其願意針對每個封包執行的名稱壓縮計算次數引入了硬性限制。需要進一步壓縮的封包將導致封包半壓縮或截斷，即使對於大型訊息的 TCP 也是如此，以避免長時間鎖定 CPU。
    此變更不應影響正常的 DNS 流量。(CVE-2024-8508)

  - rsync 中包含路徑遊走弱點。此問題源於「--inc-recursive」選項啟用的行為，這是許多用戶端選項預設啟用的行為，並且即使用戶端未明確啟用，也可由伺服器啟用。使用「--inc-recursive」選項時，如果缺少適當的符號連結驗證，再加上針對每個檔案清單進行的重複資料刪除檢查，伺服器即可在用戶端的預定目的地目錄之外寫入檔案。惡意伺服器可將惡意檔案寫入以用戶端上有效目錄/路徑命名的任意位置。(CVE-2024-12087)

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

遠端主機上安裝的 OpenSSL 為 3.3.3 之前版本。因此，它會受到 3.3.3 公告中提及的一個弱點影響。

  - 問題摘要：低階 GF(2^m) 橢圓曲線 API 搭配不受信任的欄位多項式明確值使用，可導致超出邊界記憶體讀取或寫入。影響摘要：超出邊界記憶體寫入可導致應用程式損毀，甚或可能導致遠端程式碼執行，然而，在我們所知的所有涉及橢圓曲線密碼編譯的協議中，要麼僅支援命名曲線，要麼如果支援明確的曲線參數，它們會指定無法代表有問題輸入值之二進位 (GF(2^m)) 曲線的 X9.62 編碼。因此，有弱點的應用程式存在的可能性很低。特別是，X9.62 編碼用於 X.509 憑證中的 ECC 金鑰，因此在處理 X.509 憑證的情境中不會發生有問題的輸入。任何有問題的使用案例都必須使用特殊曲線編碼。受影響的 API 包括：
    EC_GROUP_new_curve_GF2m()、EC_GROUP_new_from_params() 以及多種支援的 BN_GF2m_*() 函式。
    使用異常顯式二進位 (GF(2^m)) 曲線參數的應用程式，如果透過上述或類似的 API 使得能夠用零常數項表示無效的欄位多項式，可能會因為讀取或寫入超出陣列範圍而突然終止。無法輕易排除遠端程式碼執行。3.3、3.2、3.1 和 3.0 中的 FIPS 模組不受此問題影響。
    (CVE-2024-9143)

請注意，Nessus 並未測試此問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

遠端 Ubuntu 20.04 LTS / 22.04 LTS / 24.04 LTS 主機上安裝的套件受到 USN-7278-1 公告中所提及的多個弱點影響。

    George Pantelakis 和 Alicja Kario 發現 OpenSSL 在執行 ECDSA 簽章運算時有計時旁路。遠端攻擊者可能會利用此問題復原私人資料。
    (CVE-2024-13176)

    據發現，OpenSSL 在將低層級 GF(2^m) 橢圓曲線 API 用於欄位多項式不受信任的明確值時，未能正確處理某些記憶體作業。以這種不尋常的方式使用時，遠端攻擊者可利用此問題造成 OpenSSL 當機，進而引發拒絕服務或可能執行任意程式碼。(CVE-2024-9143)

Tenable 已直接從 Ubuntu 安全公告擷取前置描述區塊。

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

遠端主機上安裝的 OpenSSL 版本為 1.1.1zb 之前的版本。因此，它受到 1.1.1zb 公告中提及的一個弱點影響。

  - 問題摘要：低階 GF(2^m) 橢圓曲線 API 搭配不受信任的欄位多項式明確值使用，可導致超出邊界記憶體讀取或寫入。影響摘要：超出邊界記憶體寫入可導致應用程式損毀，甚或可能導致遠端程式碼執行，然而，在我們所知的所有涉及橢圓曲線密碼編譯的協議中，要麼僅支援命名曲線，要麼如果支援明確的曲線參數，它們會指定無法代表有問題輸入值之二進位 (GF(2^m)) 曲線的 X9.62 編碼。因此，有弱點的應用程式存在的可能性很低。特別是，X9.62 編碼用於 X.509 憑證中的 ECC 金鑰，因此在處理 X.509 憑證的情境中不會發生有問題的輸入。任何有問題的使用案例都必須使用特殊曲線編碼。受影響的 API 包括：
    EC_GROUP_new_curve_GF2m()、EC_GROUP_new_from_params() 以及多種支援的 BN_GF2m_*() 函式。
    使用異常顯式二進位 (GF(2^m)) 曲線參數的應用程式，如果透過上述或類似的 API 使得能夠用零常數項表示無效的欄位多項式，可能會因為讀取或寫入超出陣列範圍而突然終止。無法輕易排除遠端程式碼執行。3.3、3.2、3.1 和 3.0 中的 FIPS 模組不受此問題影響。
    (CVE-2024-9143)

請注意，Nessus 並未測試此問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

遠端主機上安裝的 OpenSSL 為 1.0.2zl 之前的版本。因此，它受到 1.0.2zl 公告中提及的一個弱點影響。

  - 問題摘要：低階 GF(2^m) 橢圓曲線 API 搭配不受信任的欄位多項式明確值使用，可導致超出邊界記憶體讀取或寫入。影響摘要：超出邊界記憶體寫入可導致應用程式損毀，甚或可能導致遠端程式碼執行，然而，在我們所知的所有涉及橢圓曲線密碼編譯的協議中，要麼僅支援命名曲線，要麼如果支援明確的曲線參數，它們會指定無法代表有問題輸入值之二進位 (GF(2^m)) 曲線的 X9.62 編碼。因此，有弱點的應用程式存在的可能性很低。特別是，X9.62 編碼用於 X.509 憑證中的 ECC 金鑰，因此在處理 X.509 憑證的情境中不會發生有問題的輸入。任何有問題的使用案例都必須使用特殊曲線編碼。受影響的 API 包括：
    EC_GROUP_new_curve_GF2m()、EC_GROUP_new_from_params() 以及多種支援的 BN_GF2m_*() 函式。
    使用異常顯式二進位 (GF(2^m)) 曲線參數的應用程式，如果透過上述或類似的 API 使得能夠用零常數項表示無效的欄位多項式，可能會因為讀取或寫入超出陣列範圍而突然終止。無法輕易排除遠端程式碼執行。3.3、3.2、3.1 和 3.0 中的 FIPS 模組不受此問題影響。
    (CVE-2024-9143)

請注意，Nessus 並未測試此問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

Use of the low-level GF(2m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only named curves are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low. In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an exotic curve encoding. The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions. Applications working with exotic explicit binary (GF(2m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

This plugin only works with Tenable.ot.
Please visit https://www.tenable.com/products/tenable-ot for more information.

ID	名稱	產品	系列	已發布	已更新	嚴重性
214031	EulerOS 2.0 SP10 : openssl (EulerOS-SA-2025-1026)	Nessus	Huawei Local Security Checks	2025/1/13	2025/5/23	high
211931	CBL Mariner 2.0 Security Update: hvloader / openssl (CVE-2024-9143)	Nessus	MarinerOS Local Security Checks	2024/11/28	2025/3/20	high
236922	EulerOS Virtualization 2.12.1 : openssl (EulerOS-SA-2025-1550)	Nessus	Huawei Local Security Checks	2025/5/17	2025/5/17	high
214168	EulerOS 2.0 SP9 : openssl (EulerOS-SA-2025-1041)	Nessus	Huawei Local Security Checks	2025/1/14	2025/5/23	high
240976	Nutanix AHV : Multiple Vulnerabilities (NXSA-AHV-20230302.101060)	Nessus	Misc.	2025/6/30	2025/7/1	high
241665	Nutanix AHV : Multiple Vulnerabilities (NXSA-AHV-20230302.103032)	Nessus	Misc.	2025/7/9	2025/7/10	high
234557	Oracle Essbase 多個弱點 (2025 年 4 月 CPU)	Nessus	Misc.	2025/4/17	2025/4/17	medium
240976	Nutanix AHV多個弱點 (NXSA-AHV-20230302.101060)	Nessus	Misc.	2025/6/30	2025/7/1	high
241665	Nutanix AHV多個弱點 (NXSA-AHV-20230302.103032)	Nessus	Misc.	2025/7/9	2025/7/10	high
209151	OpenSSL 3.3.0 < 3.3.3 弱點	Nessus	Web Servers	2024/10/16	2025/5/23	medium
216593	Ubuntu 20.04 LTS / 22.04 LTS / 24.04 LTS：OpenSSL 弱點 (USN-7278-1)	Nessus	Ubuntu Local Security Checks	2025/2/21	2025/5/23	high
209149	OpenSSL 1.1.1 < 1.1.1zb 弱點	Nessus	Web Servers	2024/10/16	2025/5/23	medium
209152	OpenSSL 1.0.2 < 1.0.2zl 弱點	Nessus	Web Servers	2024/10/16	2025/5/23	medium
502894	Siemens SIMATIC and SCALANCE Devices Out-of-bounds Write (CVE-2024-9143)	Tenable OT Security	Tenable.ot	2025/2/24	2025/11/13	medium

偵測

搜尋 Plugin

high

high

high

high

high

high

medium

high

high

medium

high

medium

medium

medium