cve.bz

CVE-2018-12120 nodejs node.js: Unprotected Primary Channel

8.1 highEPSS 4.3%Fix available

High (8.1) in nodejs node.js. EPSS 4.3% estimated probability of exploitation activity in the next 30 days.

On this page
Node.js: All versions prior to Node.js 6.15.0: Debugger port 5858 listens on any interface by default: When the debugger is enabled with `node --debug` or `node debug`, it listens to port 5858 on all interfaces by default. This may allow remote computers to attach to the debug port and evaluate arbitrary JavaScript. The default interface is now localhost. It has always been possible to start the debugger on a specific interface, such as `node --debug=localhost`. The debugger was removed in Node.js 8 and replaced with the inspector, so no versions from 8 and later are vulnerable.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
4.3% (unchanged from 4.3% a week ago; 4.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 91st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-829 Inclusion of Functionality from Untrusted Control Sphere
CWE-419 Unprotected Primary Channel
OWASP Top 10
A06:2025 Insecure Design, A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2018-12120 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2018-12120?via=ask-ai-copy and https://cve.bz/cve/CVE-2018-12120?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2018-12120 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2018-12120

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2018-12120](https://cve.bz/cve/badge/CVE-2018-12120.svg)](https://cve.bz/cve/CVE-2018-12120)

HTML:

<a href="https://cve.bz/cve/CVE-2018-12120"><img src="https://cve.bz/cve/badge/CVE-2018-12120.svg" alt="CVE-2018-12120"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
nodejs:node.jsfrom 6.0.0 before 6.15.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14nodejs8.9.3~dfsg-5DEBIAN-CVE-2018-12120
SUSEEnterprise Storage 4, Linux Enterprise Module for Web and Scripting 12nodejs44.9.1-15.17.1SUSE-SU-2019:0117-1
SUSEEnterprise Storage 4, Linux Enterprise Module for Web and Scripting 12, OpenStack Cloud 7 and 1 morenodejs66.16.0-11.21.1SUSE-SU-2019:0395-1

From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · SUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

The nodejs RPMs shipped in Red Hat OpenShift Container Platform (OCP) versions 3.6 through 3.10 are vulnerable to this flaw because they contain the affected code. Later versions of OCP used nodejs RPMs delivered from Red Hat Software Collections and Red Hat Enterprise Linux channels.

Red Hat's mitigation

* On any version :

Ensure the firewall prevents access to port 5858 on untrusted interfaces.

* On nodejs 6 :

To enforce the debug on a specific interface:

$ node --debug=localhost

ProductPackageStateAdvisory
Red Hat Enterprise Linux 8nodejsNot affected
Red Hat OpenShift Application RuntimesnodejsNot affected
Red Hat OpenShift Container Platform 3.10nodejsFix deferred
Red Hat OpenShift Container Platform 3.2nodejsOut of support scope
Red Hat OpenShift Container Platform 3.3nodejsOut of support scope
Red Hat OpenShift Container Platform 3.4nodejsOut of support scope
Red Hat OpenShift Container Platform 3.5nodejsOut of support scope
Red Hat OpenShift Container Platform 3.6nodejsOut of support scope
Red Hat OpenShift Container Platform 3.7nodejsOut of support scope
Red Hat OpenShift Container Platform 3.9nodejsFix deferred
Red Hat Software Collectionsrh-nodejs10-nodejsNot affected
Red Hat Software Collectionsrh-nodejs4-nodejsWill not fix
Red Hat Software Collectionsrh-nodejs6-nodejsWill not fix
Red Hat Software Collectionsrh-nodejs8-nodejsNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2018-12120.

Attack patterns (CAPEC)

  • CAPEC-383 Harvesting Information via API Event Monitoring Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-829 (13).

References

Check your stackJSON