Synology Security Advisory

(synology.com)

57 points | by choult 1 hour ago

8 comments

  • SchemaLoad 44 minutes ago
    You just can't have a NAS exposed to the internet. Put it behind a VPN or you will have it hacked.
    • landgenoot 31 minutes ago
      VPNs are bad from a UX perspective.

      I think the answer is mTLS.

      Unfortunately, Synology apps don't support it.

      • 8fingerlouie 12 minutes ago
        Compared to faffing around with certificates, Wireguard or if you're lazy, Tailscale, is a breeze to setup.

        Generate the config, one per client, setup the client to only route specific RFC1918 networks and disable on well known wifi networks, and that's it. It literally works for years without any maintenance.

        Tailscale is easier (presumably), but also puts a corporate entity between you and your data.

      • LoganDark 19 minutes ago
        mTLS is the one that requires a client certificate. right? It can be quite difficult to get protocols other than HTTPS to behave well with that, mostly because the application has to worry about it and many don't bother.
    • shantara 38 minutes ago
      I wouldn't expose anything from a home network except for a single Wireguard port.
  • aquariusDue 6 minutes ago
    I know this is not relevant to the topic at hand but tangentially related:

    Does anyone know of any UGREEN UGOS alternatives? I don't mind the terminal but friends prefer a web GUI and for some mundane stuff I too have started to (begrudgingly) prefer it.

  • 6thbit 51 minutes ago
    Tied to this weakness:

      >  CWE-88: Improper Neutralization of Argument Delimiters in a Command 
    
    So, they were building shell commands from some kind of user input in the OAuth API?
    • pixl97 4 minutes ago
      These smaller consumer devices always have the worst security practices.
    • formerly_proven 43 minutes ago

          system("getent passwd " . $_GET['user']);
    • no-dr-onboard 4 minutes ago
      Are surprised? Direct interpolation leading to command injection has been in the owasp ten for over a decade now.

      Prepare and parameterize statements you guys.

  • dj68k 44 minutes ago
    The oldest one I have still serving data at home is an 1813+ running DSM 7.1.1-42962 Update 9. It's inside my network and just does SMB1 and AFP for my retro computer collection and serves as a dumping ground for security camera footage. Really curious when Syno's going to finally cut this thing off from updates since it's been years since 7.2 came out and it didn't get it.

    I just recently took a 415+ off the internet (it had Photo Station and Apache only exposed to the outside). I did the "resistor mod" on its JTAG connector to save its Atom from literally frying itself and it's also still working fine. As usual, the hardware far outlives the software.

    • beart 2 minutes ago
      I never even moved to 7, but I seem to recall a security update not super long ago.
  • NathanKP 47 minutes ago
    Mitigation for now is to go to Package Center -> Installed -> OAuth Service and stop it.
  • bix6 18 minutes ago
    Feels like the have a new security update every week lately…
    • pixl97 3 minutes ago
      Which is probably too slow for the number of bad security practices in these things.
  • otekengineering 38 minutes ago
    i'm glad claude helped me install debian on my DS918 and DS920 a few weeks ago
  • lousken 56 minutes ago
    can we like ban friday from releasing patches? it is called read only for a reason