CVE-2018-7160: The Node.js Project Node.js vulnerability
The Node.js Project · Node.js
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 95% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution. An attack is possible from malicious websites open in a web browser on the same computer, or another computer with network access to the computer running the Node.js process. A malicious website could use a DNS rebinding attack to trick the web browser to bypass same-origin-policy checks and to allow HTTP connections to localhost or to hosts on the local network. If a Node.js process with the debug port active is running on localhost or on a host on the local network, the malicious website could connect to it as a debugger, and get full code execution access.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- The Node.js Project · Node.js^6.0.0 || ^8.0.0 || ^9.0.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
- May 2018
CoverageNo articles yet
No CyberSIXT article names CVE-2018-7160 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.