Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| The Node.js Project | Node.js | ^6.0.0 || ^8.0.0 || ^9.0.0 |
References
- https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/Vendor Advisory
- https://support.f5.com/csp/article/K63025104?utm_source=f5support&%3Butm_medium=RSS
- https://www.oracle.com//security-alerts/cpujul2021.htmlThird Party Advisory
- https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/Vendor Advisory
- https://support.f5.com/csp/article/K63025104?utm_source=f5support&%3Butm_medium=RSS
- https://www.oracle.com//security-alerts/cpujul2021.htmlThird Party Advisory
Timeline
- Published
- May 17, 2018
- Last modified
- Oct 8, 2026
- NVD status
- Modified