Skip to content

Withdrawn Advisory: Node.js Inspector RCE via DNS Rebinding

High severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Oct 9, 2023
Withdrawn This advisory was withdrawn on Oct 9, 2023

Package

npm node-inspector (npm)

Affected versions

>= 6.0

Patched versions

None

Description

Withdrawn Advisory

This advisory has been withdrawn because this vulnerability affects inspector code in https://github.com/nodejs/node, not the legacy debugger at https://github.com/node-inspector/node-inspector. https://github.com/nodejs/node is not in a supported ecosystem.

Original 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.

References

Published by the National Vulnerability Database May 17, 2018
Published to the GitHub Advisory Database May 13, 2022
Reviewed Jul 20, 2023
Withdrawn Oct 9, 2023
Last updated Oct 9, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

3.260%
(92nd percentile)

Weaknesses

CVE ID

CVE-2018-7160

GHSA ID

GHSA-wq4c-wm6x-jw44

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.