Node.js vulnerabilitiesAnd the versions its exploited flaws hit.
Node.js is made by Nodejs. We track 157 published vulnerabilities in it, across 872 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 10 October 2023. If you run Node.js, check your version against the exploited flaws below and patch those first.
The most recent Node.js flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023. We keep watching the known-exploited list.
Which versions of Node.js do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "18.0.0 to before 18.18.2" means from 18.0.0 up to, but not including, 18.18.2. Find your version, then patch.
- CVE-2023-44487Exploited list, 10 Oct 2023
HTTP/2 Rapid Reset Attack Vulnerability
18.0.0 to before 18.18.220.0.0 to before 20.8.1
Which Node.js vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 7.5HTTP/2 Rapid Reset Attack Vulnerability
HTTP/2 contains a rapid reset vulnerability that allows for a distributed denial-of-service attack (DDoS).
Which Node.js flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
- 95%CVE-2014-0224High
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCipherSpec messages, which allows man-in-the-middle attackers to trigger use of a zero-length master...
- 95%CVE-2016-2183High
The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to...
- 92%CVE-2022-3786High
A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking.
- 91%CVE-2022-3602High
A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking.
- 89%CVE-2016-2107Medium
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a certain padding check, which allows remote attackers to obtain sensitive cleartext information...
- 87%CVE-2019-9515High
Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service.
- 83%CVE-2019-9512High
Some HTTP/2 implementations are vulnerable to ping floods, potentially leading to a denial of service.
- 83%CVE-2019-9514High
Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service.
- 82%CVE-2022-32214Medium
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.
Running Node.js? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
HTTP/2 contains a rapid reset vulnerability that allows for a distributed denial-of-service attack (DDoS).
- Matched to
- Node.js on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 157 published vulnerabilities listed under the name Node.js, across 872 versions. The most recent Node.js flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2023-44487.
Each flaw names its own versions, usually as ranges. The newest, CVE-2023-44487, affects 18.0.0 to before 18.18.2, 20.0.0 to before 20.8.1. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Node.js. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.