Hi everyone.

Glad to post on Lemmy for the first time.

I have an ubuntu that runs a whole jellyfin/arr/torrent docker stack and used to use it as my main work and backup server.

I decided it would be best practice to host my work data on a separate machine in case anything would ever go south virus wise.

I only download and host movies, shows and music there and its all being played through the jellyfin docker.

Am I being overly cautious? Can I even get a virus like that? Has that ever happened?

Or should I continue to separate work and entertainment?

More details on my setup: i3 12100 NVMe 500 GB hosting OS and docker files (including jellyfin cache for snappy access) 5x4TB HDD mergerfs and snapraid

Ubuntu 22 LTS Tailscale Mullvad

  • Reborn2966@feddit.itEnglish
    2·
    1 year ago

    interesting, even if they got access to the plex service, how they could have escaped the plex docker container?

    i run pretty much the same stack as OP, but also run immich and paperless. i very much care if someone else have a way to access those…

    • SmashingSquid@notyour.rodeoEnglish
      4·
      1 year ago

      They weren’t using docker and the Plex software was multiple years out of data:

      https://thehackernews.com/2023/03/lastpass-hack-engineers-failure-to.html

      The shortcoming, which was discovered and reported to Plex by Tenable in March 2020, was addressed by Plex in version 1.19.3.2764 released on May 7, 2020. The current version of Plex Media Server is 1.31.1.6733.

      “Unfortunately, the LastPass employee never upgraded their software to activate the patch,” Plex said in a statement. “For reference, the version that addressed this exploit was roughly 75 versions ago.”

    • ramielrowe@lemmy.worldEnglish
      3·
      1 year ago

      In the LastPass case, I believe it was a native Plex install with a remote code execution vulnerability. But still, even in a Linux container environment, I would not trust them for security isolation. Ultimately, they all share the same kernel. One misconfiguration on the container or an errant privilege escalation exploit and you’re in.

    • Bezerker03@lemmy.bezzie.worldEnglish
      3·
      1 year ago

      It wasnt containerized sadly but remember in a container you still share (albeit split by cgroups) kernel space and the kernel. Only userland is isolated.

      So kernel level sploits are still a concern. Wasn’t the case here but still.