A vulnerability has been identified in Node.js version 20, affecting users of the experimental permission model when the --allow-fs-read flag is used with a non-* argument. This flaw arises from an inadequate permission model that fails to restrict file watching through the fs.watchFile API. As a result, malicious actors can monitor files that they do not have explicit read access to. Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.

The version of Siemens SINEC NMS installed on the remote host is prior to 2.0.1.0. It is, therefore, affected by multiple vulnerabilities as referenced in the SSA-943925 advisory.

  - coreruleset (aka OWASP ModSecurity Core Rule Set) through 3.3.4 does not detect multiple Content-Type     request headers on some platforms. This might allow attackers to bypass a WAF with a crafted payload,     aka Content-Type confusion between the WAF and the backend application. This occurs when the web     application relies on only the last Content-Type header. Other platforms may reject the additional     Content-Type header or merge conflicting headers, leading to detection as a malformed header.
    (CVE-2023-38199)

  - Some mod_proxy configurations on Apache HTTP Server versions 2.4.0 through 2.4.55 allow a HTTP Request     Smuggling attack. Configurations are affected when mod_proxy is enabled along with some form of     RewriteRule or ProxyPassMatch in which a non-specific pattern matches some portion of the user-supplied     request-target (URL) data and is then re-inserted into the proxied request-target using variable     substitution. For example, something like: RewriteEngine on RewriteRule ^/here/(.*)     http://example.com:8080/elsewhere?$1; [P] ProxyPassReverse /here/ http://example.com:8080/ Request     splitting/smuggling could result in bypass of access controls in the proxy server, proxying unintended     URLs to existing origin servers, and cache poisoning. Users are recommended to update to at least version     2.4.56 of Apache HTTP Server. (CVE-2023-25690)

  - The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json     definition for a given module. This vulnerability affects all users using the experimental policy     mechanism in all active release lines: 16.x, 18.x and, 20.x. Please note that at the time this CVE was     issued, the policy is an experimental feature of Node.js. (CVE-2023-32002)

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 16.20.1, 18.16.1, 20.3.1. It is, therefore, affected by multiple vulnerabilities as referenced in the Tuesday June 20 2023 Security Releases advisory.

  - The use of proto in process.mainModule.proto.require() can bypass the policy mechanism and require modules     outside of the policy.json definition. This vulnerability affects all users using the experimental policy     mechanism in all active release lines: 16.x, 18.x and, 20.x. Please note that at the time this CVE was     issued, the policy is an experimental feature of Node.js. Thank you, to Axel Chong for reporting this     vulnerability and thank you Rafael Gonzaga for fixing it. (CVE-2023-30581)

  - A vulnerability has been discovered in Node.js version 20, specifically within the experimental permission     model. This flaw relates to improper handling of path traversal bypass when verifying file permissions.
    This vulnerability affects all users using the experimental permission model in Node.js 20. Please note     that at the time this CVE was issued, the permission model is an experimental feature of Node.js. Thank     you, to Axel Chong for reporting this vulnerability and thank you Rafael Gonzaga for fixing it.
    (CVE-2023-30584)

  - A vulnerability in Node.js version 20 allows for bypassing restrictions set by the --experimental-     permission flag using the built-in inspector module (node:inspector). By exploiting the Worker class's     ability to create an internal worker with the kIsInternal Symbol, attackers can modify the isInternal     value when an inspector is attached within the Worker constructor before initializing a new WorkerImpl.
    This vulnerability exclusively affects Node.js users employing the permission model mechanism in Node.js     20. Please note that at the time this CVE was issued, the permission model is an experimental feature of     Node.js. Thank you, to mattaustin for reporting this vulnerability and thank you Rafael Gonzaga for fixing     it. (CVE-2023-30587)

  - A vulnerability has been identified in Node.js version 20, affecting users of the experimental permission     model when the --allow-fs-read flag is used with a non-* argument. This flaw arises from an inadequate     permission model that fails to restrict file watching through the fs.watchFile API. As a result, malicious     actors can monitor files that they do not have explicit read access to. This vulnerability affects all     users using the experimental permission model in Node.js 20. Please note that at the time this CVE was     issued, the permission model is an experimental feature of Node.js. Thanks to Colin Ihrig for reporting     this vulnerability and to Rafael Gonzaga for fixing it. (CVE-2023-30582)

  - fs.openAsBlob() can bypass the experimental permission model when using the file system read restriction     with the --allow-fs-read flag in Node.js 20. This flaw arises from a missing check in the fs.openAsBlob()     API. This vulnerability affects all users using the experimental permission model in Node.js 20. Thanks to     Colin Ihrig for reporting this vulnerability and to Rafael Gonzaga for fixing it. Please note that at the     time this CVE was issued, the permission model is an experimental feature of Node.js. (CVE-2023-30583)

  - A vulnerability has been identified in the Node.js (.msi version) installation process, specifically     affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during     the repair operation, where the msiexec.exe process, running under the NT AUTHORITY\SYSTEM context,     attempts to read the %USERPROFILE% environment variable from the current user's registry. The issue arises     when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the     msiexec.exe process attempts to create the specified path in an unsafe manner, potentially leading to     the creation of arbitrary folders in arbitrary locations. The severity of this vulnerability is heightened     by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by     standard (or non-privileged) users. Consequently, unprivileged actors, including malicious entities or     trojans, can manipulate the environment variable key to deceive the privileged msiexec.exe process. This     manipulation can result in the creation of folders in unintended and potentially malicious locations. It     is important to note that this vulnerability is specific to Windows users who install Node.js using the     .msi installer. Users who opt for other installation methods are not affected by this particular issue.
    This affects all active Node.js versions: v16, v18, and, v20. Thank you, to @sim0nsecurity for reporting     this vulnerability and thank you Tobias Nieen for fixing it. (CVE-2023-30585)

  - Node.js 20 allows loading arbitrary OpenSSL engines when the experimental permission model is enabled,     which can bypass and/or disable the permission model. The crypto.setEngine() API can be used to bypass the     permission model when called with a compatible OpenSSL engine. The OpenSSL engine can, for example,     disable the permission model in the host process by manipulating the process's stack memory to locate the     permission model Permission::enabled_ in the host process's heap memory. This vulnerability affects all     users using the experimental permission model in Node.js 20. Please note that at the time this CVE was     issued, the permission model is an experimental feature of Node.js. Thanks to Tobias Nieen for reporting     this vulnerability and fixing it. (CVE-2023-30586)

  - When an invalid public key is used to create an x509 certificate using the crypto.X509Certificate() API a     non-expect termination occurs making it susceptible to DoS attacks when the attacker could force     interruptions of application processing, as the process terminates when accessing public key info of     provided certificates from user code. The current context of the users will be gone, and that will cause a     DoS scenario. This vulnerability affects all active Node.js versions v16, v18, and, v20. Thank you, to     Marc Schnefeld for reporting this vulnerability and thank you Tobias Nieen for fixing it.
    (CVE-2023-30588)

  - The llhttp parser 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). The CR character (without LF) is sufficient to     delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence     should delimit each header-field. This vulnerability impacts all Node.js active versions: v16, v18, and,     v20. Thank you, to Yadhu Krishna M(Team bi0s & CRED Security team) for reporting this vulnerability and     thank you Paolo Insogna for fixing it. (CVE-2023-30589)

  - The generateKeys() API function returned from crypto.createDiffieHellman() only generates missing (or     outdated) keys, that is, it only generates a private key if none has been set yet. However, the     documentation says this API call: Generates private and public Diffie-Hellman key values. The documented     behavior is different from the actual behavior, and this difference could easily lead to security issues     in applications that use these APIs as the DiffieHellman may be used as the basis for application-level     security. Please note that this is a documentation change an the vulnerability has been classified under     CWE-1068 - Inconsistency Between Implementation and Documented Design. This change applies to all Node.js     active versions: v16, v18, and, v20. Thanks to Ben Smyth for reporting this vulnerability and to Tobias     Nieen for fixing it. (CVE-2023-30590)

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
191429	Siemens SINEC NMS < V2.0 SP1 Multiple Vulnerabilities	Nessus	Windows	critical
177518	Node.js 16.x < 16.20.1 / 18.x < 18.16.1 / 20.x < 20.3.1 Multiple Vulnerabilities (Tuesday June 20 2023 Security Releases).	Nessus	Misc.	high

Detections

Analytics

CVE-2023-30582

medium

Tenable Plugins

critical

critical

high