7.3 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
LOW
Integrity Impact
LOW
Availability Impact
LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
7.5 High
AI Score
Confidence
High
0.001 Low
EPSS
Percentile
37.0%
Updates are now available for the v18.x, v20.x and v21.x Node.js release lines for the following issues.
This security release includes the following dependency updates to address public vulnerabilities:
This security release includes an OpenSSL update to version 3.0.13+quic1 on all release lines to address advisories:
On Linux, Node.js ignores certain environment variables if those may have been set by an unprivileged user while the process is running with elevated privileges with the only exception of CAP_NET_BIND_SERVICE.
Due to a bug in the implementation of this exception, Node.js incorrectly applies this exception even when certain other capabilities have been set.
This allows unprivileged users to inject code that inherits the process’s elevated privileges.
Impacts:
Thank you, to Tobias Nießen for reporting this vulnerability and for fixing it.
A vulnerability in Node.js HTTP servers allows an attacker to send a specially crafted HTTP request with chunked encoding, leading to resource exhaustion and denial of service (DoS).
The server reads an unbounded number of bytes from a single connection, exploiting the lack of limitations on chunk extension bytes.
The issue can cause CPU and network bandwidth exhaustion, bypassing standard safeguards like timeouts and body size limits.
Impacts:
Thank you, to Bartek Nowotarski for reporting this vulnerability and thank you Paolo Insogna for fixing it.
The permission model protects itself against path traversal attacks by calling path.resolve() on any paths given by the user. If the path is to be treated as a Buffer, the implementation uses Buffer.from() to obtain a Buffer from the result of path.resolve().
By monkey-patching Buffer internals, namely, Buffer.prototype.utf8Write, the application can modify the result of path.resolve(), which leads to a path traversal vulnerability.
Impacts:
Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js. Thank you, to Tobias Nießen for reporting this vulnerability and for fixing it.
setuid() does not affect libuv’s internal io_uring operations if initialized before the call to setuid().
This allows the process to perform privileged operations despite presumably having dropped such privileges through a call to setuid().
Impacts:
Thank you, to valette for reporting this vulnerability and thank you Tobias Nießen for fixing it.
A vulnerability in the privateDecrypt() API of the crypto library, allowed a covert timing side-channel during PKCS#1 v1.5 padding error handling.
The vulnerability revealed significant timing differences in decryption for valid and invalid ciphertexts.
This poses a serious threat as attackers could remotely exploit the vulnerability to decrypt captured RSA ciphertexts or forge signatures, especially in scenarios involving API endpoints processing Json Web Encryption messages.
Impacts:
Thank you, to hkario for reporting this vulnerability and thank you Michael Dawson for fixing it.
Node.js depends on multiple built-in utility functions to normalize paths provided to node:fs functions, which can be overwitten with user-defined implementations leading to filesystem permission model bypass through path traversal attack.
Impacts:
Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.
Thank you, to xion for reporting this vulnerability and thank you Rafael Gonzaga for fixing it.
The Node.js Permission Model does not clarify in the documentation that wildcards should be only used as the last character of a file path.
For example: --allow-fs-read=/home/node/.ssh/*.pub
will ignore pub and give access to everything after .ssh/.
Impacts:
Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.
Thank you, to Tobias Nießen for reporting this vulnerability and thank you Rafael Gonzaga for fixing it.
Due to a long pipeline test on this security release, additional time was required. Therefore, the new target date is Wednesday 14th.
We have encounted an error in one of our patches, therefore, the release will take a bit longer than expected and the Node.js Security Releases should be available on, or shortly after, Tuesday, February 13th, 2024.
Preparing the releases is taking us a bit longer than originally expected and the Node.js Security Releases will be available on, or shortly after, Thursday, February 8th, 2024.
The Node.js project will release new versions of the 18.x, 20.x and, 21.x releases lines on or shortly after, Tuesday February 6 2024 in order to address:
The 21.x release line of Node.js is vulnerable to 4 high severity issues, 4 medium severity issues, and 1 low severity issue.
The 20.x release line of Node.js is vulnerable to 4 high severity issues, 4 medium severity issues, and 1 low severity issue.
In addition, the 18.x release line of Node.js is vulnerable to 2 high severity issues, 2 medium severity issues, and 1 low severity issue.
Releases will be available on, or shortly after, Tuesday February 6 2024.
7.3 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
LOW
Integrity Impact
LOW
Availability Impact
LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
7.5 High
AI Score
Confidence
High
0.001 Low
EPSS
Percentile
37.0%