CVE-2020-8252: The implementation of realpath in libuv < 10.22.1, < 12.18.4, and < 14.9.0 used within Node.js incorrectly determined the buffer size which
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: 0.71% (FIRST EPSS); higher than 53.5% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: NodeJS Node 10.22.1, 11.*, 12.18.4.
- Mentioned 3 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to NodeJS Node 10.22.1, 11.*, 12.18.4 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
The implementation of realpath in libuv < 10.22.1, < 12.18.4, and < 14.9.0 used within Node.js incorrectly determined the buffer size which can result in a buffer overflow if the resolved path is longer than 256 bytes.
- Published
- Sep 18, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- CWE-120
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
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 |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
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.js10.0.0 and later · before 10.22.1
- nodejs node.js12.0.0 and later · before 12.18.4
- nodejs node.js14.0.0 and later · before 14.9.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.22.1affected · semver
- 11.0 and later · before 11.*affected · semver
- 12.0 and later · before 12.18.4affected · 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-nodemon | before 1.18.3-1.module_el8.3.0+2023+d2377ea3 | 1.18.3-1.module_el8.3.0+2023+d2377ea3 |
| AlmaLinux:8 | nodejs-nodemon | before 1.18.3-1.module_el8.3.0+2047+b07ac28e | 1.18.3-1.module_el8.3.0+2047+b07ac28e |
| AlmaLinux:8 | nodejs-packaging | before 17-3.module_el8.3.0+2023+d2377ea3 | 17-3.module_el8.3.0+2023+d2377ea3 |
| AlmaLinux:8 | nodejs-packaging | before 17-3.module_el8.4.0+2224+b07ac28e | 17-3.module_el8.4.0+2224+b07ac28e |
| AlmaLinux:8 | nodejs-packaging | before 17-3.module_el8.4.0+2521+c668cc9f | 17-3.module_el8.4.0+2521+c668cc9f |
| Alpine:v3.11 | nodejs | before 12.20.1-r0 | 12.20.1-r0 |
| Alpine:v3.12 | libuv | before 1.38.1-r0 | 1.38.1-r0 |
| Alpine:v3.12 | nodejs | before 12.18.4-r0 | 12.18.4-r0 |
| Alpine:v3.13 | libuv | before 1.39.0-r0 | 1.39.0-r0 |
| Debian:12 | libuv1 | before 1.39.0-1 | 1.39.0-1 |
| openSUSE:Leap 15.2 | nodejs10 | before 10.22.1-lp152.2.6.1 | 10.22.1-lp152.2.6.1 |
| openSUSE:Leap 15.2 | nodejs12 | before 12.18.4-lp152.3.6.1 | 12.18.4-lp152.3.6.1 |
| Red Hat:enterprise_linux:8::appstream | nodejs | before 1:10.23.1-1.module+el8.3.0+9502+012d8a97 | 1:10.23.1-1.module+el8.3.0+9502+012d8a97 |
| Red Hat:enterprise_linux:8::appstream | nodejs | before 1:12.18.4-2.module+el8.2.0+8361+192e434e | 1:12.18.4-2.module+el8.2.0+8361+192e434e |
| Red Hat:enterprise_linux:8::appstream | nodejs-debuginfo | before 1:12.18.4-2.module+el8.2.0+8361+192e434e | 1:12.18.4-2.module+el8.2.0+8361+192e434e |
| Red Hat:enterprise_linux:8::appstream | nodejs-debuginfo | before 1:10.23.1-1.module+el8.3.0+9502+012d8a97 | 1:10.23.1-1.module+el8.3.0+9502+012d8a97 |
| Red Hat:enterprise_linux:8::appstream | nodejs-debugsource | before 1:12.18.4-2.module+el8.2.0+8361+192e434e | 1:12.18.4-2.module+el8.2.0+8361+192e434e |
| Red Hat:enterprise_linux:8::appstream | nodejs-debugsource | before 1:10.23.1-1.module+el8.3.0+9502+012d8a97 | 1:10.23.1-1.module+el8.3.0+9502+012d8a97 |
| Red Hat:enterprise_linux:8::appstream | nodejs-devel | before 1:10.23.1-1.module+el8.3.0+9502+012d8a97 | 1:10.23.1-1.module+el8.3.0+9502+012d8a97 |
| Red Hat:enterprise_linux:8::appstream | nodejs-devel | before 1:12.18.4-2.module+el8.2.0+8361+192e434e | 1:12.18.4-2.module+el8.2.0+8361+192e434e |
| Red Hat:enterprise_linux:8::appstream | nodejs-docs | before 1:10.23.1-1.module+el8.3.0+9502+012d8a97 | 1:10.23.1-1.module+el8.3.0+9502+012d8a97 |
| Red Hat:enterprise_linux:8::appstream | nodejs-docs | before 1:12.18.4-2.module+el8.2.0+8361+192e434e | 1:12.18.4-2.module+el8.2.0+8361+192e434e |
| Red Hat:enterprise_linux:8::appstream | nodejs-full-i18n | before 1:10.23.1-1.module+el8.3.0+9502+012d8a97 | 1:10.23.1-1.module+el8.3.0+9502+012d8a97 |
| Red Hat:enterprise_linux:8::appstream | nodejs-full-i18n | before 1:12.18.4-2.module+el8.2.0+8361+192e434e | 1:12.18.4-2.module+el8.2.0+8361+192e434e |
+29
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-2020-8201Sep 18, 2020 · Node.js < 12.18.4 and < 14.11 can be exploited to perform HTTP desync attacks and deliver malicious payloads to unsuspecting users.31Monitor
- ← EarlierCVE-2020-8251Sep 18, 2020 · Node.js < 14.11.0 is vulnerable to HTTP denial of service (DoS) attacks based on delayed requests submission which can make the server unabl33Monitor
- Later →CVE-2020-8277Nov 18, 2020 · A Node.js application that allows an attacker to trigger a DNS request for a host of their choice could trigger a Denial of Service in versi46Plan
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.22.1 | Vendor (CNA) |
| NodeJS Node | 11.* | Vendor (CNA) |
| NodeJS Node | 12.18.4 | Vendor (CNA) |
| NodeJS Node | 13.* | Vendor (CNA) |
| NodeJS Node | 14.9.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-nodemon | 1.18.3-1.module_el8.3.0+2023+d2377ea3 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging | 17-3.module_el8.4.0+2224+b07ac28e · AlmaLinux:8 | Package registry (OSV) |
| alpine:libuv | 1.38.1-r0 · Alpine:v3.12 | Package registry (OSV) |
| alpine:nodejs | 12.20.1-r0 · Alpine:v3.11 | Package registry (OSV) |
| debian:libuv1 | 1.39.0-1 · Debian:12 | Package registry (OSV) |
| opensuse:nodejs10 | 10.22.1-lp152.2.6.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| opensuse:nodejs12 | 12.18.4-lp152.3.6.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| red hat:nodejs | 1:12.18.4-2.module+el8.2.0+8361+192e434e · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-debuginfo | 1:12.18.4-2.module+el8.2.0+8361+192e434e · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-debugsource | 1:12.18.4-2.module+el8.2.0+8361+192e434e · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-devel | 1:12.18.4-2.module+el8.2.0+8361+192e434e · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-docs | 1:12.18.4-2.module+el8.2.0+8361+192e434e · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-full-i18n | 1:12.18.4-2.module+el8.2.0+8361+192e434e · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-nodemon | 0:1.18.3-1.module+el8.1.0+3369+37ae6a45 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-packaging | 0:17-3.module+el8.1.0+3369+37ae6a45 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:npm | 1:6.14.6-1.12.18.4.2.module+el8.2.0+8361+192e434e · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:rh-nodejs12-nodejs | 0:12.18.4-3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs12-nodejs-debuginfo | 0:12.18.4-3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs12-nodejs-devel | 0:12.18.4-3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
+4
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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0453 · Jun 8, 2021(IBM Güvenlik Bülteni Yayınladı)
- TR-21-0096 · Feb 3, 2021(IBM, Ürünlerine İlişkin Güvenlik Bülteni Yayınladı)
- TR-20-955 · Nov 13, 2020(IBM Ürünleri Zafiyeti)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];
memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];
if (pkt->len > sizeof(buf)) {
return -EINVAL;
}
memcpy(buf, pkt->data, pkt->len);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- lists.opensuse.org/opensuse-security-announce/2020-10/msg00023.html
- hackerone.com/reports/965914
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4OOYAMJVLLCLXDTHW3V5UXNULZBBK4O6/
- nodejs.org/en/blog/vulnerability/september-2020-security-releases/
- security.gentoo.org/glsa/202009-15
- security.netapp.com/advisory/ntap-20201009-0004/
- usn.ubuntu.com/4548-1/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.