遠端主機上安裝的 MySQL Enterprise Monitor 為 8.0.24 之前的 8.0.x 版。因此，會受到 2021 年 4 月 CPU 公告中提及的多個弱點影響。

  - Oracle MySQL 的 MySQL Enterprise Monitor 產品中存在的弱點 (元件：Monitoring: General (Apache Tomcat))。受到影響的支援版本是 8.0.23 和之前的版本。攻擊此弱點的難度較小，經由多個通訊協定存取網路的未經驗證攻擊者可藉此入侵 MySQL Enterprise Monitor。
    若成功攻擊此弱點，則攻擊者未經授權即可存取重要資料，或完整存取所有 MySQL Enterprise Monitor 可存取資料。(CVE-2020-17527)

  - Oracle MySQL 的 MySQL Enterprise Monitor 產品中存在的弱點 (元件：Monitoring: General (Apache Struts))。受到影響的支援版本是 8.0.23 和之前的版本。攻擊此弱點的難度較小，經由 HTTPS 存取網路的未經驗證攻擊者可藉此入侵 MySQL Enterprise Monitor。若成功攻擊此弱點，則可能導致接管 MySQL Enterprise Monitor (CVE-2020-17530)。

  - Oracle MySQL 的 MySQL Enterprise Monitor 產品中存在的弱點 (元件：Monitoring: General (OpenSSL))。
    受到影響的支援版本是 8.0.23 和之前的版本。攻擊此弱點有一定難度，經由 HTTPS 存取網路的未經驗證攻擊者可藉此入侵 MySQL Enterprise Monitor。若成功攻擊此弱點，則可能導致在未經授權的情況下建立、刪除或修改重要資料或所有 MySQL Enterprise Monitor 的可存取資料，並可在未經授權的情況下存取重要資料或完整存取所有 MySQL Enterprise Monitor 的可存取資料。(CVE-2021-3450)

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

遠端主機上安裝的 openssl11 為 1.1.1g-12 之前版本。因此，會受到 ALAS2-2021-1622 公告中所提及的多個弱點影響。

  - 如果從用戶端傳送惡意特製的重新交涉 ClientHello 訊息，OpenSSL TLS 伺服器可能會當機。如果 TLSv1.2 重新交涉 ClientHello 省略 signature_algorithms 延伸模組 (出現在初始 ClientHello 中)，但包含一個 signature_algorithms_cert 延伸模組，則會導致 NULL 指標解除參照，進而導致當機和拒絕服務攻擊。伺服器只有在已啟用 TLSv1.2 和重新交涉 (預設組態) 的情況下，才會受到影響。OpenSSL TLS 用戶端不受此問題影響。所有 OpenSSL 1.1.1 版本皆受到此問題影響。這些版本的使用者應升級至 OpenSSL 1.1.1k。OpenSSL 1.0.2 不受此問題影響。已在 OpenSSL 1.1.1k 中修復 (受影響的是 1.1.1-1.1.1j)。(CVE-2021-3449)

  - X509_V_FLAG_X509_STRICT 旗標針對憑證鏈中存在的憑證啟用其他安全性檢查。預設未設定。從 OpenSSL 1.1.1h 版開始，系統已新增一項檢查作為附加的嚴格檢查，以禁止鏈結中已明確編碼橢圓曲線參數的憑證。此檢查的實作中有一個錯誤，這表示先前確認鏈結中的憑證為有效 CA 憑證的檢查結果被覆寫。這可有效繞過非 CA 憑證不得發出其他憑證的檢查。如果已設定用途，則隨後有機會檢查憑證是否為有效的 CA 憑證。libcrypto 中實作的所有具名用途值都會執行此檢查。因此，在設定用途的情況下，即使已使用 strict 旗標，憑證鏈仍會遭到拒絕。在 libssl 用戶端和伺服器憑證驗證常式中，預設有一個用途，但應用程式可以覆寫或移除該用途。若要受到此問題影響，應用程式必須明確設定 X509_V_FLAG_X509_STRICT 驗證旗標，且不得設定憑證驗證的用途，或者若為 TLS 用戶端或伺服器應用程式，則不得覆寫預設用途。OpenSSL 1.1.1h 及更新版本受到此問題影響。這些版本的使用者應升級至 OpenSSL 1.1.1k。
    OpenSSL 1.0.2 不受此問題影響。已在 OpenSSL 1.1.1k 中修正 (受影響的是 1.1.1h-1.1.1j)。
    (CVE-2021-3450)

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

遠端 CentOS Linux 8 主機上安裝的套件受到 CESA-2021: 1024 公告中提及的多個弱點影響。

  - openssl：處理 signature_algorithms 時會發生 NULL 指標解除參照的問題 (CVE-2021-3449)

  - openssl：X509_V_FLAG_X509_STRICT 存在 CA 憑證檢查繞過問題 (CVE-2021-3450)

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

遠端 Redhat Enterprise Linux 8 主機上安裝的套件受到 RHSA-2021: 1189 公告中提及的多個弱點影響。

  - openssl：處理 signature_algorithms 時會發生 NULL 指標解除參照的問題 (CVE-2021-3449)

  - openssl：X509_V_FLAG_X509_STRICT 存在 CA 憑證檢查繞過問題 (CVE-2021-3450)

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

