And you think if Jellyfin were a comparable size, there wouldn’t be just as many or more?
Comment on Plex’s crackdown on free remote streaming access starts this week - Ars Technica
tyler@programming.dev 9 hours agoAside from most of those being “potential issues”, which weren’t proven, the rest are GETs of things that do not need to be secret, things like album art and list of installed plugins. Besides the one plugin issue, which was an actual security issue, which was fixed over a year and a half ago. github.com/jellyfin/jellyfin/pull/11436
Contrast that with Plex which has numerous high severity CVEs that include things like remote code execution, directory traversal, and more.
MaggiWuerze@feddit.org 5 hours ago
fartsparkles@lemmy.world 3 hours ago
You’re aware those CVEs are only relevant for ancient versions of Plex and were fixed long ago?
Cocodapuf@lemmy.world 3 hours ago
Yeah, as you said, that’s a pretty serious security issue. That’s a data leak that explicitly lays out the shape of your attack surface. It tells the attacker exactly what additional software your server is running and if any of it includes known vulnerabilities, the attacker now knows how to gain access.