CVE-2018-7160
CVE-2018-7160 Vulnerability Analysis & Exploit Intelligence
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.
Published Updated Sources: cvelistV5, nodejs
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
10%
chance of exploitation in 30 days
CVSS base
Unscored
no source published a base score
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Weakness & attack patterns
- CWE-350
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1584.002Compromise Infrastructure: DNS Server
References
3 on the record
- www.oracle.com//security-alerts/cpujul2021.html
x_refsource_MISC
- nodejs.org/en/blog/vulnerability/march-2018-security-releases/
x_refsource_CONFIRM
- support.f5.com/csp/article/K63025104?utm_source=f5support&%3Butm_medium=RSS
x_refsource_CONFIRM
Elsewhere on this site
- the node js projectevery CVE for this vendor
- CWE-350other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.