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

Netgear R6300 and WN2500RP - connect refused #15

Closed
hossman opened this issue Jan 3, 2014 · 4 comments
Closed

Netgear R6300 and WN2500RP - connect refused #15

hossman opened this issue Jan 3, 2014 · 4 comments

Comments

@hossman
Copy link

hossman commented Jan 3, 2014

"probably not vulnerable (error: [Errno 111] Connection refused)" for both of the following devices...

Hardware Version R6300
Firmware Version V1.0.2.68_1.0.49

Hardware Version WN2500RP
Firmware Version V1.0.0.30_1.0.58

@elvanderb
Copy link
Owner

thank you, updated :)

@depau
Copy link

depau commented May 14, 2014

False. Netgear R6300 has a backdoor that provides access to a root busybox shell through telnet.
You actually have to log in, but the username and password are not changeable through the GUI, and once you open the backdoor it stays open until you reboot it. Once you're in you can change the password though and close the door (if I remember correctly it was the "nvram" command, or something similar).

More details here: http://wiki.openwrt.org/toh/netgear/telnet.console#python-alternative.to.the.windows.version

See pull request #102.

depau pushed a commit to depau-forks/TCP-32764 that referenced this issue May 14, 2014
@elvanderb
Copy link
Owner

This repo is dedicated to the TCP/32764 backdoor and this router is not vulnerable to this backdoor.
I'm aware of the telnetenable vulnerability / backdoor but it's not the same :)

@depau
Copy link

depau commented May 17, 2014

Oh ok sorry, my bad!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants