A flaw was found in Node.js versions before 6.15.0. A 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. References: https://nodejs.org/en/blog/vulnerability/november-2018-security-releases/
Created nodejs tracking bugs for this issue: Affects: epel-all [bug 1661018] Affects: fedora-all [bug 1661017]
Reducing the severity of the flaw down to Medium : Red Hat Enterprise Linux comes with a firewall enabled by default, blocking this port on untrusted interfaces.
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
Upstream fix: https://github.com/nodejs/node/commit/a9791c90
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.
The current nodejs releaase in RHOAR 10 rhoar-nodejs10-10.16.0-1.el7 has been rebased and includes these fixes. Hence not affected
In reply to comment #12: > The current nodejs releaase in RHOAR 10 rhoar-nodejs10-10.16.0-1.el7 has > been rebased and includes these fixes. Hence not affected nodejs 10 was never affected.
I am going to close this as nodejs v6.x is long out of support.