因此，會受到 ALAS2-2024-2502 公告中所提及的多個弱點影響。

    在 openssl 中發現 Null 指標解除參照缺陷。遠端攻擊者若能控制 GENERAL_NAME_cmp 函式的引數，造成使用 openssl 編譯的應用程式毀損，進而導致拒絕服務。此弱點對系統可用性威脅最大。(CVE-2020-1971)

    在某些情況下，若輸入長度接近平台上整數的最大允許長度，呼叫 EVP_CipherUpdate、EVP_EncryptUpdate 和 EVP_DecryptUpdate 可能造成輸出長度引數溢位。在此類情況下，函式呼叫的傳回值將為 1 (表示成功)，但輸出長度值將為負值。這可造成應用程式的行為不正確或損毀。
    (CVE-2021-23840)

    OpenSSL 公開 API 函式 X509_issuer_and_serial_hash() 嘗試根據 X509 憑證中所含的簽發者和序號資料建立唯一的雜湊值。但是，它無法正確處理剖析簽發者欄位時可能發生的任何錯誤 (如果簽發者欄位遭到惡意建構，則可能發生此類錯誤)。之後，這可能導致 NULL 指標解除參照和當機，進而導致潛在的拒絕服務攻擊。(CVE-2021-23841)

    在 openssl 中發現一個瑕疵。如果用戶端傳送 TLSv1.2 重新協商 ClientHello 並省略 signature_algorithms 延伸模組，但是包含 signature_algorithms_cert 延伸模組，則可發生伺服器當機和拒絕服務攻擊。此弱點對系統可用性威脅最大。
    (CVE-2021-3449)

    在 openssl 中發現一個瑕疵。未啟用會對憑證鏈結中存在之憑證啟用其他安全性檢查的旗標，使得驗證鏈結中憑證是否為有效 CA 憑證的確認步驟被略過。此弱點對資料機密性與完整性的威脅最大。(CVE-2021-3450)

    據發現，openssl 會假設 ASN.1 字串是以 NULL 終止。惡意執行者可以強制應用程式使用特製的非 NUL 終止字串呼叫 openssl 函式，刻意遭遇此錯誤，進而可能導致應用程式損毀，造成拒絕服務攻擊，或者可能記憶體洩漏。此弱點對資料機密性及系統可用性的威脅最大。(CVE-2021-3712)

    BN_mod_sqrt() 函式專用於計算模組化平方根，其中包含一個可導致其針對非質數模數永遠執行迴圈的錯誤。在內部剖析包含壓縮形式的橢圓曲線公開金鑰或具有以壓縮形式編碼之基點的顯式橢圓曲線參數時，會使用此函式。透過建構具有無效顯式曲線參數的憑證，可能會觸發無限迴圈。由於憑證剖析發生在驗證憑證簽章之前，因此任何剖析外部提供之憑證的處理程序都可能遭受拒絕服務攻擊。也可以在剖析建構的私密金鑰時造成無限迴圈，因為這些金鑰中可能包含顯式橢圓曲線參數。因此，易受攻擊的情況包括：使用伺服器憑證的 TLS 伺服器 - 使用用戶端憑證的 TLS 伺服器 - 從客戶處取得憑證或私密金鑰的主機供應商 - 剖析來自使用者憑證要求的認證機構 - 剖析 ASN.1 橢圓曲線參數的任何其他應用程式，以及使用 BN_mod_sqrt() 的任何其他應用程式 (其中攻擊者可控制容易受到此 DoS 問題影響的參數值)。在 OpenSSL 1.0.2 版本中，最初剖析憑證期間並未剖析公開金鑰，進而導致觸發無限迴圈變得略微困難。不過，任何需要憑證公開金鑰的作業都會觸發無限迴圈。特別是，攻擊者可在驗證憑證簽章期間使用自我簽署憑證觸發迴圈。OpenSSL 1.0.2、 1.1.1 和 3.0 會受到此問題影響。此問題已在 2022 年 3 月 15 日發布的 1.1.1n 和 3.0.2 版本中得到解決。已在 OpenSSL 3.0.2 中修復 (受影響的是 3.0.0、3.0.1)。已在 OpenSSL 1.1.1n 中修復 (受影響的是 1.1.1-1.1.1m)。已在 OpenSSL 1.0.2zd 中修正 (受影響的是 1.0.2-1.0.2zc)。(CVE-2022-0778) (CVE-2022-0778)

    c_rehash 指令碼未正確清理殼層中繼字元以防止命令插入。某些作業系統會以自動執行的方式發佈此指令碼。在這類作業系統上，攻擊者可以透過指令碼的權限執行任意命令。c_rehash 指令碼的使用已過時，應由 OpenSSL rehash 命令列工具取代。
    已在 OpenSSL 3.0.3 中修復 (受影響的是 3.0.0、3.0.1、3.0.2)。已在 OpenSSL 1.1.1o 中修復 (受影響的是 1.1.1-1.1.1n)。
    已在 OpenSSL 1.0.2ze 中修復 (受影響的是 1.0.2-1.0.2zd)。(CVE-2022-1292)

    在 OpenSSL 中發現一個瑕疵。CVE-2022-1292 中的問題未在 `c_rehash` 指令碼中的其他位置發現雜湊憑證的檔案名稱可能會傳遞至透過 shell 執行的命令。某些作業系統會以自動執行的方式發佈此指令碼。在這些作業系統中，此瑕疵會使得攻擊者能夠透過指令碼的權限執行任意命令。(CVE-2022-2068)

    在某些情況下，使用 AES-NI 組件最佳化實作的 32 位元 x86 平台的 AES OCB 模式將不會加密完整的資料。這可能會洩漏預先存在於未寫入記憶體中的 16 位元組資料。在就地加密的特殊情況下，會洩漏純文字的 16 位元組。由於 OpenSSL 不支援適用於 TLS 和 DTLS 的 OCB 型加密套件，因此兩者均不受影響。已在 OpenSSL 3.0.5 中修復 (受影響的是 3.0.0-3.0.4)。已在 OpenSSL 1.1.1q 中修正 (受影響的是 1.1.1-1.1.1p)。(CVE-2022-2097)

    OpenSSL RSA Decryption 實作中存在計時型旁路，其足可在 Bleichenbacher 式攻擊中跨網路復原密文。若要成功解密，攻擊者必須能夠傳送大量的試用訊息以進行解密。此問題會影響所有 RSA 填補模式：PKCS#1 v1.5、RSA-OEAP 和 RSASVE。(CVE-2022-4304)

    PEM_read_bio_ex() 函式會從 BIO 讀取 PEM 檔案，並剖析和解碼名稱 (例如：
    CERTIFICATE)、任何標題資料和負載資料。如果函式成功運行，則使用包含相關解碼資料之緩衝區的指標填入 name_out、標頭和資料引數。
    呼叫者負責釋放這些緩衝區。攻擊者可以建構會產生 0 位元組承載資料的 PEM 檔案。在此情況下，PEM_read_bio_ex() 會傳回失敗程式碼，但會在標頭引數中填入已釋放的緩衝區指標。如果呼叫者也釋放此緩衝區，則會發生雙重釋放。這很可能會導致當機。能夠提供惡意 PEM 檔案進行剖析的攻擊者可利用此弱點發動拒絕服務攻擊。

    PEM_read_bio() 和 PEM_read() 函式是 PEM_read_bio_ex() 的簡單包裝函式，因此這些函式也會直接受到影響。

    其他一些 OpenSSL 函式也會間接呼叫這些函式，包括同樣容易遭受攻擊的 PEM_X509_INFO_read_bio_ex() 和 SSL_CTX_use_serverinfo_file()。若在 OpenSSL 內部使用部分此類函式，則不會受到影響，因為如果 PEM_read_bio_ex() 傳回失敗程式碼，呼叫者將不會釋放標頭引數。這些位置包括 PEM_read_bio_TYPE() 函式以及 OpenSSL 3.0 中引入的解碼器。

    OpenSSL asn1parse 命令行應用程式也受此問題影響。(CVE-2022-4450)

    在 OpenSSL 的 BIO_new_NDEF 函式中發現一個釋放後使用弱點。公開 API 函式 BIO_new_NDEF 是用於透過 BIO 串流 ASN.1 資料的協助程式函式。此函式主要供 OpenSSL 內部使用，以支援 SMIME、CMS 和 PKCS7 串流功能，但也可能由終端使用者應用程式直接呼叫。此函式會接收來自呼叫者的 BIO，並在前面附加新的 BIO_f_asn1 篩選器 BIO 以形成 BIO 鏈結，然後將 BIO 鏈結的新標頭傳回給呼叫者。在某些情況下。例如，如果 CMS 收件人公開金鑰無效，則新篩選器 BIO 會被釋放，並且該函式會傳回 NULL 結果，表明失敗。但在此情況下，BIO 鏈結未經正確清理，且呼叫者傳送的 BIO 仍保留先前釋放的篩選器 BIO 的內部指標。如果呼叫者隨後呼叫 BIO 上的 BIO_pop()，將會發生釋放後使用錯誤，進而可能導致當機。(CVE-2023-0215)

    當 OpenSSL X.400 位址在 X.509 GeneralName 內部進行處理時，在 OpenSSL 中發現有類型混淆弱點。啟用 CRL 檢查時 (例如應用程式設定 X509_V_FLAG_CRL_CHECK 旗標)，此弱點可能允許攻擊者向 memcmp 呼叫傳遞任意指標，使其能夠讀取記憶體內容或造成拒絕服務攻擊。在大多數情況下，攻擊者需要同時提供憑證鍊和 CRL，以上兩者都不需要有效的簽章。如果攻擊者只控制其中一個輸入，則另一個輸入必須已包含 X.400 位址作為 CRL 發佈點，此情況並不常見。在此情況下，此弱點有可能僅會影響已實作透過網路擷取 CRL 這一功能的應用程式。(CVE-2023-0286)

    在所有受支援的 OpenSSL 版本中發現一個與驗證包含原則限制的 X.509 憑證鏈相關的安全性弱點。攻擊者可能會建立惡意憑證鏈，觸發計算資源的指數使用，進而惡意利用此弱點，對受影響的系統發動拒絕服務 (DoS) 攻擊。原則處理預設爲禁用狀態，但若將 -policy 引數傳遞至命令行公用程式，或呼叫 X509_VERIFY_PARAM_set1_policies() 函式，即可啟用原則處理。(CVE-2023-0464)

    驗證憑證時使用非預設選項的應用程式可能容易遭受惡意 CA 的攻擊，進而規避特定檢查。OpenSSL 會以無訊息方式忽略分葉憑證中的無效憑證原則，並略過該憑證的其他憑證原則檢查。惡意 CA 可利用此弱點，刻意宣告無效的憑證原則，以完全規避憑證的原則檢查。原則處理預設爲禁用狀態，但若將 -policy 引數傳遞至命令行公用程式，或呼叫 X509_VERIFY_PARAM_set1_policies() 函式，即可啟用原則處理。(CVE-2023-0465)

    X509_VERIFY_PARAM_add0_policy() 函式被記錄為在進行憑證驗證時隱含啟用憑證原則檢查。不過，此函式的實作並未啟用這一檢查，因而會造成含有無效或錯誤原則的憑證通過憑證驗證。
    由於突然啟用原則檢查可能會中斷現有部署，因此決定保留 X509_VERIFY_PARAM_add0_policy() 函式的現有行為。需要 OpenSSL 才能執行憑證原則檢查的應用程式需要使用 X509_VERIFY_PARAM_set1_policy()，或透過以 X509_V_FLAG_POLICY_CHECK 旗標引數呼叫 X509_VERIFY_PARAM_set_flags()，來明確啟用原則檢查。
    OpenSSL 中預設停用憑證原則檢查，應用程式亦未普遍使用此檢查。
    (CVE-2023-0466)

    問題摘要：處理某些特製的 ASN.1 物件識別碼或包含這些識別碼的資料可能會非常緩慢。

    影響摘要：對於直接使用 OBJ_obj2txt() 或使用任何 OpenSSL 子系統 OCSP、PKCS7/SMIME、CMS、CMP/CRMF 或 TS 的應用程式，它們在處理這些訊息時可能造成拒絕服務。

    OBJECT IDENTIFIER 由一系列數字 (子識別碼) 組成，其中大部分沒有大小限制。OBJ_obj2txt() 可用於將以 DER 編碼形式 (使用 OpenSSL 類型 ASN1_OBJECT) 提供的 ASN.1 OBJECT IDENTIFIER 轉譯為其規範數值文字形式，即以句點分隔的十進位形式的 OBJECT IDENTIFIER 子識別碼。

    當 OBJECT IDENTIFIER 中的其中一個子識別碼非常大 (大得離譜，佔用數十或數百 KiB) 時，在文字中轉譯為十進位數字可能需要很長的時間。時間複雜度為 O(n^2)，其中「n」是以位元組 (*) 為單位的子識別碼大小。

    OpenSSL 3.0 版引入了使用字串形式的名稱/識別碼擷取密碼編譯演算法的支援。這包括使用規範數值文字形式的 OBJECT IDENTIFIER 作為擷取演算法的識別碼。

    此類 OBJECT IDENTIFIER 可透過 ASN.1 結構 AlgorithmIdentifier 接收，該結構常用於多個通訊協定，以指定應使用何種密碼編譯演算法來簽署或驗證、加密或解密，或摘要式傳遞的資料。

    直接使用未受信任的資料呼叫 OBJ_obj2txt() 的應用程式會受到任何 OpenSSL 版本的影響。如果僅用於顯示目的，則認為低嚴重性。

    在 OpenSSL 3.0 和更新版本中，這會影響子系統 OCSP、PKCS7/SMIME、CMS、CMP/CRMF 或 TS。它也會影響處理 X.509 憑證的任何項目，包括驗證其簽章等簡單項目。

    對 TLS 的影響相對較低，因為所有版本的 OpenSSL 在對等端的憑證鏈上都有 100KiB 的限制。此外，這只會影響已明確啟用用戶端驗證的用戶端或伺服器。

    在 OpenSSL 1.1.1 和 1.0.2 版中，這只會影響顯示不同的物件，例如 X.509 憑證。我們假設此問題不會以會造成拒絕服務的方式發生，因此這些版本不會受到此問題的影響，進而被視為低嚴重性。(CVE-2023-2650)

    問題摘要：檢查過長的 DH 金鑰或參數時可能會非常緩慢。

    影響摘要：使用 DH_check()、DH_check_ex() 或 EVP_PKEY_param_check() 函式檢查 DH 金鑰或 DH 參數的應用程式可能會遇到長時間延遲。如果要檢查的金鑰或參數是從未受信任的來源取得，這可能會導致拒絕服務。

    DH_check() 函式會對 DH 參數執行各種檢查，其中一項檢查會確認模數 (「p」參數) 不是太大。嘗試使用非常大的模數時執行速度會變慢，且 OpenSSL 通常不會使用長度超過 10,000 位元的模數。

    不過，DH_check() 函式會檢查已提供金鑰或參數的多個方面。
    有些檢查會使用提供的模數值，即使已發現此模數值過大亦然。

    應用程式如果呼叫 DH_check() 並提供從未受信任的來源取得之金鑰或參數，可能容易遭受拒絕服務攻擊。

    DH_check() 函式本身會受到一些其他 OpenSSL 函式的呼叫。呼叫其他任何函式的應用程式可能會受到類似影響。受此問題影響的其他函式為 DH_check_ex() 和 EVP_PKEY_param_check()。

    使用「-check」選項時，OpenSSL dhparam 和 pkeyparam 命令行應用程式也容易受到影響。

    OpenSSL SSL/TLS 實作不受此問題影響。OpenSSL 3.0 和 3.1 FIPS 提供者不受此問題影響。(CVE-2023-3446)

    問題摘要：產生過長的 X9.42 DH 金鑰或檢查過長的 X9.42 DH 金鑰或參數時可能會非常緩慢。

    - 問題摘要：使用 DH_generate_key() 函式產生 X9.42 DH 金鑰的應用程式可能會遇到長時間延遲。同樣地，使用 DH_check_pub_key()、DH_check_pub_key_ex() 或 EVP_PKEY_public_check() 檢查 X9.42 DH 金鑰或 X9.42 DH 參數的應用程式可能會遇到長時間延遲。如果正在進行檢查的金鑰或是參數已經透過未受信任的來源取得，如此可能導致拒絕。

    雖然 DH_check() 會執行所有必要的檢查 (截至 CVE-2023-3817)，但 DH_check_pub_key() 並不會進行任何此類檢查，因此容易受到過大的 P 和 Q 參數的影響。

    同樣地，當 DH_generate_key() 執行檢查是否有過大的 P 時，它不會檢查過大的 Q。

    應用程式如果呼叫 DH_generate_key() 或 DH_check_pub_key() 並提供從未受信任之來源取得的金鑰或參數，則容易遭受拒絕服務攻擊。

    DH_generate_key() 和 DH_check_pub_key() 也會被其他許多 OpenSSL 函式呼叫。呼叫任何其他函式的應用程式亦可能會受到類似影響。受此問題影響的其他函式包括 DH_check_pub_key_ex()、EVP_PKEY_public_check() 和 EVP_PKEY_generate()。

    使用 -pubcheck 選項時的 OpenSSL pkey 命令行應用程式，以及 OpenSSL genpkey 命令行應用程式也容易受到影響。

    OpenSSL SSL/TLS 實作不受此問題影響。

    OpenSSL 3.0 和 3.1 FIPS 提供者不受此問題影響。(CVE-2023-5678)

