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 erro
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.2% (FIRST EPSS); higher than 82.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: NodeJS Node 10.*, 11.*, 12.*.
Low priority for now. Upgrade to NodeJS Node 10.*, 11.*, 12.* or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 23, 2023
- Updated
- Jun 17, 2026
- EPSS
- 2.2% · 82th percentile
- CWE
- CWE-310
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| nodejs | node.js | cpe:2.3:a:nodejs:node.js |
Using node.js? Add it to your stack and be the first to know about CVEs like this one. (Node.js)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs node.js14.0.0 and later · up to 14.14.0 inclusive
- nodejs node.js14.0.0 and later · before 14.21.3
- nodejs node.js16.0.0 and later · up to 16.12.0 inclusive
- nodejs node.js16.0.0 and later · before 16.19.1
- nodejs node.js18.0.0 and later · up to 18.11.0 inclusive
- nodejs node.js18.0.0 and later · before 18.14.1
- nodejs node.js19.0.0 and later · before 19.2.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.
NodeJS Node
- 4.0 and later · before 4.*affected · semver
- 5.0 and later · before 5.*affected · semver
- 6.0 and later · before 6.*affected · semver
- 7.0 and later · before 7.*affected · semver
- 8.0 and later · before 8.*affected · semver
- 9.0 and later · before 9.*affected · semver
- 10.0 and later · before 10.*affected · semver
- 11.0 and later · before 11.*affected · semver
- 12.0 and later · before 12.*affected · semver
- 13.0 and later · before 13.*affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | nodejs | before 1:16.19.1-1.module_el8.7.0+3496+a59a3324 | 1:16.19.1-1.module_el8.7.0+3496+a59a3324 |
| AlmaLinux:8 | nodejs-devel | before 1:16.19.1-1.module_el8.7.0+3496+a59a3324 | 1:16.19.1-1.module_el8.7.0+3496+a59a3324 |
| AlmaLinux:8 | nodejs-docs | before 1:16.19.1-1.module_el8.7.0+3496+a59a3324 | 1:16.19.1-1.module_el8.7.0+3496+a59a3324 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:16.19.1-1.module_el8.7.0+3496+a59a3324 | 1:16.19.1-1.module_el8.7.0+3496+a59a3324 |
| AlmaLinux:8 | nodejs-nodemon | before 2.0.20-3.module_el8.7.0+3496+a59a3324 | 2.0.20-3.module_el8.7.0+3496+a59a3324 |
| AlmaLinux:8 | nodejs-packaging | before 25-1.module_el8.5.0+2605+45d748af | 25-1.module_el8.5.0+2605+45d748af |
| AlmaLinux:8 | npm | before 1:8.19.3-1.16.19.1.1.module_el8.7.0+3496+a59a3324 | 1:8.19.3-1.16.19.1.1.module_el8.7.0+3496+a59a3324 |
| AlmaLinux:9 | nodejs | before 1:18.14.2-2.module_el9.2.0+29+de583a0b | 1:18.14.2-2.module_el9.2.0+29+de583a0b |
| AlmaLinux:9 | nodejs-devel | before 1:18.14.2-2.module_el9.2.0+29+de583a0b | 1:18.14.2-2.module_el9.2.0+29+de583a0b |
| AlmaLinux:9 | nodejs-docs | before 1:18.14.2-2.module_el9.2.0+29+de583a0b | 1:18.14.2-2.module_el9.2.0+29+de583a0b |
| AlmaLinux:9 | nodejs-full-i18n | before 1:18.14.2-2.module_el9.2.0+29+de583a0b | 1:18.14.2-2.module_el9.2.0+29+de583a0b |
| AlmaLinux:9 | nodejs-nodemon | before 2.0.20-2.module_el9.2.0+29+de583a0b | 2.0.20-2.module_el9.2.0+29+de583a0b |
| AlmaLinux:9 | nodejs-packaging | before 2021.06-4.module_el9.1.0+13+d9a595ea | 2021.06-4.module_el9.1.0+13+d9a595ea |
| AlmaLinux:9 | nodejs-packaging-bundler | before 2021.06-4.module_el9.1.0+13+d9a595ea | 2021.06-4.module_el9.1.0+13+d9a595ea |
| AlmaLinux:9 | npm | before 1:9.5.0-1.18.14.2.2.module_el9.2.0+29+de583a0b | 1:9.5.0-1.18.14.2.2.module_el9.2.0+29+de583a0b |
| Alpine:v3.15 | nodejs | before 16.19.1-r0 | 16.19.1-r0 |
| Alpine:v3.17 | nodejs | before 18.14.1-r0 | 18.14.1-r0 |
| Debian:12 | nodejs | before 18.19.0+dfsg-6~deb12u1 | 18.19.0+dfsg-6~deb12u1 |
| Debian:13 | nodejs | before 18.13.0+dfsg1-1.1 | 18.13.0+dfsg1-1.1 |
| openSUSE:Tumbleweed | nodejs18 | before 18.14.2-1.1 | 18.14.2-1.1 |
| openSUSE:Tumbleweed | nodejs19 | before 19.7.0-1.1 | 19.7.0-1.1 |
| Red Hat:enterprise_linux:8::appstream | nodejs | before 1:18.14.2-2.module+el8.7.0+18445+9493b6ea | 1:18.14.2-2.module+el8.7.0+18445+9493b6ea |
| Red Hat:enterprise_linux:8::appstream | nodejs | before 1:16.19.1-1.module+el8.7.0+18373+704f5cef | 1:16.19.1-1.module+el8.7.0+18373+704f5cef |
| Red Hat:enterprise_linux:8::appstream | nodejs-debuginfo | before 1:18.14.2-2.module+el8.7.0+18445+9493b6ea | 1:18.14.2-2.module+el8.7.0+18445+9493b6ea |
+40
Same product
nodejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed56Plan
- CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an 53Plan
- CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory c50Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-23936Feb 16, 2023 · CRLF Injection in Nodejs ‘undici’ via host21Monitor
- ← EarlierCVE-2023-23918Feb 23, 2023 · A privilege escalation vulnerability exists in Node.js <19.6.1, <18.14.1, <16.19.1 and <14.21.3 that made it possible to bypass the experime31Monitor
- Later →CVE-2023-23920Feb 23, 2023 · An untrusted search path vulnerability exists in Node.js.16Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| NodeJS Node | 10.* | Vendor (CNA) |
| NodeJS Node | 11.* | Vendor (CNA) |
| NodeJS Node | 12.* | Vendor (CNA) |
| NodeJS Node | 13.* | Vendor (CNA) |
| NodeJS Node | 14.21.3 | Vendor (CNA) |
| NodeJS Node | 15.* | Vendor (CNA) |
| NodeJS Node | 16.19.1 | Vendor (CNA) |
| NodeJS Node | 17.* | Vendor (CNA) |
| NodeJS Node | 18.14.1 | Vendor (CNA) |
| NodeJS Node | 19.2.0 | Vendor (CNA) |
| NodeJS Node | 4.* | Vendor (CNA) |
| NodeJS Node | 5.* | Vendor (CNA) |
| NodeJS Node | 6.* | Vendor (CNA) |
| NodeJS Node | 7.* | Vendor (CNA) |
| NodeJS Node | 8.* | Vendor (CNA) |
| NodeJS Node | 9.* | Vendor (CNA) |
| almalinux:nodejs | 1:16.19.1-1.module_el8.7.0+3496+a59a3324 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-devel | 1:16.19.1-1.module_el8.7.0+3496+a59a3324 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-docs | 1:16.19.1-1.module_el8.7.0+3496+a59a3324 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-full-i18n | 1:16.19.1-1.module_el8.7.0+3496+a59a3324 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-nodemon | 2.0.20-3.module_el8.7.0+3496+a59a3324 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging | 25-1.module_el8.5.0+2605+45d748af · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging-bundler | 2021.06-4.module_el9.1.0+13+d9a595ea · AlmaLinux:9 | Package registry (OSV) |
| almalinux:npm | 1:8.19.3-1.16.19.1.1.module_el8.7.0+3496+a59a3324 · AlmaLinux:8 | Package registry (OSV) |
| alpine:nodejs | 16.19.1-r0 · Alpine:v3.15 | Package registry (OSV) |
| debian:nodejs | 18.19.0+dfsg-6~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:nodejs16 | 16.19.1-150400.3.15.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:nodejs18 | 18.14.2-150400.9.6.2 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:nodejs19 | 19.7.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:nodejs | 1:16.19.1-1.module+el8.7.0+18373+704f5cef · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
+15
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-310 · Cryptographic IssuesCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.