What is the severity of CVE-2018-12120?

CVE-2018-12120 is considered a medium severity vulnerability due to the risk of unauthorized remote access to the debugger.

How do I fix CVE-2018-12120?

To fix CVE-2018-12120, upgrade Node.js to version 6.15.0 or later to ensure the debugger only listens on localhost by default.

Who is affected by CVE-2018-12120?

CVE-2018-12120 affects all versions of Node.js prior to 6.15.0 that have the debugger enabled.

What can happen if CVE-2018-12120 is exploited?

Exploiting CVE-2018-12120 can allow attackers to connect to the debugger and execute arbitrary commands on the Node.js application.

Is there a workaround for CVE-2018-12120?

A temporary workaround for CVE-2018-12120 is to avoid enabling the debugger on production systems or bind the debugger to specific interfaces.

Vulnerability/
CVE-2018-12120

high

8.1

CWE

829 419

28/11/2018

5/8/2024

CVE-2018-12120

First published: Wed Nov 28 2018(Updated: )

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.

Credit: cve-request@iojs.org

Affected Software	Affected Version	How to fix
Langgenius Dify Node.js	>=6.0.0<6.15.0

Remedy

https://nodejs.org/en/blog/vulnerability/november-2018-security-releases/

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-12120?
CVE-2018-12120 is considered a medium severity vulnerability due to the risk of unauthorized remote access to the debugger.
How do I fix CVE-2018-12120?
To fix CVE-2018-12120, upgrade Node.js to version 6.15.0 or later to ensure the debugger only listens on localhost by default.
Who is affected by CVE-2018-12120?
CVE-2018-12120 affects all versions of Node.js prior to 6.15.0 that have the debugger enabled.
What can happen if CVE-2018-12120 is exploited?
Exploiting CVE-2018-12120 can allow attackers to connect to the debugger and execute arbitrary commands on the Node.js application.
Is there a workaround for CVE-2018-12120?
A temporary workaround for CVE-2018-12120 is to avoid enabling the debugger on production systems or bind the debugger to specific interfaces.

agent/references
agent/weakness
agent/type
collector/mitre-cve
source/MITRE
agent/remedy
agent/severity
agent/last-modified-date
agent/author
agent/first-publish-date
agent/description
agent/event
agent/source
agent/softwarecombine
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/nodejs
canonical/langgenius dify node.js
version/langgenius dify node.js/6.0.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.