The remote Ubuntu 22.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-5710-1 advisory.

    It was discovered that OpenSSL incorrectly handled certain X.509 Email Addresses. If a certificate     authority were tricked into signing a specially-crafted certificate, a remote attacker could possibly use     this issue to cause OpenSSL to crash, resulting in a denial of service. The default compiler options for     affected releases reduce the vulnerability to a denial of service. (CVE-2022-3602, CVE-2022-3786)

    It was discovered that OpenSSL incorrectly handled applications creating custom ciphers via the legacy     EVP_CIPHER_meth_new() function. This issue could cause certain applications that mishandled values to the     function to possibly end up with a NULL cipher and messages in plaintext. (CVE-2022-3358)

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

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

The remote Oracle Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2022-7288 advisory.

    - CVE-2022-3602: X.509 Email Address Buffer Overflow - running tests       Resolves: CVE-2022-3602

Tenable has extracted the preceding description block directly from the Oracle 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 Fedora 37 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2022-0f1d2e0537 advisory.

    Security fix for CVE-2022-3602 and CVE-2022-3786


Tenable has extracted the preceding description block directly from the Fedora 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 ALAS2023-2023-084 advisory.

    An HTTP Request Smuggling (HRS) vulnerability was found in the llhttp library, used by Node.JS. Spaces as     part of the header names were accepted as valid. In situations where HTTP conversations are being proxied     (such as proxy, reverse-proxy, load-balancer), an attacker can use this flaw to inject arbitrary messages     through the proxy. The highest threat from this vulnerability is to confidentiality and integrity.
    (CVE-2021-22959)

    An HTTP Request Smuggling (HRS) vulnerability was found in the llhttp library, used by Node.JS. During the     parsing of chunked messages, the chunk size parameter was not validated properly. In situations where HTTP     conversations are being proxied (such as proxy, reverse-proxy, load-balancer), an attacker can use this     flaw to inject arbitrary messages through the proxy. The highest threat from this vulnerability is to     confidentiality and integrity. (CVE-2021-22960)

    A flaw was found in npm. The npm ci command proceeds with an installation even if dependency information     in package-lock.json differs from package.json. This behavior is inconsistent with the documentation and     makes it easier for attackers to install malware that was supposed to have been blocked by an exact     version match requirement in package-lock.json. (CVE-2021-43616)

    A flaw was found in node.js where it accepted a certificate's Subject Alternative Names (SAN) entry, as     opposed to what is specified by the HTTPS protocol. This flaw allows an active person-in-the-middle to     forge a certificate and impersonate a trusted host. (CVE-2021-44531)

    It was found that node.js did not safely read the x509 certificate generalName format properly, resulting     in data injection. A certificate could use a specially crafted extension in order to be successfully     validated, permitting an attacker to impersonate a trusted host. (CVE-2021-44532)

    A flaw was found in node.js, where it did not properly handle multi-value Relative Distinguished Names.
    This flaw allows a specially crafted x509 certificate to produce a false multi-value Relative     Distinguished Name and to inject arbitrary data in node.js libraries. (CVE-2021-44533)

    Prototype pollution via console.table properties (CVE-2022-21824)

    A OS Command Injection vulnerability exists in Node.js versions <14.20.0, <16.16.0, <18.5.0 due to an     insufficient IsAllowedHost check that can easily be bypassed because IsIPAddress does not properly check     if an IP address is invalid before making DBS requests allowing rebinding attacks. (CVE-2022-32212)

    The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly parse     and validate Transfer-Encoding headers and can lead to HTTP Request Smuggling (HRS). (CVE-2022-32213)

    The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not strictly use     the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).
    (CVE-2022-32214)

    The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly     handle multi-line Transfer-Encoding headers. This can lead to HTTP Request Smuggling (HRS).
    (CVE-2022-32215)

    A cryptographic vulnerability exists on Node.js on linux in versions of 18.x prior to 18.40.0 which     allowed a default path for openssl.cnf that might be accessible under some circumstances to a non-admin     user instead of /etc/ssl as was the case in versions prior to the upgrade to OpenSSL 3. (CVE-2022-32222)

    Node.js is vulnerable to Hijack Execution Flow: DLL Hijacking under certain conditions on Windows     platforms.This vulnerability can be exploited if the victim has the following dependencies on a Windows     machine:* OpenSSL has been installed and C:\Program Files\Common Files\SSL\openssl.cnf exists.Whenever     the above conditions are present, `node.exe` will search for `providers.dll` in the current user     directory.After that, `node.exe` will try to search for `providers.dll` by the DLL Search Order in     Windows.It is possible for an attacker to place the malicious file `providers.dll` under a variety of     paths and exploit this vulnerability. (CVE-2022-32223)

    A vulnerability was found in NodeJS due to weak randomness in the WebCrypto keygen within the     SecretKeyGenTraits::DoKeyGen() in src/crypto/crypto_keygen.cc. Node.js made calls to EntropySource() in     SecretKeyGenTraits::DoKeyGen(). However, it does not check the return value and assumes the     EntropySource() always succeeds, but it can and sometimes will fail. This flaw allows a remote attacker to     decrypt sensitive information. (CVE-2022-35255)

    HTTP Request Smuggling Due to Incorrect Parsing of Header Fields (CVE-2022-35256)

    A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occursafter certificate chain signature verification and requires either a CA to     have signed the malicious certificate or for the application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to     overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash     (causing a denial of service) or potentially remote code execution.. (CVE-2022-3602)

    A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occurs after certificate chain signature verification and requires either a CA to     have signed a malicious certificate or for an application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a     certificate to overflow an arbitrary number of bytes containing the . character (decimal 46) on the stack.
    This buffer overflow could result in a crash (causing a denial of service). (CVE-2022-3786)

    A flaw was found in NodeJS. The issue occurs in the Node.js rebinding protector for --inspect that still     allows invalid IP addresses, specifically, the octal format. This flaw allows an attacker to perform DNS     rebinding and execute arbitrary code. (CVE-2022-43548)

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 version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the 0844671c-5a09-11ed-856e-d4c9ef517024 advisory.

  - A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occurs after certificate chain signature verification and requires either a CA to     have signed the malicious certificate or for the application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to     overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash     (causing a denial of service) or potentially remote code execution. Many platforms implement stack     overflow protections which would mitigate against the risk of remote code execution. The risk may be     further mitigated based on stack layout for any given platform/compiler. Pre-announcements of     CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors     described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new     version as soon as possible. In a TLS client, this can be triggered by connecting to a malicious server.
    In a TLS server, this can be triggered if the server requests client authentication and a malicious client     connects. Fixed in OpenSSL 3.0.7 (Affected 3.0.0,3.0.1,3.0.2,3.0.3,3.0.4,3.0.5,3.0.6). (CVE-2022-3602)

  - A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occurs after certificate chain signature verification and requires either a CA to     have signed a malicious certificate or for an application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a     certificate to overflow an arbitrary number of bytes containing the `.' character (decimal 46) on the     stack. This buffer overflow could result in a crash (causing a denial of service). In a TLS client, this     can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server     requests client authentication and a malicious client connects. Fixed in OpenSSL 3.0.7 (Affected     3.0.0,3.0.1,3.0.2,3.0.3,3.0.4,3.0.5,3.0.6). (CVE-2022-3786)

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 Junos OS installed on the remote host is affected by multiple vulnerabilities as referenced in the JSA69999 advisory.

  - A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occurs after certificate chain signature verification and requires either a CA to     have signed a malicious certificate or for an application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a     certificate to overflow an arbitrary number of bytes containing the `.' character (decimal 46) on the     stack. This buffer overflow could result in a crash (causing a denial of service). In a TLS client, this     can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server     requests client authentication and a malicious client connects. (CVE-2022-3786)

  - A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occurs after certificate chain signature verification and requires either a CA to     have signed the malicious certificate or for the application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to     overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash     (causing a denial of service) or potentially remote code execution. Many platforms implement stack     overflow protections which would mitigate against the risk of remote code execution. The risk may be     further mitigated based on stack layout for any given platform/compiler. Pre-announcements of     CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors     described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new     version as soon as possible. In a TLS client, this can be triggered by connecting to a malicious server.
    In a TLS server, this can be triggered if the server requests client authentication and a malicious client     connects. (CVE-2022-3602)

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

