Comment on Improve very slow library scans on Jellyfin 10.11 / 12 on spinning media
blue_morpho@lemmy.world@lemmy.world 3 weeks agoYou obviously don’t use Plex to claim it doesn’t need an open port for remote access:
…plex.tv/…/201543147-what-network-ports-do-i-need…
I already posted a CVE that allowed hackers access to a Plex server running at home.
GoatSynagogue@lemmy.world 3 weeks ago
OK so you don’t understand networking, don’t understand how Plex works, don’t understand how that CVE does nothing of the sort, and have poor reading comprehension skills.
I’d hate to be your poor server.
blue_morpho@lemmy.world@lemmy.world 3 weeks ago
I quoted Plex documentation where it explains in detail that you need port 32400 OPEN for remote access. support.plex.tv/…/200289506-remote-access/
I linked the CVE but here is the plain language version because you didn’t read what I linked:
howtogeek.com/over-300k-plex-servers-are-still-vu…
"The flaw has been assigned a CVSS score of 10.0, the highest possible level of severity. This score indicates that the vulnerability can be exploited remotely over the internet, is easy to execute, and requires no authentication or interaction from the server’s owner. A successful attack could result in a total loss of confidentiality, integrity, and availability. An attacker could access, modify, or delete a user’s private media files, or even disable the entire Plex server. "
What the fuck is wrong with you?
GoatSynagogue@lemmy.world 3 weeks ago
You clearly don’t understand how Plex and port forwarding work if you think that is in any way the same as opening a port to the Internet for everyone to hit jellyfin with zero security on it.
The CVE has been exploited zero times that we know of, and at worst they can delete your media files and Plex server. It’s never been reported of happening, and we have no idea how difficult it is to do - but because it hasn’t happened, it’s probably extremely hard and requires a chain of very unlikely things to have happened first.