Elektrine lite

← Feed

@Morgikan@fedia.io

Post #3783133

2026-07-06 01:03 UTC

My biggest concern is pivoting. Specific to Jellyfin, many users are using docker, but do not isolate the user so the daemon is operating as root. With that setup, an attacker could mount the host filesystem to the container and would own the host from that container. Again, for the linux mention, the answer is pivoting. Many machines use Tailscale. If one of those machines were to be compromised using Tailscale's default ACL, they would be able to move laterally through the network without issue. At that point, it would be possible to modify existing nodes (ex. subnet routers, exit nodes, etc) or even add additional rogue nodes. The question of why people care is tricky. Why should you care if your networked printer is using out of date firmware? It likely isn't storing personal information, right? It's a prime target because it's easy, poorly monitored, and opens another door. A lot of infosec is just keeping doors shut so other doors don't get opened.

Replies (1)

  • @hirihit640@sh.itjust.works 2026-07-06 04:44

    With that setup, an attacker could mount the host filesystem to the container and would own the host from that container. Can you elaborate more on this? Assuming an attacker is in the Jellyfin container with full remote code execution, how could they mount the host filesystem?

    Open ##3783131