An update of the openssl package has been released.

The remote host is affected by the vulnerability described in GLSA-202211-01 (OpenSSL: Multiple Vulnerabilities)

  - A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occurs after certificate chain signature verification and requires either a CA to     have signed the malicious certificate or for the application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to     overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash     (causing a denial of service) or potentially remote code execution. Many platforms implement stack     overflow protections which would mitigate against the risk of remote code execution. The risk may be     further mitigated based on stack layout for any given platform/compiler. Pre-announcements of     CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors     described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new     version as soon as possible. In a TLS client, this can be triggered by connecting to a malicious server.
    In a TLS server, this can be triggered if the server requests client authentication and a malicious client     connects. Fixed in OpenSSL 3.0.7 (Affected 3.0.0,3.0.1,3.0.2,3.0.3,3.0.4,3.0.5,3.0.6). (CVE-2022-3602)

  - A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occurs after certificate chain signature verification and requires either a CA to     have signed a malicious certificate or for an application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a     certificate to overflow an arbitrary number of bytes containing the `.' character (decimal 46) on the     stack. This buffer overflow could result in a crash (causing a denial of service). In a TLS client, this     can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server     requests client authentication and a malicious client connects. Fixed in OpenSSL 3.0.7 (Affected     3.0.0,3.0.1,3.0.2,3.0.3,3.0.4,3.0.5,3.0.6). (CVE-2022-3786)

Note that Nessus has not tested for these issues 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 multiple vulnerabilities as referenced in the ALSA-2022:7288 advisory.

  - A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occurs after certificate chain signature verification and requires either a CA to     have signed the malicious certificate or for the application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to     overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash     (causing a denial of service) or potentially remote code execution. Many platforms implement stack     overflow protections which would mitigate against the risk of remote code execution. The risk may be     further mitigated based on stack layout for any given platform/compiler. Pre-announcements of     CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors     described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new     version as soon as possible. In a TLS client, this can be triggered by connecting to a malicious server.
    In a TLS server, this can be triggered if the server requests client authentication and a malicious client     connects. Fixed in OpenSSL 3.0.7 (Affected 3.0.0,3.0.1,3.0.2,3.0.3,3.0.4,3.0.5,3.0.6). (CVE-2022-3602)

  - A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occurs after certificate chain signature verification and requires either a CA to     have signed a malicious certificate or for an application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a     certificate to overflow an arbitrary number of bytes containing the `.' character (decimal 46) on the     stack. This buffer overflow could result in a crash (causing a denial of service). In a TLS client, this     can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server     requests client authentication and a malicious client connects. Fixed in OpenSSL 3.0.7 (Affected     3.0.0,3.0.1,3.0.2,3.0.3,3.0.4,3.0.5,3.0.6). (CVE-2022-3786)

