A cryptographic vulnerability exists in Node.js <19.2.0, <18.14.1, <16.19.1, <14.21.3 that in…
CVE-2023-23919 is a high-severity vulnerability in Node from Node.js, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 4.*, 5.*, 6.* as the first without the flaw, so updating Node to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 2.21% chance of exploitation within 30 days, higher than 83% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Node to 4.* or 5.* or 6.* or 7.*, whichever matches your release line, or a later version.
- Update Node.js to 14.21.3 or 16.19.1 or 18.14.1 or 19.2.0, whichever matches your release line, or a later version.
- Read the advisory on nodejs.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Node.js | Node | 4.0 up to, but not including, 4.*; 5.0 up to, but not including, 5.*; 6.0 up to, but not including, 6.*; 7.0 up to, but not including, 7.*; 8.0 up to, but not including, 8.*; 9.0 up to, but not including, 9.*; 10.0 up to, but not including, 10.*; 11.0 up to, but not including, 11.*; and 8 more ranges | 4.*, 5.*, 6.*, 7.*, 8.*, 9.* |
| Node.js | Node.js | 14.0.0 through 14.14.0; 14.0.0 up to, but not including, 14.21.3; 16.0.0 through 16.12.0; 16.0.0 up to, but not including, 16.19.1; 18.0.0 through 18.11.0; 18.0.0 up to, but not including, 18.14.1; 19.0.0 up to, but not including, 19.2.0 | 14.21.3, 16.19.1, 18.14.1, 19.2.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 3.1 | 7.5 | High | CISA (ADP) |
Official description
A cryptographic vulnerability exists in Node.js <19.2.0, <18.14.1, <16.19.1, <14.21.3 that in some cases did does not clear the OpenSSL error stack after operations that may set it. This may lead to false positive errors during subsequent cryptographic operations that happen to be on the same thread. This in turn could be used to cause a denial of service.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- hackerone.com/reports/1808596Exploit, Third Party Advisory
Other references
Other vulnerabilities in Node
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
Spotted an error? Tell us.