Comment on Jellyfin over the internet
Vanilla_PuddinFudge@infosec.pub 2 weeks agoHere, since you can’t use a search engine: www.cvedetails.com/…/Jellyfin-Jellyfin.html
More, because I’ve been around this lap before, you’ll ask for more and not believe that one, here’s another: www.cvedetails.com/…/Jellyfin-Jellyfin.html
offspec@lemmy.world 2 weeks ago
I don’t want to be an asshole but after checking a couple of those out they all appear to be post-authorization vulnerabilities? Like sure if you’re just passing out credentials to your jellyfin instance someone could use the device log upload to wreck your container, but shouldn’t most people be more worried about vulnerabilities that have surface for unauthorized attackers?
ryan_harg@discuss.tchncs.de 2 weeks ago
plus, most of the mentioned cve’s state “versions before …”. Exposing a service to the internet always has a risk to it, keeping your service up-to-date is mandatory. Running behind a vpn can protect you, sure. But it also has to be practical. I don’t get why Jellyfin especially gets this kind of slaming. You’ll find similar records for any other software.
Vanilla_PuddinFudge@infosec.pub 2 weeks ago
A while back there was a situation where outsiders could get the name of the contents of your Jellyfin server, which would incriminate anyone. I believe it’s patched now, but I don’t think Jellyfin is winning any security awards. It’s a selfhosted media server. I have no frame of reference for knowing whether or not any of my information was overkill and I’m sure there are even some out there that would say I didn’t go far enough, even.