Search for packages
| purl | pkg:deb/debian/nodejs@0.10.29~dfsg-1~bpo70%2B1 |
| Next non-vulnerable version | 20.19.2+dfsg-1 |
| Latest non-vulnerable version | 20.19.2+dfsg-1 |
| Risk | 10.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-1yyk-tacv-83he
Aliases: CVE-2022-32212 |
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. |
Affected by 13 other vulnerabilities. |
|
VCID-2a49-wha4-zyba
Aliases: CVE-2019-15605 |
HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed |
Affected by 31 other vulnerabilities. |
|
VCID-2kqd-yu19-nqh7
Aliases: CVE-2015-8027 |
nodejs: unspecified denial of service vulnerability |
Affected by 55 other vulnerabilities. |
|
VCID-2rfj-4mj2-dkbm
Aliases: CVE-2016-1669 |
Affected by 55 other vulnerabilities. |
|
|
VCID-2vqy-3hmp-yyfe
Aliases: CVE-2022-21824 |
Due to the formatting logic of the "console.table()" function it was not safe to allow user controlled input to be passed to the "properties" parameter while simultaneously passing a plain object with at least one property as the first parameter, which could be "__proto__". The prototype pollution has very limited control, in that it only allows an empty string to be assigned to numerical keys of the object prototype.Node.js >= 12.22.9, >= 14.18.3, >= 16.13.2, and >= 17.3.1 use a null protoype for the object these properties are being assigned to. |
Affected by 13 other vulnerabilities. |
|
VCID-392n-vptx-jycx
Aliases: CVE-2019-5737 |
In Node.js including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1, an attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep-alive mode and by sending headers very slowly. This keeps the connection and associated resources alive for a long period of time. Potential attacks are mitigated by the use of a load balancer or other proxy layer. This vulnerability is an extension of CVE-2018-12121, addressed in November and impacts all active Node.js release lines including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1. |
Affected by 31 other vulnerabilities. |
|
VCID-3fmh-tfy5-sfdy
Aliases: CVE-2020-8201 |
Node.js < 12.18.4 and < 14.11 can be exploited to perform HTTP desync attacks and deliver malicious payloads to unsuspecting users. The payloads can be crafted by an attacker to hijack user sessions, poison cookies, perform clickjacking, and a multitude of other attacks depending on the architecture of the underlying system. The attack was possible due to a bug in processing of carrier-return symbols in the HTTP header names. |
Affected by 13 other vulnerabilities. |
|
VCID-3nf4-ypt3-3bem
Aliases: CVE-2021-44531 |
Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.Versions of Node.js with the fix for this disable the URI SAN type when checking a certificate against a hostname. This behavior can be reverted through the --security-revert command-line option. |
Affected by 13 other vulnerabilities. |
|
VCID-47y2-q8ds-37an
Aliases: CVE-2015-6764 |
security update |
Affected by 55 other vulnerabilities. |
|
VCID-5f9x-2thd-73dg
Aliases: CVE-2022-32215 |
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). |
Affected by 13 other vulnerabilities. |
|
VCID-6wrp-gbh5-aybu
Aliases: CVE-2018-7160 GHSA-wq4c-wm6x-jw44 |
The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution. An attack is possible from malicious websites open in a web browser on the same computer, or another computer with network access to the computer running the Node.js process. A malicious website could use a DNS rebinding attack to trick the web browser to bypass same-origin-policy checks and to allow HTTP connections to localhost or to hosts on the local network. If a Node.js process with the debug port active is running on localhost or on a host on the local network, the malicious website could connect to it as a debugger, and get full code execution access. |
Affected by 31 other vulnerabilities. |
|
VCID-89uf-r4wj-7feq
Aliases: CVE-2020-8287 |
Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 allow two copies of a header field in an HTTP request (for example, two Transfer-Encoding header fields). In this case, Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling. |
Affected by 31 other vulnerabilities. Affected by 13 other vulnerabilities. |
|
VCID-8qyb-ne8j-g3bb
Aliases: CVE-2022-35255 |
A weak randomness in WebCrypto keygen vulnerability exists in Node.js 18 due to a change with EntropySource() in SecretKeyGenTraits::DoKeyGen() in src/crypto/crypto_keygen.cc. There are two problems with this: 1) It does not check the return value, it assumes EntropySource() always succeeds, but it can (and sometimes will) fail. 2) The random data returned byEntropySource() may not be cryptographically strong and therefore not suitable as keying material. |
Affected by 13 other vulnerabilities. |
|
VCID-8yeb-pdsh-jua3
Aliases: CVE-2018-12116 |
Node.js: All versions prior to Node.js 6.15.0 and 8.14.0: HTTP request splitting: If Node.js can be convinced to use unsanitized user-provided Unicode data for the `path` option of an HTTP request, then data can be provided which will trigger a second, unexpected, and user-defined HTTP request to made to the same server. |
Affected by 31 other vulnerabilities. |
|
VCID-9e63-4jfk-y3d9
Aliases: CVE-2016-5325 |
nodejs: reason argument in ServerResponse#writeHead() not properly validated |
Affected by 55 other vulnerabilities. |
|
VCID-9nfh-cgh8-ykam
Aliases: CVE-2019-9511 |
Excessive CPU usage in HTTP/2 with small window updates |
Affected by 31 other vulnerabilities. |
|
VCID-aymp-hts9-fyhe
Aliases: CVE-2021-22959 |
The parser in accepts requests with a space (SP) right after the header name before the colon. This can lead to HTTP Request Smuggling (HRS) in llhttp < v2.1.4 and < v6.0.6. |
Affected by 13 other vulnerabilities. |
|
VCID-bgkg-8bpp-hufv
Aliases: CVE-2019-15604 |
Improper Certificate Validation in Node.js 10, 12, and 13 causes the process to abort when sending a crafted X.509 certificate |
Affected by 31 other vulnerabilities. |
|
VCID-byj3-tu61-9bhy
Aliases: CVE-2021-22930 |
Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory corruption, to change process behavior. |
Affected by 13 other vulnerabilities. |
|
VCID-csbz-fj5g-j7f2
Aliases: CVE-2018-7159 |
The HTTP parser in all current versions of Node.js ignores spaces in the `Content-Length` header, allowing input such as `Content-Length: 1 2` to be interpreted as having a value of `12`. The HTTP specification does not allow for spaces in the `Content-Length` value and the Node.js HTTP parser has been brought into line on this particular difference. The security risk of this flaw to Node.js users is considered to be VERY LOW as it is difficult, and may be impossible, to craft an attack that makes use of this flaw in a way that could not already be achieved by supplying an incorrect value for `Content-Length`. Vulnerabilities may exist in user-code that make incorrect assumptions about the potential accuracy of this value compared to the actual length of the data supplied. Node.js users crafting lower-level HTTP utilities are advised to re-check the length of any input supplied after parsing is complete. |
Affected by 31 other vulnerabilities. |
|
VCID-d12s-13vn-p3f7
Aliases: CVE-2022-43548 |
A OS Command Injection vulnerability exists in Node.js versions <14.21.1, <16.18.1, <18.12.1, <19.0.1 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.The fix for this issue in https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32212 was incomplete and this new CVE is to complete the fix. |
Affected by 13 other vulnerabilities. |
|
VCID-de8e-u8sq-nyby
Aliases: CVE-2023-23920 |
An untrusted search path vulnerability exists in Node.js. <19.6.1, <18.14.1, <16.19.1, and <14.21.3 that could allow an attacker to search and potentially load ICU data when running with elevated privileges. |
Affected by 13 other vulnerabilities. |
|
VCID-evst-4u5k-mfek
Aliases: CVE-2018-7164 |
Node.js versions 9.7.0 and later and 10.x are vulnerable and the severity is MEDIUM. A bug introduced in 9.7.0 increases the memory consumed when reading from the network into JavaScript using the net.Socket object directly as a stream. An attacker could use this cause a denial of service by sending tiny chunks of data in short succession. This vulnerability was restored by reverting to the prior behaviour. |
Affected by 31 other vulnerabilities. |
|
VCID-fjaq-v9m9-bbgv
Aliases: CVE-2018-7161 |
All versions of Node.js 8.x, 9.x, and 10.x are vulnerable and the severity is HIGH. An attacker can cause a denial of service (DoS) by causing a node server providing an http2 server to crash. This can be accomplished by interacting with the http2 server in a manner that triggers a cleanup bug where objects are used in native code after they are no longer available. This has been addressed by updating the http2 implementation. |
Affected by 31 other vulnerabilities. |
|
VCID-ghcc-kqdm-nkem
Aliases: CVE-2022-35256 |
The llhttp parser in the http module in Node v18.7.0 does not correctly handle header fields that are not terminated with CLRF. This may result in HTTP Request Smuggling. |
Affected by 13 other vulnerabilities. |
|
VCID-gmk8-4jw3-gyam
Aliases: CVE-2014-5256 |
V8: Memory Corruption and Stack Overflow |
Affected by 55 other vulnerabilities. |
|
VCID-gnh8-babc-vqfr
Aliases: CVE-2023-30590 |
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, but the function is also needed to compute the corresponding public key after calling setPrivateKey(). However, the documentation says this API call: "Generates private and public Diffie-Hellman key values". The documented behavior is very 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, implications are consequently broad. |
Affected by 12 other vulnerabilities. |
|
VCID-htva-kyj3-zffg
Aliases: CVE-2014-9748 |
The uv_rwlock_t fallback implementation for Windows XP and Server 2003 in libuv before 1.7.4 does not properly prevent threads from releasing the locks of other threads, which allows attackers to cause a denial of service (deadlock) or possibly have unspecified other impact by leveraging a race condition. |
Affected by 55 other vulnerabilities. |
|
VCID-j4rg-hgxj-jufb
Aliases: CVE-2024-22019 |
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. |
Affected by 12 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-jd3c-ftbh-hffx
Aliases: CVE-2025-47153 |
Certain build processes for libuv and Node.js for 32-bit systems, such as for the nodejs binary package through nodejs_20.19.0+dfsg-2_i386.deb for Debian GNU/Linux, have an inconsistent off_t size (e.g., building on i386 Debian always uses _FILE_OFFSET_BITS=64 for the libuv dynamic library, but uses the _FILE_OFFSET_BITS global system default of 32 for nodejs), leading to out-of-bounds access. NOTE: this is not a problem in the Node.js software itself. In particular, the Node.js website's download page does not offer prebuilt Node.js for Linux on i386. |
Affected by 12 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-k39t-1zme-9kc9
Aliases: CVE-2020-11080 |
In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. The proof of concept attack involves a malicious client constructing a SETTINGS frame with a length of 14,400 bytes (2400 individual settings entries) over and over again. The attack causes the CPU to spike at 100%. nghttp2 v1.41.0 fixes this vulnerability. There is a workaround to this vulnerability. Implement nghttp2_on_frame_recv_callback callback, and if received frame is SETTINGS frame and the number of settings entries are large (e.g., > 32), then drop the connection. |
Affected by 31 other vulnerabilities. |
|
VCID-k9se-mw48-cucj
Aliases: CVE-2025-23085 |
A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions. This vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x. |
Affected by 12 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-kb5h-fym3-gbgt
Aliases: CVE-2018-12122 |
Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Slowloris HTTP Denial of Service: An attacker can cause a Denial of Service (DoS) by sending headers very slowly keeping HTTP or HTTPS connections and associated resources alive for a long period of time. |
Affected by 31 other vulnerabilities. |
|
VCID-mdgu-hnk7-57hu
Aliases: CVE-2023-46809 |
Node.js versions which bundle an unpatched version of OpenSSL or run against a dynamically linked version of OpenSSL which are unpatched are vulnerable to the Marvin Attack - https://people.redhat.com/~hkario/marvin/, if PCKS #1 v1.5 padding is allowed when performing RSA descryption using a private key. |
Affected by 12 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-n36r-n97v-fqe8
Aliases: CVE-2022-32214 GHSA-q5vx-44v4-gch4 |
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). |
Affected by 13 other vulnerabilities. |
|
VCID-njvw-kz8k-5qab
Aliases: CVE-2022-32213 GHSA-5689-v88g-g6rv |
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). |
Affected by 13 other vulnerabilities. |
|
VCID-p1tj-fm96-cbfh
Aliases: CVE-2019-5739 |
nodejs: DoS with keep-alive HTTP connection |
Affected by 31 other vulnerabilities. |
|
VCID-pbkh-mkz6-gubx
Aliases: CVE-2019-15606 |
Including trailing white space in HTTP header values in Nodejs 10, 12, and 13 causes bypass of authorization based on header value comparisons |
Affected by 31 other vulnerabilities. |
|
VCID-ps4g-2gfg-xbbd
Aliases: CVE-2017-11499 |
nodejs: Constant Hashtable Seeds vulnerability |
Affected by 31 other vulnerabilities. |
|
VCID-pvsg-a82t-77eu
Aliases: CVE-2020-8265 |
Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an error, this object is passed back to the caller as part of a StreamWriteResult structure. This may be exploited to corrupt memory leading to a Denial of Service or potentially other exploits. |
Affected by 31 other vulnerabilities. Affected by 13 other vulnerabilities. |
|
VCID-qfwe-wqg1-xydr
Aliases: CVE-2018-12115 |
In all versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0 when used with UCS-2 encoding (recognized by Node.js under the names `'ucs2'`, `'ucs-2'`, `'utf16le'` and `'utf-16le'`), `Buffer#write()` can be abused to write outside of the bounds of a single `Buffer`. Writes that start from the second-to-last position of a buffer cause a miscalculation of the maximum length of the input bytes to be written. |
Affected by 31 other vulnerabilities. |
|
VCID-r7kf-z7f5-3qd2
Aliases: CVE-2020-8174 |
napi_get_value_string_*() allows various kinds of memory corruption in node < 10.21.0, 12.18.0, and < 14.4.0. |
Affected by 31 other vulnerabilities. |
|
VCID-s6vn-d7fj-rqh1
Aliases: CVE-2016-2086 |
nodejs: Request smuggling vulnerability |
Affected by 55 other vulnerabilities. |
|
VCID-sn12-fkzk-bqdt
Aliases: CVE-2021-22939 |
If the Node.js https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to servers with an expired certificate would have been accepted. |
Affected by 13 other vulnerabilities. |
|
VCID-u2j6-hkd3-8kaj
Aliases: CVE-2015-7384 |
Uncontrolled Resource Consumption Node.js allows remote attackers to cause a denial of service. |
Affected by 55 other vulnerabilities. |
|
VCID-u3a7-xrve-3uhj
Aliases: CVE-2016-7099 |
Affected by 55 other vulnerabilities. |
|
|
VCID-u9mc-kjy8-quhc
Aliases: CVE-2016-2216 |
nodejs: Response splitting vulnerability using Unicode characters |
Affected by 55 other vulnerabilities. |
|
VCID-uypg-fgmq-37cu
Aliases: CVE-2021-22960 |
The parse function in llhttp < 2.1.4 and < 6.0.6. ignores chunk extensions when parsing the body of chunked requests. This leads to HTTP Request Smuggling (HRS) under certain conditions. |
Affected by 13 other vulnerabilities. |
|
VCID-v55u-2g1c-jyfe
Aliases: CVE-2023-32559 |
A privilege escalation vulnerability exists in the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. The use of the deprecated API `process.binding()` can bypass the policy mechanism by requiring internal modules and eventually take advantage of `process.binding('spawn_sync')` run arbitrary code, outside of the limits defined in a `policy.json` file. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js. |
Affected by 12 other vulnerabilities. |
|
VCID-v9pq-n6cq-8uef
Aliases: CVE-2021-22883 |
Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an 'unknownProtocol' are established. This leads to a leak of file descriptors. If a file descriptor limit is configured on the system, then the server is unable to accept new connections and prevent the process also from opening, e.g. a file. If no file descriptor limit is configured, then this lead to an excessive memory usage and cause the system to run out of memory. |
Affected by 31 other vulnerabilities. Affected by 13 other vulnerabilities. |
|
VCID-ve6j-gey6-x7c5
Aliases: CVE-2021-22884 |
Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to DNS rebinding attacks as the whitelist includes “localhost6”. When “localhost6” is not present in /etc/hosts, it is just an ordinary domain that is resolved via DNS, i.e., over network. If the attacker controls the victim's DNS server or can spoof its responses, the DNS rebinding protection can be bypassed by using the “localhost6” domain. As long as the attacker uses the “localhost6” domain, they can still apply the attack described in CVE-2018-7160. |
Affected by 31 other vulnerabilities. Affected by 13 other vulnerabilities. |
|
VCID-w45f-wj8b-4ugk
Aliases: CVE-2018-7167 |
Calling Buffer.fill() or Buffer.alloc() with some parameters can lead to a hang which could result in a Denial of Service. In order to address this vulnerability, the implementations of Buffer.alloc() and Buffer.fill() were updated so that they zero fill instead of hanging in these cases. All versions of Node.js 6.x (LTS "Boron"), 8.x (LTS "Carbon"), and 9.x are vulnerable. All versions of Node.js 10.x (Current) are NOT vulnerable. |
Affected by 31 other vulnerabilities. |
|
VCID-wg15-1yfy-ebg1
Aliases: CVE-2018-12121 |
Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Denial of Service with large HTTP headers: By using a combination of many requests with maximum sized headers (almost 80 KB per connection), and carefully timed completion of the headers, it is possible to cause the HTTP server to abort from heap allocation failure. Attack potential is mitigated by the use of a load balancer or other proxy layer. |
Affected by 31 other vulnerabilities. |
|
VCID-whe5-t9us-3kcb
Aliases: CVE-2021-44533 |
Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a single-value Relative Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in order to inject a Common Name that would allow bypassing the certificate subject verification.Affected versions of Node.js that do not accept multi-value Relative Distinguished Names and are thus not vulnerable to such attacks themselves. However, third-party code that uses node's ambiguous presentation of certificate subjects may be vulnerable. |
Affected by 13 other vulnerabilities. |
|
VCID-wv7u-zn1z-nufa
Aliases: CVE-2019-9514 GHSA-39qc-96h7-956f |
Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both. |
Affected by 31 other vulnerabilities. |
|
VCID-wvtc-3qza-afgh
Aliases: CVE-2019-9513 |
Excessive CPU usage in HTTP/2 with priority changes |
Affected by 31 other vulnerabilities. |
|
VCID-ww2t-7h1n-wye4
Aliases: CVE-2018-7158 |
The `'path'` module in the Node.js 4.x release line contains a potential regular expression denial of service (ReDoS) vector. The code in question was replaced in Node.js 6.x and later so this vulnerability only impacts all versions of Node.js 4.x. The regular expression, `splitPathRe`, used within the `'path'` module for the various path parsing functions, including `path.dirname()`, `path.extname()` and `path.parse()` was structured in such a way as to allow an attacker to craft a string, that when passed through one of these functions, could take a significant amount of time to evaluate, potentially leading to a full denial of service. |
Affected by 31 other vulnerabilities. |
|
VCID-xek7-efvx-eyb7
Aliases: CVE-2021-44532 |
Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.Versions of Node.js with the fix for this escape SANs containing the problematic characters in order to prevent the injection. This behavior can be reverted through the --security-revert command-line option. |
Affected by 13 other vulnerabilities. |
|
VCID-xhbn-z77y-d7c6
Aliases: CVE-2024-22025 |
A vulnerability in Node.js has been identified, allowing for a Denial of Service (DoS) attack through resource exhaustion when using the fetch() function to retrieve content from an untrusted URL. The vulnerability stems from the fact that the fetch() function in Node.js always decodes Brotli, making it possible for an attacker to cause resource exhaustion when fetching content from an untrusted URL. An attacker controlling the URL passed into fetch() can exploit this vulnerability to exhaust memory, potentially leading to process termination, depending on the system configuration. |
Affected by 12 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-xnc5-2mfd-1yfp
Aliases: CVE-2018-12123 |
Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Hostname spoofing in URL parser for javascript protocol: If a Node.js application is using url.parse() to determine the URL hostname, that hostname can be spoofed by using a mixed case "javascript:" (e.g. "javAscript:") protocol (other protocols are not affected). If security decisions are made about the URL based on the hostname, they may be incorrect. |
Affected by 31 other vulnerabilities. |
|
VCID-y19k-kvzc-2kgq
Aliases: CVE-2023-30589 GHSA-cggh-pq45-6h9x |
The llhttp parser in the http module in Node v20.2.0 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 impacts all Node.js active versions: v16, v18, and, v20 |
Affected by 12 other vulnerabilities. |
|
VCID-ym9e-zbqf-1ycg
Aliases: CVE-2024-27983 |
An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with HTTP/2 CONTINUATION frame are sent to the server and then a TCP connection is abruptly closed by the client triggering the Http2Session destructor while header frames are still being processed (and stored in memory) causing a race condition. |
Affected by 12 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-yzvu-9h4e-63hm
Aliases: CVE-2018-12120 |
Node.js: All versions prior to Node.js 6.15.0: Debugger port 5858 listens on any interface by default: When the debugger is enabled with `node --debug` or `node debug`, it listens to port 5858 on all interfaces by default. This may allow remote computers to attach to the debug port and evaluate arbitrary JavaScript. The default interface is now localhost. It has always been possible to start the debugger on a specific interface, such as `node --debug=localhost`. The debugger was removed in Node.js 8 and replaced with the inspector, so no versions from 8 and later are vulnerable. |
Affected by 31 other vulnerabilities. |
|
VCID-z158-x137-k7g6
Aliases: CVE-2018-7162 |
All versions of Node.js 9.x and 10.x are vulnerable and the severity is HIGH. An attacker can cause a denial of service (DoS) by causing a node process which provides an http server supporting TLS server to crash. This can be accomplished by sending duplicate/unexpected messages during the handshake. This vulnerability has been addressed by updating the TLS implementation. |
Affected by 31 other vulnerabilities. |
|
VCID-zjn1-8ez8-m7hn
Aliases: CVE-2024-27982 |
The team has identified a critical vulnerability in the http server of the most recent version of Node, where malformed headers can lead to HTTP request smuggling. Specifically, if a space is placed before a content-length header, it is not interpreted correctly, enabling attackers to smuggle in a second request within the body of the first. |
Affected by 12 other vulnerabilities. Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||