Comment on What's the security situation when opening a jellyfin server up for casting?

• irmadlad@lemmy.world ⁨9⁩ ⁨hours⁩ ago

  my homeserver is compromised and has beenpart of a bitcoin mining farm for years

  The very first Linux server I deployed on a VPS was hacked almost immediately because of my ignorance. The bot gained entrance, and they supplanted a miner rig. Now, on a tiny VPS, it’s pretty easy to tell if you’re running a coin miner because all of the resources will be pegged. However, I got to thinking, on a corporate server, if they did manage to do this, it would almost be undetectable until someone started reviewing logs.

  source
• GraveyardOrbit@lemmy.zip ⁨13⁩ ⁨hours⁩ ago

  There are probably thousands of zero days out there in the hands of hacking organizations and nation state level actors. Exposing anything to the internet that doesn’t absolutely have to be is an invitation for the world to join your network and access all your files, if you’re okay with that risk then proceed

  source

  • diegantobass@lemmy.world ⁨11⁩ ⁨hours⁩ ago

    Aren’t zero day very specific? Or maybe it’s become a very generic term.

    Anyway, I am under the impression that either it’s suddenly very simple to hack into EVERYONE because someone zero dayed the wireguard protocol and there a major flow in it, it’s a shitshow, for all, for some, just me or nobody, whatever. Or it’s a very targeted attack on me personaly, and that’s a whole other story and the means to protect my pictures of my cats and my cool public domain movies collection are different (think social engineering). Also port 22 being bombarded by brute force attempts so don’t choose a password that’s 6 letters thanks.

    I KNOW I am missing many things, but still, I don’t get it.

    source

    • GraveyardOrbit@lemmy.zip ⁨11⁩ ⁨hours⁩ ago

      In all likelihood a targeted attack would never come your way but when hosting community made software like immich for example there is a very large attack surface with no security researchers poking at it to find vulnerabilities of which there are likely many. Exposing something like nginx or Wireguard is likely very safe if properly secured because it’s been battle hardened over the decades with millions of eyes on it trying to break it at every turn. So what matters most is your threat model, what you’re deploying, and how you’re deploying it.

      Fail2ban will protect you from brute force but just this week there was a maximum risk vulnerability found in react allowing remote code execution, this is one of the most used frameworks on the web developed by some of the most talented engineers in tech over a decade ago and it still has issues that could lead to malicious takeover of your system.

      source

      • diegantobass@lemmy.world ⁨11⁩ ⁨hours⁩ ago

        React2Shell is exactly the shitshow situation yes. Suddenly we are all at risk. But in this case, I’m sorry to say that my cats’ pictures are worthless.

        Your point on nginx/wireguard makes me think that it might be better to htaccess through a reverse proxy than relying on a built in login system. For exemple, I should deactivate jellyfin’s login and put it behind an htaccess at the proxy’s level. Is that completely dumb?

        Anyway, I clearly need to research “threat models” and cyber/infosec more. Thank you very much!

        source