CVE-2018-7160
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 9.5% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 9.5% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 9.5% · EPSS, next 30 days
- Weakness
- CWE-350
- Record status
- Modified
Affected
- Nodejs node.js ≤ 6.8.1
- Nodejs node.js < 6.14.0
- Nodejs node.js ≤ 8.8.1
- Nodejs node.js < 8.11.0
- Nodejs node.js < 9.10.0
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2018-7160.md and follow it. Check whether this project is affected by CVE-2018-7160. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/
- https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/
References
- https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/
- https://support.f5.com/csp/article/K63025104?utm_source=f5support&%3Butm_medium=RSS
- https://www.oracle.com//security-alerts/cpujul2021.html
- https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/
- https://support.f5.com/csp/article/K63025104?utm_source=f5support&%3Butm_medium=RSS
- https://www.oracle.com//security-alerts/cpujul2021.html