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

  • HumanPerson@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    2
    ·
    6 days ago

    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.

    • schizo@forum.uncomfortable.business
      link
      fedilink
      English
      arrow-up
      6
      ·
      6 days ago

      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.

      • SayCyberOnceMore@feddit.ukOP
        link
        fedilink
        English
        arrow-up
        3
        ·
        6 days ago

        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.