vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2023-23919

HIGH
7.5
CVSS Score
Published: February 23, 2023 at 12:00 AM UTC
Updated: October 24, 2026 at 01:10 PM UTC
1 product affected across 1 vendorNode.js

Using Node by NodeJS?

Get instant alerts when new vulnerabilities affect Node - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
HIGH7.5
Exploit prediction
EPSS 2%
SSVC
PoC

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Node.js· Node.js
95%
14.0.0 ≤ v ≤ 14.14.014.0.0 ≤ v < 14.21.316.0.0 ≤ v ≤ 16.12.016.0.0 ≤ v < 16.19.118.0.0 ≤ v ≤ 18.11.018.0.0 ≤ v < 18.14.119.0.0 ≤ v < 19.2.010.011.012.013.014.015.016.017.018.019.04.05.06.07.08.09.0
Affected range stops below 10.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 11.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 12.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 13.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 14.21.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 15.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.19.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.14.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.2.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.*, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (3)

ExploitThird Party Advisory
Source: [email protected]
https://hackerone.com/reports/1808596
PatchVendor Advisory
Source: [email protected]
https://nodejs.org/en/blog/vulnerability/february-2023-security-releases/
Source: [email protected]
https://security.netapp.com/advisory/ntap-20230316-0008/

SSVC — Action Prioritization

SSVCPoCAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHCISA-ADP
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-310NVD-CWE-Other

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card