Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node --debug --debug-host=127.0.0.1 #4242

Closed
rafis opened this issue Dec 11, 2015 · 2 comments
Closed

node --debug --debug-host=127.0.0.1 #4242

rafis opened this issue Dec 11, 2015 · 2 comments
Labels
question Issues that look for answers.

Comments

@rafis
Copy link

rafis commented Dec 11, 2015

I have just discovered that my VPS exposes all my private propietary code to the Internet :) I'm not even sure if hacker can eval some really bad code like require('fs').readdirSync('/etc') when I'm debugging.
How to limit interface on which debug is listening?
Have anybody developed nodejs code snifferer or VPS backdoorer (sometimes I'm running sudo mc and can forget that)? It will not take too long to scan the Internet with zmap for first machine with port 5858 open and iterate in such way over them in a loop.
Is vulnerability discovered by Quihoo 360 researcher Guang Gong only related to Android+Chrome and not to V8 in general?

@bnoordhuis bnoordhuis added question Issues that look for answers. debugger labels Dec 11, 2015
@bnoordhuis
Copy link
Member

How to limit interface on which debug is listening?

I have a PR that I need to revisit that (re)implements that: #3316

Is vulnerability discovered by Quihoo 360 researcher Guang Gong only related to Android+Chrome and not to V8 in general?

Which vulnerability in particular are you referring to?

@jasnell
Copy link
Member

jasnell commented Mar 22, 2016

Closing given the lack of response. Can reopen if necessary.

@jasnell jasnell closed this as completed Mar 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Issues that look for answers.
Projects
None yet
Development

No branches or pull requests

3 participants