Tenable 已直接從所測試產品的安全公告擷取前置描述區塊。

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

According to its self-reported version, the Tenable Nessus agent running on the remote host is prior to 8.2.4. It is, therefore, affected by multiple vulnerabilities. Nessus Agent leverages third-party software to help provide underlying functionality. Two separate third-party components (OpenSSL and   sqlite) were found to contain vulnerabilities, and updated versions have been made available by the providers.

Out of caution and in line with good practice, Tenable opted to upgrade the bundled libraries to address the potential impact of these issues. Nessus Agent 8.2.4 will update OpenSSL to version 1.1.1k and sqlite to version 3.34.1 to address the identified vulnerabilities.

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

The 8.0.23 and prior versions of MySQL Connectors installed on the remote host are affected by a vulnerability as referenced in the July 2020 CPU advisory. A vulnerability in the MySQL Connectors product of Oracle MySQL (components:
Connector/C++ (OpenSSL) and Connector/ODBC (OpenSSL)). Supported versions that are affected are 8.0.23 and prior. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all MySQL Connectors accessible data as well as unauthorized access to critical data or complete access to all MySQL Connectors accessible data.

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

Oracle reports :

This Critical Patch Update contains 41 new security patches for Oracle MySQL. 10 of these vulnerabilities may be remotely exploitable without authentication, i.e., may be exploited over a network without requiring user credentials. The highest CVSS v3.1 Base Score of vulnerabilities affecting Oracle MySQL is 8.8.

