QUOTE(andrew9292 @ May 30 2010, 12:29 AM)
Probably why they put that up ;p
Okay, good job for TS as he found out this major security risk considering the number of IT grads and professionals these days are out there...
But posting this here is actually publicity to this loophole.
Only those who came to LYN would find out about this and if they are tech savvy enough, they will know how to get around it to minimize the exposure risk as much as possible.
But again, if someone with unholy intention stumbles upon this, it could mean disaster for those unaware and incapable to prevent it...
I would like to ask TS, now that you have found out and posted it to public, what is your next step? Will you report to relevant authorities?
Otherwise the purpose of this thread will be:
1. Publicize a major loophole in UniFi
2. Giving knowledgeable users the chance to avoid the risk, a really small amount of people in LYN.
3. Exposing a mass mount of UniFi-ers to exploits...
So, just be aware of that. I'm no IT expert with any qualification btw. TS, u're doing the right thing, salute! but there is still a loophole in what you are doing

haha
I spent some time thinking about it. There were a lot of things I took into consideration..
In the end I feel as though its my duty to notify the community about these things. It's not my job to fix it, it's TM's job. If they had planned this through and allowed for open access to their hardware in the first place, we wouldn't be in this mess. Why even bother putting the PPPoE server on VLAN 500? Why didn't they just not use any tagging in the first place? It wouldn't make a difference to them but it would give their customers tons of new options and better security. It's because they chose to follow this closed method that all these flaws are starting to come out. If I'm not mistaken, I even mentioned on LYN in the first week I got Unifi that there's a telnet daemon on the set top box and SSH daemon on the DIR-615.. and it would only be a matter of time till someone found the keys.
It took me less than 2 months to completely break the system (from the users end). Sure, I have a lot of experience in this field but I'm just a final year network security student and I did this in my free time because I was trying to help people @ LYN. 2 months in however, all these flaws in their system start to get noticed. You hand this system to a professional blackhat hacker and the entire network is going to go down in a week or so.
I know sending a message to LYN isn't exactly sending a message to every Unifi user in Malaysia, there are tons of users (even TM staff) which have their routers exposed at the moment. Eventually however, the word is going to get out. They will either patch their firmware 7.05 and fix it or notify their technicians to not enable these particular features doing install.
The best case scenario I can hope for is that they start doing installs with this secondary admin account so people have full control over the hardware and service they're dishing out RM200+ a month for.And you know, even though this 'fix' blocks WAN access..
I believe the SSH daemon is still running on the LAN subnet. It cannot be turned off without using the secondary admin account and logging into the SSH server using PuTTy or something. Those people who are running Unifi hotspots (aka kopitiam shops) are still vulnerable.
I know some of you are going to hate me with the typical 'why did you let others know' mentality.. but lets be honest here, just because I don't tell you something it doesn't magically make it non-existent okay? I'm not going to release the account details yet and I'm hoping those of you who have also found this account wont either.. and I know that's not a perfect solution but its better than closing both your eyes and pretending there is no problem with the system.