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.
As someone who isn’t a fan of e-waste, I really hate these little “appliance” type NASes. Companies abandon them while they’re still perfectly usable and meeting someone’s needs, and tell you oh sorry, I guess you should buy a new one and throw your current one away. (Which, annoyingly, the article also does.)
I agree, though I wouldn’t blame the article. If it is insecure, you shouldn’t be using it unless it is set up to allow you to run a real os on it.
I mean I’m not blaming anyone other than the manufacturers who make things and then arbitrarily decide to stop supporting them while they’re still perfectly usable, leaving basically no choice other than trashing and buying a new one.
Agreed.
If the hardware’s standard, then it’s possible for people (us) to keep these things out of the ground / incinerator for a few more years, but if it’s custom / proprietary stuff, then that’s just terrible.
Totally agree! Also, at work we have some Synology and their web UI is soooo slow that it’s almost unusable