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.

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 Node.js installed on the remote host is prior to 14.20.0, 16.16.0, 18.5.0. It is, therefore, affected by multiple vulnerabilities as referenced in the July 7th 2022 Security Releases advisory.

  - The llhttp parser in the http module does not correctly parse and validate Transfer-Encoding headers. This     can lead to HTTP Request Smuggling (HRS). More details will be available at CVE-2022-32213 after     publication. Thank you to Zeyu Zhang (@zeyu2001) for reporting this vulnerability. Impacts:
    (CVE-2022-32213)

  - The llhttp parser in the http module does not strictly use the CRLF sequence to delimit HTTP requests.
    This can lead to HTTP Request Smuggling (HRS). More details will be available at CVE-2022-32214 after     publication. Thank you to Zeyu Zhang (@zeyu2001) for reporting this vulnerability. Impacts:
    (CVE-2022-32214)

  - The llhttp parser in the http module does not correctly handle multi-line Transfer-Encoding headers. This     can lead to HTTP Request Smuggling (HRS). More details will be available at CVE-2022-32215 after     publication. Thank you to Zeyu Zhang (@zeyu2001) for reporting this vulnerability. Impacts:
    (CVE-2022-32215)

  - The IsAllowedHost check can easily be bypassed because IsIPAddress does not properly check if an IP     address is invalid or not. When an invalid IPv4 address is provided (for instance 10.0.2.555 is provided),     browsers (such as Firefox) will make DNS requests to the DNS server, providing a vector for an attacker-     controlled DNS server or a MITM who can spoof DNS responses to perform a rebinding attack and hence     connect to the WebSocket debugger, allowing for arbitrary code execution. This is a bypass of     CVE-2021-22884. More details will be available at CVE-2022-32212 after publication. Thank you to Axel     Chong for reporting this vulnerability. Impacts: (CVE-2022-32212)

  - This vulnerability can be exploited if the victim has the following dependencies on Windows machine:
    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. More details will be available at CVE-2022-32223 after publication. Thank you     to Yakir Kadkoda from Aqua Security for reporting this vulnerability. Impacts: Note: Node.js can use an     OpenSSL configuration file by specifying the environment variable OPENSSL_CONF, or using the command line     option --openssl-conf, and if none of those are specified will default to reading the default OpenSSL     configuration file openssl.cnf. Node.js will only read a section that is by default named nodejs_conf. If     your installation was using the default openssl.cnf file and is affected by this breaking change you can     fall back to the previous behavior by: (CVE-2022-32223)

  - When Node.js starts on linux based systems, it attempts to read     /home/iojs/build/ws/out/Release/obj.target/deps/openssl/openssl.cnf, which ordinarily doesn't exist. On     some shared systems an attacker may be able create this file and therefore affect the default OpenSSL     configuration for other users. Thank you to Michael Scovetta from the OpenSSF Alpha-Omega project for     reporting this vulnerability. Impacts: (CVE-2022-32222)

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

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 Node.js installed on the remote host is prior to 14.20.1, 16.17.1, 18.9.1. It is, therefore, affected by multiple vulnerabilities as referenced in the September 23rd 2022 Security Releases advisory.

  - The fix for CVE-2022-32212, covered the cases for routable IP addresses, however, there exists a specific     behavior on macOS devices when handling the http://0.0.0.0 URL that allows an attacker-controlled DNS     server to bypass the DNS rebinding protection by resolving hosts in the .local domain. An attacker-     controlled DNS server can, resolve <Computer Name>.local to any arbitrary IP address, and consequently     cause the victim's browser to load arbitrary content at http://0.0.0.0. This allows the attacker to bypass     the DNS rebinding protection. Thank you, to Zeyu Zhang (@zeyu2001) for reporting this vulnerability and     thank you Rafael Gonzaga for fixing it. Impacts: (CVE-2022-32212)

  - Due to an incomplete fix for CVE-2022-32215, the llhttp parser in the http module in Node.js v16.16.0 and     18.7.0 still does not correctly handle multi-line Transfer-Encoding headers. This can lead to HTTP Request     Smuggling (HRS). Thank you, Liav Gutman of the JFrog CSO Team for reporting this vulnerability and thank     you Paolo Insogna for fixing it. Impacts: (CVE-2022-32215)

  - The fix for CVE-2022-32213 can be bypassed using an obs-fold, which the Node.js HTTP parser supports. If     the Node.js HTTP module is used as a proxy, then it incorrectly parses the transfer-encoding header as     indicative of chunked request, while folding the headers and hence forwarding Transfer-Encoding: chunked     abc which is not a valid transfer-encoding header to the downstream server. As such this can lead to HTTP     request smuggling as indicated by CVE-2022-32213. Thank you, Haxatron for reporting this vulnerability.
    Impacts: (CVE-2022-32213)

  - The llhttp parser in the http module in Node.js v18.7.0 does not correctly handle header fields that are     not terminated with CLRF. This may result in HTTP Request Smuggling. Thank you, VVX7 for reporting this     vulnerability. Impacts: (CVE-2022-35256)

  - In Node.js 18 and later, at startup, the process attempts to read     /home/iojs/build/ws/out/Release/obj.target/deps/openssl/openssl.cnf on MacOS which ordinarily doesn't     exist. The attack would be an attacker with access to a shared MacOS host with a self-chosen username     (iojs) being able to affect the OpenSSF configuration of other users. Thank you, Michael Dawson for     reporting (and fixing!) this vulnerability. Impacts: (CVE-2022-32222)

  - Node.js made calls to EntropySource() in SecretKeyGenTraits::DoKeyGen() in src/crypto/crypto_keygen.cc.
    However, it does not check the return value, it assumes EntropySource() always succeeds, but it can (and     sometimes will) fail. Thank you, Ben Noordhuis for reporting (and fixing!) this vulnerability. Impacts:
    (CVE-2022-35255)

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 b9210706-feb0-11ec-81fa-1c697a616631 advisory.

  - 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 OS Command Injection vulnerability exists in Node.js versions <14.20.0, <16.20.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)

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

ID	Name	Product	Family	Severity
195166	GLSA-202405-29 : Node.js: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	critical
173113	Amazon Linux 2023 : nodejs, nodejs-devel, nodejs-full-i18n (ALAS2023-2023-084)	Nessus	Amazon Linux Local Security Checks	critical
165634	Node.js 14.x < 14.20.0 / 16.x < 16.16.0 / 18.x < 18.5.0 Multiple Vulnerabilities (July 7th 2022 Security Releases).	Nessus	Misc.	high
165633	Node.js 14.x < 14.20.1 / 16.x < 16.17.1 / 18.x < 18.9.1 Multiple Vulnerabilities (September 23rd 2022 Security Releases).	Nessus	Misc.	critical
162898	FreeBSD : Node.js -- July 7th 2022 Security Releases (b9210706-feb0-11ec-81fa-1c697a616631)	Nessus	FreeBSD Local Security Checks	high

Detections

Analytics

CVE-2022-32222

medium

Tenable Plugins

critical

critical

high

critical

high