CVE-2018-7166: The Node.js Project Node.js vulnerability
The Node.js Project · Node.js
Vendor fix available · Affected: The Node.js Project Node.js · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 88% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
In all versions of Node.js 10 prior to 10.9.0, an argument processing flaw can cause `Buffer.alloc()` to return uninitialized memory. This method is intended to be safe and only return initialized, or cleared, memory. The third argument specifying `encoding` can be passed as a number, this is misinterpreted by `Buffer's` internal "fill" method as the `start` to a fill operation. This flaw may be abused where `Buffer.alloc()` arguments are derived from user input to return uncleared memory blocks that may contain sensitive information.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- The Node.js Project · Node.jsAll versions of Node.js 10 prior to 10.9.0
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
- The Node.js Project
- Published
- August 2018
CoverageNo articles yet
No CyberSIXT article names CVE-2018-7166 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.