MariaDB is affected by CVE-2021-2372 and CVE-2021-2389 only.

An update of the openssl package has been released.

MySQL Enterprise Monitor installed on the remote host is 8.0.x prior to 8.0.24. Therefore, it's affected by multiple vulnerabilities as referenced in the April 2021 CPU advisory.

  - Vulnerability in the MySQL Enterprise Monitor product of Oracle MySQL (component: Monitoring: General     (Apache Tomcat)). Supported versions that are affected are 8.0.23 and prior. Easily exploitable vulnerability     allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Enterprise Monitor.
    Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to     all MySQL Enterprise Monitor accessible data (CVE-2020-17527).

  - Vulnerability in the MySQL Enterprise Monitor product of Oracle MySQL (component: Monitoring: General     (Apache Struts)). Supported versions that are affected are 8.0.23 and prior. Easily exploitable vulnerability     allows unauthenticated attacker with network access via HTTPS to compromise MySQL Enterprise Monitor. Successful     attacks of this vulnerability can result in takeover of MySQL Enterprise Monitor (CVE-2020-17530).

  - Vulnerability in the MySQL Enterprise Monitor product of Oracle MySQL (component: Monitoring: General (OpenSSL)).
    Supported versions that are affected are 8.0.23 and prior. Difficult to exploit vulnerability allows     unauthenticated attacker with network access via HTTPS to compromise MySQL Enterprise Monitor. Successful attacks     of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or     all MySQL Enterprise Monitor accessible data as well as unauthorized access to critical data or complete access     to all MySQL Enterprise Monitor accessible data (CVE-2021-3450).

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 multiple vulnerabilities as referenced in the ALAS2-2021-1622 advisory.

    A flaw was found in openssl. A server crash and denial of service attack could occur if a client sends a     TLSv1.2 renegotiation ClientHello and omits the signature_algorithms extension but includes a     signature_algorithms_cert extension. The highest threat from this vulnerability is to system availability.
    (CVE-2021-3449)

    A flaw was found in openssl. The flag that enables additional security checks of certificates present in a     certificate chain was not enabled allowing a confirmation step to verify that certificates in the chain     are valid CA certificates is bypassed. The highest threat from this vulnerability is to data     confidentiality and integrity. (CVE-2021-3450)

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 CentOS Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the CESA-2021:1024 advisory.

  - openssl: NULL pointer dereference in signature_algorithms processing (CVE-2021-3449)

  - openssl: CA certificate check bypass with X509_V_FLAG_X509_STRICT (CVE-2021-3450)

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

