Just stumbled across this (overly dramatic?) article and thought I’d just post it here…
It’s more to act as a reminder that if you’ve got a NAS that is serving content to the interwebs, then make sure it’s behind a proxy of some kind to prevent weaknesses (ie in the management Web UI) being exposed.
Obvz, this article is pointing to Zyxel, but it could be your DIY home-built NAS with Cockpit: CVE-2024-2947 - just an example, not bashing that project at all.
I’ve used Squid and HAProxy over the years (mostly on my pfSense box) - but I’d be interested to know if there’s other options that I’ve not heard of
You must log in or register to comment.
I had one of those NAS (NSA320). Even when they were new and suppoted they were using some ancient custom version of linux with ancient packages. It would be insane to expose them on the internet.
Yeah, I actually finally got rid of mine a year ago, but it never was allowed to access the Internet. Also didn’t support smbv3 when those huge issues came out so has to use custom package sources to get updates. Never buying something unless it can have open source firmware flashed any time for my NAS hardware. Using TrueNAS now on slightly old custom built PC I upgraded from.
