Your Linux-based home router could succumb to a new Telnet worm, Remaiten
|
|
|
Comments (4)
After the TP-Link thing...
I currently have a Buffalo router running DD-WRT. I really only use it as a wireless access point, the routing functions are all turned off except for DHCP forwarding. Once this router dies, I will be building my own from old PCs -- similar to this prior newswire posting:
http://lxer.com/module/newswire/ext_link.php?rid=227712
I currently have a Buffalo router running DD-WRT. I really only use it as a wireless access point, the routing functions are all turned off except for DHCP forwarding. Once this router dies, I will be building my own from old PCs -- similar to this prior newswire posting:
http://lxer.com/module/newswire/ext_link.php?rid=227712
@jsusanka
> have a netgear WNR3500L and it shipped with the telnet port open on both the wan side and lan side.
From a bit of initial research, it turns out that partially free open source Linux-based routr firmwares Tomato and OpenWRT could very well support the WNR3500L(V1?, v?) Whichever version it is, BOTH WNR3500L devices have Broadcom BCM4718xxx chips, so I don't see how the Linux/Remaiten worm could as easily wreck these non-ARM and non-MIPS devices.
Of course, once one of these open source Linux-based routr firmwares is successfuly installed, you'd still have to know how to COMPLETELY disable telnet, and actually DO this ASAP to avaoid the problem.
2c
> have a netgear WNR3500L and it shipped with the telnet port open on both the wan side and lan side.
From a bit of initial research, it turns out that partially free open source Linux-based routr firmwares Tomato and OpenWRT could very well support the WNR3500L(V1?, v?) Whichever version it is, BOTH WNR3500L devices have Broadcom BCM4718xxx chips, so I don't see how the Linux/Remaiten worm could as easily wreck these non-ARM and non-MIPS devices.
Of course, once one of these open source Linux-based routr firmwares is successfuly installed, you'd still have to know how to COMPLETELY disable telnet, and actually DO this ASAP to avaoid the problem.
2c
root access and netstat are your friends:
Check open ports:
And make sure you find a line that looks like this:
Check open ports:
- Enable ssh and copy your ssh public key over to the DD-WRT router, don't use passwords -- use keys and only keys for ssh
- Login with ssh key
#netstat -l
#nvram show |grep telnet telnetd_enable=0Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post

called support immediately and they denied that their router ships this way.
about a week later they upgraded the firmware and port 23 isn't open any more.
how about the manufacturers use some common sense