Node.js reports : OpenSSL - CA certificate check bypass with X509_V_FLAG_X509_STRICT (High) (CVE-2021-3450) This is a vulnerability in OpenSSL which may be exploited through Node.js. You can read more about it in https://www.openssl.org/news/secadv/20210325.txt OpenSSL - NULL pointer deref in signature_algorithms processing (High) (CVE-2021-3449) This is a vulnerability in OpenSSL which may be exploited through Node.js. You can read more about it in https://www.openssl.org/news/secadv/20210325.txt npm upgrade - Update y18n to fix Prototype-Pollution (High) (CVE-2020-7774) This is a vulnerability in the y18n npm module which may be exploited by prototype pollution. You can read more about it in https://github.com/advisories/GHSA-c4w7-xm78-47vh

The remote Redhat Enterprise Linux 8 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2021:1189 advisory.

    The redhat-virtualization-host packages provide the Red Hat Virtualization Host. These packages include     redhat-release-virtualization-host, ovirt-node, and rhev-hypervisor. Red Hat Virtualization Hosts (RHVH)     are installed using a special build of Red Hat Enterprise Linux with only the packages required to host     virtual machines. RHVH features a Cockpit user interface for monitoring the host's resources and     performing administrative tasks.

    The ovirt-node-ng packages provide the Red Hat Virtualization Host. These packages include redhat-release-     virtualization-host, ovirt-node, and rhev-hypervisor. Red Hat Virtualization Hosts (RHVH) are installed     using a special build of Red Hat Enterprise Linux with only the packages required to host virtual     machines. RHVH features a Cockpit user interface for monitoring the host's resources and performing     administrative tasks.

    Changes to the redhat-release-virtualization-host component:

    * Previously, the redhat-support-tool was missing from the RHV-H 4.4 package.
    In this release, the redhat-support-tool has been added. (BZ#1928607)

    Security Fix(es):

    * openssl: NULL pointer dereference in signature_algorithms processing (CVE-2021-3449)

    * openssl: CA certificate check bypass with X509_V_FLAG_X509_STRICT (CVE-2021-3450)

    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 these issues but has instead relied only on the application's self-reported version number.

The remote Alibaba Cloud Linux 3 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALINUX3-SA-2021:0021 advisory.

    Package updates are available for Alibaba Cloud Linux 3 that fix the following vulnerabilities:

    CVE-2021-3449:
    An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a     client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was     present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL     pointer dereference will result, leading to a crash and a denial of service attack. A server is only     vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS     clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of     these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in     OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).

    CVE-2021-3450:
    The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a     certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow     certificates in the chain that have explicitly encoded elliptic curve parameters was added as an     additional strict check. An error in the implementation of this check meant that the result of a previous     check to confirm that certificates in the chain are valid CA certificates was overwritten. This     effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a     purpose has been configured then there is a subsequent opportunity for checks that the certificate is a     valid CA. All of the named purpose values implemented in libcrypto perform this check. Therefore, where     a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A     purpose is set by default in libssl client and server certificate verification routines, but it can be     overridden or removed by an application. In order to be affected, an application must explicitly set the     X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification     or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions     1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k.
    OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).

