CVE-2023-23919: NodeJS vulnerability
NodeJS · Node
Vendor fix available · Affected: NodeJS · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 82% of scored CVEs
DescriptionCVE.org
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 products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- NodeJS · Nodefrom 4.0 before 4.*; from 5.0 before 5.*; from 6.0 before 6.*; from 7.0 before 7.*; from 8.0 before 8.*; from 9.0 before 9.* and 10 more
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- NodeJS
- Published
- February 2023
- Bounty reports
- 2 disclosed on HackerOne
Disclosed bug bounty reports about CVE-2023-23919
The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.
- CVE-2023-23919: Multiple OpenSSL error handling issues in nodejs crypto libraryInternet Bug Bounty · 2023 · medium severityValid
- Multiple OpenSSL error handling issues in nodejs crypto libraryNode.js · 2023 · medium severityValid
CoverageNo articles yet
No CyberSIXT article names CVE-2023-23919 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.