Synology Security Advisory

A newly disclosed critical vulnerability in Synology’s OAuth Service—apparently stemming from unsafe shell command construction—has renewed scrutiny of the security of consumer NAS devices. Commenters emphasize that exposing a NAS directly to the internet is risky and recommend mitigations such as uninstalling the affected package, relying on VPNs like WireGuard or Tailscale, or adding reverse proxies and strict access controls. The exchange also highlights broader concerns: Synology’s aging software stack, the usability trade‑offs of VPNs and mTLS, and growing “patch fatigue” among people self‑hosting services at home.

Nature of the vulnerability and mitigations

  • Advisory tied to command injection via improper neutralization of arguments (CWE-88) in the OAuth Service.
  • Commenters infer shell commands are built from user input in the OAuth API.
  • Recommended mitigation: stop or uninstall the OAuth Service package via Package Center, especially on older units where fixes are “ongoing.”
  • Several note OAuth appears installed by default, even if unused.

Debate over patch timing and disclosure

  • Some argue vendors should avoid releasing planned patches on Fridays to reduce weekend fire drills.
  • Others counter that once active exploitation is seen, rapid release is necessary regardless of day.
  • A few say announcing a critical bug before a patch is available is unsettling but acknowledge mitigations exist.

Exposing NAS devices to the internet

  • Strong recurring theme: do not directly expose home NAS services; instead, put them behind VPNs or at least reverse proxies with TLS and tools like fail2ban.
  • Several mention active compromises of internet-facing Synology devices and communities filled with “I was hacked” reports.
  • Some still want public access for photos, media, or backups and accept the residual risk with hardening and backups.

VPN vs mTLS and remote-access UX

  • Many favor WireGuard or Tailscale as simpler, broadly applicable approaches; some mention split tunneling and near-zero maintenance once set up.
  • mTLS is seen as powerful but harder to deploy, especially for non-HTTP protocols and consumer apps; often misused as both authn and authz.
  • UX complaints focus on needing VPNs for phones (e.g., automatic photo backup) and battery concerns; others say modern VPNs are lightweight.

Synology software quality and maintenance

  • Criticism that Synology uses very old kernels, filesystems, and userland components, with heavy backporting and custom forks.
  • Concerns this legacy stack and slow library updates increase long-term risk, especially as more vulnerabilities are discovered.
  • Counterpoint: compared to DIY setups, Synology is still relatively hardened and sometimes patches core services quickly.

Self‑hosting risk, compromises, and fatigue

  • Multiple anecdotes: compromised NAS in a DMZ, waves of recent break-ins, and users deciding to shut down or de-expose services.
  • Several express “patching fatigue” and question whether self‑hosting on consumer NAS remains worth the ongoing security burden.

Alternatives and workarounds

  • Some run Debian or other OSes on Synology hardware or migrate to mini PCs/other NAS platforms.
  • Suggestions include Tailscale packages for Synology, containers behind reverse proxies, and offloading Plex/media servers to separate machines.