Tenable has extracted the preceding description block directly from the Alibaba Cloud 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.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2024-2502 advisory.

    A null pointer dereference flaw was found in openssl. A remote attacker, able to control the arguments of     the GENERAL_NAME_cmp function, could cause the application, compiled with openssl to crash resulting in a     denial of service. The highest threat from this vulnerability is to system availability. (CVE-2020-1971)

    Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument     in some cases where the input length is close to the maximum permissible length for an integer on the     platform. In such cases the return value from the function call will be 1 (indicating success), but the     output length value will be negative. This could cause applications to behave incorrectly or crash.
    (CVE-2021-23840)

    The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based     on the issuer and serial number data contained within an X509 certificate. However it fails to correctly     handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is     maliciously constructed). This may subsequently result in a NULL pointer deref and a crash leading to a     potential denial of service attack. (CVE-2021-23841)

    A flaw was found in openssl. A server crash and denial of service attack could occur if a client sends a     TLSv1.2 renegotiation ClientHello and omits the signature_algorithms extension but includes a     signature_algorithms_cert extension. The highest threat from this vulnerability is to system availability.
    (CVE-2021-3449)

    A flaw was found in openssl. The flag that enables additional security checks of certificates present in a     certificate chain was not enabled allowing a confirmation step to verify that certificates in the chain     are valid CA certificates is bypassed. The highest threat from this vulnerability is to data     confidentiality and integrity. (CVE-2021-3450)

    It was found that openssl assumed ASN.1 strings to be NUL terminated. A malicious actor may be able to     force an application into calling openssl function with a specially crafted, non-NUL terminated string to     deliberately hit this bug, which may result in a crash of the application, causing a Denial of Service     attack, or possibly, memory disclosure. The highest threat from this vulnerability is to data     confidentiality and system availability. (CVE-2021-3712)

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

    The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This     script is distributed by some operating systems in a manner where it is automatically executed. On such     operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of     the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool.
    Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n).
    Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd). (CVE-2022-1292)

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

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

    A timing-based side channel exists in the OpenSSL RSA Decryption implementation, which could be sufficient     to recover a ciphertext across a network in a Bleichenbacher style attack. To achieve a successful     decryption, an attacker would have to be able to send a very large number of trial messages for     decryption. This issue affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP, and RSASVE. (CVE-2022-4304)

    The function PEM_read_bio_ex() reads a PEM file from a BIO and parses anddecodes the name (e.g.
    CERTIFICATE), any header data and the payload data.If the function succeeds then the name_out,     header and data arguments arepopulated with pointers to buffers containing the relevant decoded data.
    Thecaller is responsible for freeing those buffers. It is possible to construct aPEM file that results in     0 bytes of payload data. In this case PEM_read_bio_ex()will return a failure code but will populate the     header argument with a pointerto a buffer that has already been freed. If the caller also frees this     bufferthen a double free will occur. This will most likely lead to a crash. Thiscould be exploited by an     attacker who has the ability to supply malicious PEMfiles for parsing to achieve a denial of service     attack.

    The functions PEM_read_bio() and PEM_read() are simple wrappers aroundPEM_read_bio_ex() and therefore     these functions are also directly affected.

    These functions are also called indirectly by a number of other OpenSSLfunctions including     PEM_X509_INFO_read_bio_ex() andSSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL     internaluses of these functions are not vulnerable because the caller does not free theheader argument if     PEM_read_bio_ex() returns a failure code. These locationsinclude the PEM_read_bio_TYPE() functions as well     as the decoders introduced inOpenSSL 3.0.

    The OpenSSL asn1parse command line application is also impacted by this issue. (CVE-2022-4450)

    A use-after-free vulnerability was found in OpenSSL's BIO_new_NDEF function. The public API function     BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally     by OpenSSL to support the SMIME, CMS, and PKCS7 streaming capabilities, but it may also be called directly     by end-user applications. The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter     BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the     caller. Under certain conditions. For example, if a CMS recipient public key is invalid, the new filter     BIO is freed, and the function returns a NULL result indicating a failure. However, in this case, the BIO     chain is not properly cleaned up, and the BIO passed by the caller still retains internal pointers to the     previously freed filter BIO. If the caller then calls BIO_pop() on the BIO, a use-after-free will occur,     possibly resulting in a crash. (CVE-2023-0215)

    A type confusion vulnerability was found in OpenSSL when OpenSSL X.400 addresses processing inside an     X.509 GeneralName. When CRL checking is enabled (for example, the application sets the     X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a     memcmp call, enabling them to read memory contents or cause a denial of service. In most cases, the attack     requires the attacker to provide both the certificate chain and CRL, of which neither needs a valid     signature. If the attacker only controls one of these inputs, the other input must already contain an     X.400 address as a CRL distribution point, which is uncommon. In this case, this vulnerability is likely     only to affect applications that have implemented their own functionality for retrieving CRLs over a     network. (CVE-2023-0286)

    A security vulnerability has been identified in all supported versions of OpenSSL related to the     verification of X.509 certificate chains that include policy constraints. Attackers may be able to exploit     this vulnerability by creating a malicious certificate chain that triggers exponential use of     computational resources, leading to a denial-of-service (DoS) attack on affected systems. Policy     processing is disabled by default but can be enabled by passing the `-policy' argument to the command line     utilities or by calling the `X509_VERIFY_PARAM_set1_policies()' function. (CVE-2023-0464)

    Applications that use a non-default option when verifying certificates may be vulnerable to an attack from     a malicious CA to circumvent certain checks. Invalid certificate policies in leaf certificates are     silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A     malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent     policy checking on the certificate altogether. Policy processing is disabled by default but can be enabled     by passing the `-policy' argument to the command line utilities or by calling the     `X509_VERIFY_PARAM_set1_policies()' function. (CVE-2023-0465)

    The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy     check when doing certificate verification. However the implementation of the function does not enable the     check which allows certificates with invalid or incorrect policies to pass the certificate verification.
    As suddenly enabling the policy check could break existing deployments it was decided to keep the existing     behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to     perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the     policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument.
    Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
    (CVE-2023-0466)

    Issue summary: Processing some specially crafted ASN.1 object identifiers ordata containing them may be     very slow.

    Impact summary: Applications that use OBJ_obj2txt() directly, or use any ofthe OpenSSL subsystems OCSP,     PKCS7/SMIME, CMS, CMP/CRMF or TS with no messagesize limit may experience notable to very long delays when     processing thosemessages, which may lead to a Denial of Service.

    An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers -most of which have no size     limit.  OBJ_obj2txt() may be used to translatean ASN.1 OBJECT IDENTIFIER given in DER encoding form (using     the OpenSSLtype ASN1_OBJECT) to its canonical numeric text form, which are thesub-identifiers of the     OBJECT IDENTIFIER in decimal form, separated byperiods.

    When one of the sub-identifiers in the OBJECT IDENTIFIER is very large(these are sizes that are seen as     absurdly large, taking up tens or hundredsof KiBs), the translation to a decimal number in text may take a     very longtime.  The time complexity is O(n^2) with 'n' being the size of thesub-identifiers in bytes (*).

    With OpenSSL 3.0, support to fetch cryptographic algorithms using names /identifiers in string form was     introduced.  This includes using OBJECTIDENTIFIERs in canonical numeric text form as identifiers for     fetchingalgorithms.

    Such OBJECT IDENTIFIERs may be received through the ASN.1 structureAlgorithmIdentifier, which is commonly     used in multiple protocols to specifywhat cryptographic algorithm should be used to sign or verify,     encrypt ordecrypt, or digest passed data.

    Applications that call OBJ_obj2txt() directly with untrusted data areaffected, with any version of     OpenSSL.  If the use is for the mere purposeof display, the severity is considered low.

    In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME,CMS, CMP/CRMF or TS.  It also     impacts anything that processes X.509certificates, including simple things like verifying its signature.

    The impact on TLS is relatively low, because all versions of OpenSSL have a100KiB limit on the peer's     certificate chain.  Additionally, this onlyimpacts clients, or servers that have explicitly enabled     clientauthentication.

    In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects,such as X.509 certificates.  This     is assumed to not happen in such a waythat it would cause a Denial of Service, so these versions are     considerednot affected by this issue in such a way that it would be cause for concern,and the severity is     therefore considered low. (CVE-2023-2650)

    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 longdelays. Where the key or parameters that are being     checked have been obtainedfrom an untrusted source this may lead to a Denial of Service.

    The function DH_check() performs various checks on DH parameters. One of thosechecks confirms that the     modulus ('p' parameter) is not too large. Trying to usea very large modulus is slow and OpenSSL will not     normally use a modulus whichis over 10,000 bits in length.

    However the DH_check() function checks numerous aspects of the key or parametersthat have been supplied.
    Some of those checks use the supplied modulus valueeven if it has already been found to be too large.

    An application that calls DH_check() and supplies a key or parameters obtainedfrom 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()     andEVP_PKEY_param_check().

    Also vulnerable are the OpenSSL dhparam 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 not affected by this issue. (CVE-2023-3446)

    Issue summary: Generating excessively long X9.42 DH keys or checkingexcessively long X9.42 DH keys or     parameters may be very slow.

    Impact summary: Applications that use the functions DH_generate_key() togenerate an X9.42 DH key may     experience long delays.  Likewise, applicationsthat 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 froman 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 thereforevulnerable for excessively large P and Q parameters.

    Likewise, while DH_generate_key() performs a check for an excessively largeP, it doesn't check for an     excessively large Q.

    An application that calls DH_generate_key() or DH_check_pub_key() andsupplies a key or parameters obtained     from an untrusted source could bevulnerable to a Denial of Service attack.

    DH_generate_key() and DH_check_pub_key() are also called by a number ofother OpenSSL functions.  An     application calling any of those otherfunctions may similarly be affected.  The other functions affected     by thisare 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)

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

  - In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances     where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection     were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other     places in the script where the file names of certificates being hashed were possibly passed to a command     executed through the shell. This script is distributed by some operating systems in a manner where it is     automatically executed. On such operating systems, an attacker could execute arbitrary commands with the     privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the     OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in     OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze). (CVE-2022-2068)

  - The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat     Extension packets, which allows remote attackers to obtain sensitive information from process memory via     crafted packets that trigger a buffer over-read, as demonstrated by reading private keys, related to     d1_both.c and t1_lib.c, aka the Heartbleed bug. (CVE-2014-0160)

  - OpenSSL 0.9.7 before 0.9.7l and 0.9.8 before 0.9.8d allows remote attackers to cause a denial of service     (infinite loop and memory consumption) via malformed ASN.1 structures that trigger an improperly handled     error condition. (CVE-2006-2937)

  - OpenSSL 0.9.7 before 0.9.7l, 0.9.8 before 0.9.8d, and earlier versions allows attackers to cause a denial     of service (CPU consumption) via parasitic public keys with large (1) public exponent or (2) public     modulus values in X.509 certificates that require extra time to process when using RSA signature     verification. (CVE-2006-2940)

  - Buffer overflow in the SSL_get_shared_ciphers function in OpenSSL 0.9.7 before 0.9.7l, 0.9.8 before     0.9.8d, and earlier versions has unspecified impact and remote attack vectors involving a long list of     ciphers. (CVE-2006-3738)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
