Skip to main content
Public proof of conceptFix available

CVE-2023-23919

A public proof of concept exists; no exploitation attested.

  • Published2023-02-23
  • Fixed in19.2.0 · 18.14.1 · 16.19.1 · 14.21.3
  • WeaknessCWE-310

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2023-02-2320:15CVE publishedNVD

Versions per branch

NVD · OSV
Node.js
BranchAffectedFixed in
19.x≥ 19.0.0, < 19.2.019.2.0
18.x≥ 18.0.0, < 18.14.118.14.1
16.x≥ 16.0.0, < 16.19.116.19.1
14.x≥ 14.0.0, < 14.21.314.21.3
14.x≥ 14.0.0, ≤ 14.14.0no fix published
16.x≥ 16.0.0, ≤ 16.12.0no fix published
18.x≥ 18.0.0, ≤ 18.11.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As hackerone, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • NodeJS Nodeother versions: not affected
    Affected
    • ≥ 4.0, < 4.*no fix statedsemver
    • ≥ 5.0, < 5.*no fix statedsemver
    • ≥ 6.0, < 6.*no fix statedsemver
    • ≥ 7.0, < 7.*no fix statedsemver
    • ≥ 8.0, < 8.*no fix statedsemver
    • ≥ 9.0, < 9.*no fix statedsemver
    • ≥ 10.0, < 10.*no fix statedsemver
    • ≥ 11.0, < 11.*no fix statedsemver

    8 more version lines in the CVE record.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-04-30

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • nodejsUbuntu:22.04:LTSall versions · fixed in 12.22.9~dfsg-1ubuntu3.4
  • nodejsUbuntu:20.04:LTSall versions · fixed in 10.19.0~dfsg-3ubuntu1.5
  • nodejsRocky Linux:8all versions · fixed in 1:16.19.1-1.module+el8.7.0+1178+d52dba78
  • nodejsRed Hat:enterprise_linux:9::appstreamall versions · fixed in 1:18.14.2-2.module+el9.2.0.z+18497+a402347cand 5 other packages
  • nodejsRed Hat:enterprise_linux:8::appstreamall versions · fixed in 1:16.19.1-1.module+el8.7.0+18373+704f5cefand 5 other packages
  • nodejsRed Hat:enterprise_linux:8::appstreamall versions · fixed in 1:18.14.2-2.module+el8.7.0+18445+9493b6eaand 5 other packages
  • nodejsDebian:14all versions · fixed in 18.13.0+dfsg1-1.1
  • nodejsDebian:13all versions · fixed in 18.13.0+dfsg1-1.1

54 more package ranges on OSV.dev

Vendor advisories

  • CVE-2023-23919 Red Hat Product Security92 products fixed · 1 known affected

    Node.js: OpenSSL error handling issues in nodejs crypto library

    3scale-amp2/system-rhel7 as a component of Red Hat 3scale API Management Platform 2

  • RHSA-2023:2654 Red Hat Product Security31 products fixed

    Red Hat Security Advisory: nodejs:18 security, bug fix, and enhancement update

  • RHSA-2023:1583 Red Hat Product Security31 products fixed

    Red Hat Security Advisory: nodejs:18 security, bug fix, and enhancement update

  • RHSA-2023:1582 Red Hat Product Security30 products fixed

    Red Hat Security Advisory: nodejs:16 security, bug fix, and enhancement update

Full record on NVD

Fix

  1. Update Node.js to 19.2.0 · 18.14.1 · 16.19.1 · 14.21.3
  2. Vendor fix Red Hat Product Security RHSA-2023:2654 · 31 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
  3. No fix planned, says the vendor Red Hat Product Security CVE-2023-23919 · 1 productWill not fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2023-02-23
Last Modified
2026-10-24
NVD status
Modified
GitHub Advisory
GHSA-mfq6-mjjx-mp7f

Frequently asked questions

What is CVE-2023-23919?

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.

Is CVE-2023-23919 actively exploited?

A proof-of-concept exploit exists for CVE-2023-23919, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2023-23919?

CVE-2023-23919 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running Node.js? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record