Note that Nessus has not tested for these issues 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 multiple vulnerabilities as referenced in the ELSA-2022-10004 advisory.

    - CVE-2022-3602: X.509 Email Address Buffer Overflow - running tests       Resolves: CVE-2022-3602

Tenable has extracted the preceding description block directly from the Oracle 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 SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:4586-1 advisory.

    - CVE-2022-3996: Fixed X.509 Policy Constraints Double Locking (bsc#1206374)

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.

An update of the nodejs package has been released.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2023-051 advisory.

    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)

    The function `OCSP_basic_verify` verifies the signer certificate on an OCSP response. In the case where     the (non-default) flag OCSP_NOCHECKS is used then the response will be positive (meaning a successful     verification) even in the case where the response signing certificate fails to verify. It is anticipated     that most users of `OCSP_basic_verify` will not use the OCSP_NOCHECKS flag. In this case the     `OCSP_basic_verify` function will return a negative value (indicating a fatal error) in the case of a     certificate verification failure. The normal expected return value in this case would be 0. This issue     also impacts the command line OpenSSL ocsp application. When verifying an ocsp response with the
    -no_cert_checks option the command line application will report that the verification is successful even     though it has in fact failed. In this case the incorrect successful response will also be accompanied by     error messages showing the failure and contradicting the apparently successful result. Fixed in OpenSSL     3.0.3 (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1343)

    The OpenSSL 3.0 implementation of the RC4-MD5 ciphersuite incorrectly uses the AAD data as the MAC key.
    This makes the MAC key trivially predictable. An attacker could exploit this issue by performing a man-in-     the-middle attack to modify data being sent from one endpoint to an OpenSSL 3.0 recipient such that the     modified data would still pass the MAC integrity check. Note that data sent from an OpenSSL 3.0 endpoint     to a non-OpenSSL 3.0 endpoint will always be rejected by the recipient and the connection will fail at     that point. Many application protocols require data to be sent from the client to the server first.
    Therefore, in such a case, only an OpenSSL 3.0 server would be impacted when talking to a non-OpenSSL 3.0     client. If both endpoints are OpenSSL 3.0 then the attacker could modify data being sent in both     directions. In this case both clients and servers could be affected, regardless of the application     protocol. Note that in the absence of an attacker this bug means that an OpenSSL 3.0 endpoint     communicating with a non-OpenSSL 3.0 endpoint will fail to complete the handshake when using this     ciphersuite. The confidentiality of data is not impacted by this issue, i.e. an attacker cannot decrypt     data that has been encrypted using this ciphersuite - they can only modify it. In order for this attack to     work both endpoints must legitimately negotiate the RC4-MD5 ciphersuite. This ciphersuite is not compiled     by default in OpenSSL 3.0, and is not available within the default provider or the default ciphersuite     list. This ciphersuite will never be used if TLSv1.3 has been negotiated. In order for an OpenSSL 3.0     endpoint to use this ciphersuite the following must have occurred: 1) OpenSSL must have been compiled with     the (non-default) compile time option enable-weak-ssl-ciphers 2) OpenSSL must have had the legacy provider     explicitly loaded (either through application code or via configuration) 3) The ciphersuite must have been     explicitly added to the ciphersuite list 4) The libssl security level must have been set to 0 (default is     1) 5) A version of SSL/TLS below TLSv1.3 must have been negotiated 6) Both endpoints must negotiate the     RC4-MD5 ciphersuite in preference to any others that both endpoints have in common Fixed in OpenSSL 3.0.3     (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1434)

    The OPENSSL_LH_flush() function, which empties a hash table, contains a bug that breaks reuse of the     memory occuppied by the removed hash table entries. This function is used when decoding certificates or     keys. If a long lived process periodically decodes certificates or keys its memory usage will expand     without bounds and the process might be terminated by the operating system causing a denial of service.
    Also traversing the empty hash table entries will take increasingly more time. Typically such long lived     processes might be TLS clients or TLS servers configured to accept client certificate authentication. The     function was added in the OpenSSL 3.0 version thus older releases are not affected by the issue. Fixed in     OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1473)

    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 optimized 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. (CVE-2022-2097)

    A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occursafter certificate chain signature verification and requires either a CA to     have signed the malicious certificate or for the application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to     overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash     (causing a denial of service) or potentially remote code execution.. (CVE-2022-3602)

    A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint     checking. Note that this occurs after certificate chain signature verification and requires either a CA to     have signed a malicious certificate or for an application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a     certificate to overflow an arbitrary number of bytes containing the . character (decimal 46) on the stack.
    This buffer overflow could result in a crash (causing a denial of service). (CVE-2022-3786)

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.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
166798	Ubuntu 22.04 LTS : OpenSSL vulnerabilities (USN-5710-1)	Nessus	Ubuntu Local Security Checks	2022/11/2	2024/8/27	high
166801	Oracle Linux 9 : openssl (ELSA-2022-7288)	Nessus	Oracle Linux Local Security Checks	2022/11/2	2024/11/1	high
211127	Fedora 37 : openssl (2022-0f1d2e0537)	Nessus	Fedora Local Security Checks	2024/11/14	2024/11/15	high
173113	Amazon Linux 2023 : nodejs, nodejs-devel, nodejs-full-i18n (ALAS2023-2023-084)	Nessus	Amazon Linux Local Security Checks	2023/3/21	2024/12/11	critical
166787	FreeBSD : OpenSSL -- Buffer overflows in Email verification (0844671c-5a09-11ed-856e-d4c9ef517024)	Nessus	FreeBSD Local Security Checks	2022/11/2	2022/12/15	high
173835	Juniper Junos OS Multiple Vulnerabilities (JSA69999)	Nessus	Junos Local Security Checks	2023/4/4	2023/4/5	high
203215	Photon OS 4.0: Openssl PHSA-2022-4.0-0272	Nessus	PhotonOS Local Security Checks	2024/7/23	2024/7/24	high
166788	GLSA-202211-01 : OpenSSL: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	2022/11/2	2023/10/6	high
166808	AlmaLinux 9 : openssl (ALSA-2022:7288)	Nessus	Alma Linux Local Security Checks	2022/11/2	2022/12/15	high
167841	Oracle Linux 9 : openssl (ELSA-2022-10004)	Nessus	Oracle Linux Local Security Checks	2022/11/18	2026/2/9	high
168955	SUSE SLED15: libopenssl-3-devel / libopenssl-3-devel-32bit / libopenssl3 / etc (SUSE-SU-2022:4586-1)	Nessus	SuSE Local Security Checks	2022/12/21	2026/6/26	high
236956	Photon OS 4.0: Nodejs PHSA-2025-4.0-0801	Nessus	PhotonOS Local Security Checks	2025/5/20	2025/5/20	critical
173139	Amazon Linux 2023 : openssl, openssl-devel, openssl-libs (ALAS2023-2023-051)	Nessus	Amazon Linux Local Security Checks	2023/3/21	2025/9/4	high
195166	GLSA-202405-29 : Node.js: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	2024/5/8	2024/5/8	critical
332189	Photon OS 5.0: Nodejs PHSA-2023-5.0-91-0011	Nessus	PhotonOS Local Security Checks	2026/8/5	2026/8/5	high

检测

插件搜索

high

high

high

critical

high

high

high

high

high

high

high

critical

high

critical

high