Node.js

Every one of the 19 is a mark on the map. Named now: 1 to 19, most at risk first.

1. 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 ver…CVE-2018-12122The Node.js Project · 41% likely

   CWE-400

2. 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…CVE-2019-5737Node.js · 16% likely

   CWE-400

3. 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 he…CVE-2018-12121The Node.js Project · 10% likely

   CWE-400

4. 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 web…CVE-2018-7160The Node.js Project · 9.5% likely

   CWE-350

5. 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'…CVE-2018-12115The Node.js Project · 7.8% likely

   CWE-787

6. 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 ser…CVE-2018-7161The Node.js Project · 7.5% likely

   CWE-20

7. Command injection vulnerability in programing languages on Microsoft Windows operating system.CVE-2024-3566Node.js · CVSS 9.8 · 6.8% likely

   CWE-78

8. 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 implementati…CVE-2018-7167The Node.js Project · 6.7% likely

   CWE-119

9. 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 serv…CVE-2018-7162The Node.js Project · 6.6% likely

   CWE-20

10. 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 Jav…CVE-2018-7164The Node.js Project · 6.2% likely

    CWE-400

11. Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node.js 6.16.0 and earlier. Node.js 8.0.0 introduced a dedicated server.keepAliveTimeout…CVE-2019-5739Node.js · 4.9% likely

    CWE-400

12. 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 o…CVE-2018-12116The Node.js Project · 4.6% likely

    CWE-115

13. 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…CVE-2018-12120The Node.js Project · 4.3% likely

    CWE-419

14. 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() t…CVE-2018-12123The Node.js Project · 4.0% likely

    CWE-115

15. 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…CVE-2018-7159The Node.js Project · 3.5% likely

    CWE-115

16. 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…CVE-2018-7158The Node.js Project · 3.5% likely

    CWE-185

17. In all versions of Node.js 10 prior to 10.9.0, an argument processing flaw can cause `Buffer.alloc()` to return uninitialized memory. This method is intended to be safe and only r…CVE-2018-7166The Node.js Project · 3.3% likely

    CWE-226

18. Node.js was affected by OpenSSL vulnerability CVE-2017-3737 in regards to the use of SSL_read() due to TLS handshake failure. The result was that an active network attacker could…CVE-2017-15896The Node.js Project · 2.4% likely
19. Node.js had a bug in versions 8.X and 9.X which caused buffers to not be initialized when the encoding for the fill value did not match the encoding specified. For example, 'Buffe…CVE-2017-15897The Node.js Project · 2.3% likely

    CWE-665

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.