Ubiquity Malware

There was a post on the UBNT forums where a user wanted Ubiquiti to pay for all their time to fix this issue on their endpoints because this wasn't in any of the release notes. Some other user went off on them and stated that this vulnerability is about a year old and it's not Ubiquiti's fault that you aren't keeping your endpoints patched with security updates. I got a kick out of that. That's like running Windows XP and blaming MS for getting infected. Also, the release notes did note that this issue was, in fact a problem long before now. I'll see if I can find the thread.

https://community.ubnt.com/t5/airMAX-General-Discussion/Virus-attack-URGENT-UBNT/td-p/1562940
 
Last edited:
LOL!!! Thanks. If it's a year or more old I'd bet they've been hearing from some lawyers then. In the case of updates for devices like this I'm always on top of them. Unlike OS updates, where there are surprises everywhere, updating these things are very solid. Hope you find the thread, sounds like it will be a good read.
 
I don't really know the Ubiquiti product lines, but are any of these products designed to be exposed to the world (e.g. routers or other edge devices) or are they mostly supposed to be internal equipment?
 
Markverhyden said:
If it's a year or more old I'd bet they've been hearing from some lawyers then.
Click to expand...

It's not so much that the vulnerability is a year old as that it was patched in a security update released in July, 2015 after it was reported privately to them via their bug bounty program. They even backported the fix to an earlier version of the firmware (5.5.11 vs 5.6.2) because some people weren't ready to jump from 5.5 to 5.6.
 
Here's another good post from that thread:

TCC wrote:
After having spent a half $1 million over the last many years with ubiquiti and what do I get when I need some assistance?some joker on the chat line that says sorry we can't help you please refer to this link! WTF ubiquiti you should be ashamed of yourselves for putting us in this position. I'll be sending you a bill. It will be for thousands of dollars spent resolving this ridiculous event.
  1. No one cares how much you spent with Ubiquiti. Someone else spent more.
  2. It's not like you weren't made aware of the potential problem plenty inadvance.
  3. Clean up after your network management mistakes and learn for next time.
 

fencepost said:
It's not so much that the vulnerability is a year old as that it was patched in a security update released in July, 2015 after it was reported privately to them via their bug bounty program. They even backported the fix to an earlier version of the firmware (5.5.11 vs 5.6.2) because some people weren't ready to jump from 5.5 to 5.6.
Click to expand...
Yeah, I meant to say this was fixed about a year ago and just because you didn't apply the security updates does not make this Ubiquiti's fault. You know the "lack of planning on your part doesn't make an emergency on mine" type of deal.
 
Who is deploying these with their http/https interfaces exposed to the internet? You probably deserve to be infected. In my dealings with Ubiquiti "installers" over the years, I can guarantee not a one of them would know what NAT was if it slapped them in the face. Simply, while this is alarming from a technical stand-point, I find it hard to believe many of these devices are left exposed.
 
Yeah I saw that notification from Ubiquiti, read the details...and chuckled. As stated several times above.."Who puts their wireless APs on public IPs exposed to the internet? Or forwards 443 to them?"

It's sad that the lawyers forced them to release that notice, when it's standard network best practice to keep public facing devices updated to help mitigate exploits.
Just like with EVERY OTHER BRAND of network equipment.
 
I know they would not be the same people who would stick a fresh, hot paper/styrofoam cup of coffee between their legs while driving around in their car.....
 
That does remind me of cruel jokes done at LAN parties.....going back to the Win9X days...it was common for some peeps to do a full share of their entire C drive. And unfortunately that bad practice continued in the Win2K and XP days.

oh boy...bad stuff happened.... ;7
 
You must log in or register to reply here.

Similar threads

glennd
Introducing UniFi LED
Replies
4
Views
994
nerd2u
nerd2u
YeOldeStonecat
Quick blog article from the guy that started Ubiquiti
Replies
8
Views
993
Tech Savvy
Tech Savvy
YeOldeStonecat
Ubiquiti releases new ultra small form factor gigabit routers, EdgeRouterX
Replies
7
Views
1K
Markverhyden
Markverhyden
MM PC Solutions
Microsoft offering free TechNet Plus subscription
2
Replies
29
Views
5K
purple_minion
P
Back
Top