148986	Oracle MySQL Enterprise Monitor 多個弱點 (2021 年 4 月 CPU)	Nessus	CGI abuses	2021/4/26	2023/4/25	critical
148196	Amazon Linux 2：openssl11 (ALAS-2021-1622)	Nessus	Amazon Linux Local Security Checks	2021/3/27	2024/12/11	high
148281	CentOS 8：openssl (CESA-2021: 1024)	Nessus	CentOS Local Security Checks	2021/4/1	2024/1/5	high
148542	RHEL 8：Red Hat Virtualization (RHSA-2021: 1189)	Nessus	Red Hat Local Security Checks	2021/4/14	2024/11/7	high
192206	Amazon Linux 2：edk2，--advisory ALAS2-2024-2502 (ALAS-2024-2502)	Nessus	Amazon Linux Local Security Checks	2024/3/18	2025/9/26	high
148392	Tenable Nessus Agent < 8.2.4 Multiple Vulnerabilities (TNS-2021-08)	Nessus	Misc.	2021/4/8	2022/12/5	high
151906	Oracle MySQL Connectors (Jul 2021 CPU)	Nessus	Misc.	2021/7/21	2023/12/7	high
151899	FreeBSD : MySQL -- Multiple vulnerabilities (38a4a043-e937-11eb-9b84-d4c9ef517024)	Nessus	FreeBSD Local Security Checks	2021/7/21	2023/12/7	high
148355	Photon OS 4.0: Openssl PHSA-2021-4.0-0007	Nessus	PhotonOS Local Security Checks	2021/4/7	2025/8/22	high
148986	Oracle MySQL Enterprise Monitor Multiple Vulnerabilities (Apr 2021 CPU)	Nessus	CGI abuses	2021/4/26	2023/4/25	critical
148196	Amazon Linux 2 : openssl11 (ALAS-2021-1622)	Nessus	Amazon Linux Local Security Checks	2021/3/27	2024/12/11	high
148281	CentOS 8 : openssl (CESA-2021:1024)	Nessus	CentOS Local Security Checks	2021/4/1	2024/1/5	high
148534	FreeBSD : Node.js -- April 2021 Security Releases (c0c1834c-9761-11eb-acfd-0022489ad614)	Nessus	FreeBSD Local Security Checks	2021/4/14	2024/1/4	critical
148542	RHEL 8 : Red Hat Virtualization (RHSA-2021:1189)	Nessus	Red Hat Local Security Checks	2021/4/14	2024/11/7	high
236482	Alibaba Cloud Linux 3 : 0021: openssl (ALINUX3-SA-2021:0021)	Nessus	Alibaba Cloud Linux Local Security Checks	2025/5/14	2025/5/15	high
192206	Amazon Linux 2 : edk2, --advisory ALAS2-2024-2502 (ALAS-2024-2502)	Nessus	Amazon Linux Local Security Checks	2024/3/18	2025/9/26	high
266257	NewStart CGSL MAIN 6.06 : openssl Multiple Vulnerabilities (NS-SA-2025-0211)	Nessus	NewStart CGSL Local Security Checks	2025/9/30	2025/10/1	high

检测

插件搜索

critical

high

high

high

high

high

high

high

high

critical

high

high

critical

high

high

high

high