CVE-2023-46809
No exploitation reported by the sources we read.
- Published2024-09-07
- WeaknessCWE-385
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « 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
Node.js versions which bundle an unpatched version of OpenSSL or run against a dynamically linked version of OpenSSL which are unpatched are vulnerable to the Marvin Attack - https://people.redhat.com/~hkario/marvin/, if PCKS #1 v1.5 padding is allowed when performing RSA descryption using a private key.
Timeline
dates in UTC- 2024-09-0716:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-46809?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-46809?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
CISA-ADP · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 18.x | ≥ 18.0, ≤ 18.19.0 | no fix published | CISA-ADP |
| 20.x | ≥ 20.0, ≤ 20.11.0 | no fix published | CISA-ADP |
| 21.x | ≥ 21.0, ≤ 21.6.0 | no fix published | CISA-ADP |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 21.x | ≥ 21.0.0, < 21.6.1 | 21.6.1 | OSV |
| 20.11 | ≥ 19.0.0, < 20.11.1 | 20.11.1 | OSV |
| 18.19 | < 18.19.1 | 18.19.1 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 21.x | ≥ 21.0.0, < 21.6.1 | 21.6.1 | OSV |
| 20.11 | ≥ 19.0.0, < 20.11.1 | 20.11.1 | OSV |
| 18.19 | < 18.19.1 | 18.19.1 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
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
- nodejsAlmaLinux:9all versions · fixed in 1:18.19.1-1.module_el9.3.0+59+28b95644and 3 other packages
- nodejsAlmaLinux:9all versions · fixed in 1:20.11.1-1.module_el9.3.0+88+29afeaa2and 3 other packages
- nodejsAlmaLinux:8all versions · fixed in 1:18.19.1-1.module_el8.9.0+3753+4de0891band 3 other packages
- nodejsAlmaLinux:8all versions · fixed in 1:20.11.1-1.module_el8.9.0+3775+d8460d35and 3 other packages
- nodejs-nodemonAlmaLinux:9all versions · fixed in 3.0.1-1.module_el9.2.0+36+853e48f5
- nodejs-nodemonAlmaLinux:9all versions · fixed in 3.0.1-1.module_el9.3.0+47+c33bc288
- nodejs-nodemonAlmaLinux:8all versions · fixed in 3.0.1-1.module_el8.8.0+3613+1ed8c91d
- nodejs-nodemonAlmaLinux:8all versions · fixed in 3.0.1-1.module_el8.9.0+3731+490e3ce5
8 more package ranges on OSV.dev
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Published
- 2024-09-07
- Last Modified
- 2026-06-17
- NVD status
- Deferred
Frequently asked questions
What is CVE-2023-46809?
Is CVE-2023-46809 actively exploited?
What is the CVSS score for CVE-2023-46809?
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 ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.