Skip to content
Noroxi
CVE-2018-7160· NVD / CVE Program· CNA nodejs

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.

Noroxi assessment

Priority: Monitor (action score 38/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 9.8% (FIRST EPSS); higher than 95.4% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: nodejs (Alpine:v3.10) 8.11.0-r0; nodejs (Debian:12) 8.11.1~dfsg-2; rh-nodejs8-nodejs (Red Hat:rhel_software_collections:3::el7) 0:8.11.4-1.el7.

Low priority for now. Upgrade to nodejs (Alpine:v3.10) 8.11.0-r0; nodejs (Debian:12) 8.11.1~dfsg-2; rh-nodejs8-nodejs (Red Hat:rhel_software_collections:3::el7) 0:8.11.4-1.el7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

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.

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
May 17, 2018
Updated
Oct 8, 2026
EPSS
9.9% · 95th percentile

Report tools

JSON

Action score

38

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
3 / 30 · 9.9%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2018-7160

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for nodejs records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
nodejsnode.js

Using node.js? Add it to your stack and be the first to know about CVEs like this one. (Node.js)

Add to my stack

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • nodejs node.js6.0.0 and later · up to 6.8.1 inclusive
  • nodejs node.js6.9.0 and later · before 6.14.0
  • nodejs node.js8.0.0 and later · up to 8.8.1 inclusive
  • nodejs node.js8.9.0 and later · before 8.11.0
  • nodejs node.js9.0.0 and later · before 9.10.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (nodejs). Independent of NVD's CPE analysis and usually ahead of it.

  • The Node.js Project Node.js

    • ^6.0.0 || ^8.0.0 || ^9.0.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10nodejsbefore 8.11.0-r08.11.0-r0
Debian:12nodejsbefore 8.11.1~dfsg-28.11.1~dfsg-2
npmnode-inspectorfrom 6.0—
Red Hat:rhel_software_collections:3::el7rh-nodejs8-nodejsbefore 0:8.11.4-1.el70:8.11.4-1.el7
Red Hat:rhel_software_collections:3::el7rh-nodejs8-nodejs-debuginfobefore 0:8.11.4-1.el70:8.11.4-1.el7
Red Hat:rhel_software_collections:3::el7rh-nodejs8-nodejs-develbefore 0:8.11.4-1.el70:8.11.4-1.el7
Red Hat:rhel_software_collections:3::el7rh-nodejs8-nodejs-docsbefore 0:8.11.4-1.el70:8.11.4-1.el7
Red Hat:rhel_software_collections:3::el7rh-nodejs8-npmbefore 0:5.6.0-8.11.4.1.el70:5.6.0-8.11.4.1.el7
SUSE:OpenStack Cloud 7nodejs6before 6.14.1-11.12.16.14.1-11.12.1

Same product

nodejs: all records

Other highest-scoring records for the same primary product.

  • CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed
    56Plan
  • CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an
    53Plan
  • CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory c
    50Plan
  • CVE-2021-22931Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application crashes due to missing input validation
    46Plan
  • CVE-2020-8277A Node.js application that allows an attacker to trigger a DNS request for a host of their choice could trigger a Denial of Service in versi
    46Plan
  • CVE-2017-14849Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was incompatible with the p
    46Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:nodejs8.11.0-r0 · Alpine:v3.10Package registry (OSV)
debian:nodejs8.11.1~dfsg-2 · Debian:12Package registry (OSV)
red hat:rh-nodejs8-nodejs0:8.11.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs8-nodejs-debuginfo0:8.11.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs8-nodejs-devel0:8.11.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs8-nodejs-docs0:8.11.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs8-npm0:5.6.0-8.11.4.1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
suse:nodejs66.14.1-11.12.1 · SUSE:OpenStack Cloud 7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-350 · Reliance on Reverse DNS Resolution for a Security-Critical Action

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records