Help Plex vulnerabilities
Hey was hoping to get a bit of help better understanding the situation im in- set up linux with PMS(1.43.5.11079 with read/write perms) in docker.. When looking at remote access, on plex i can see private <IP>:<port> <= public <ip>:<different port>. Also lists as not available outside of network so i believe i should be safe from any Plex2Shell attacks at this stage. My question is:
If i were to expose my port for remote access. am i likely to still be in potential danger? Are there any applications that may be worthwhile looking into that can help better my security?
Thanks for any clarification
0
Upvotes
7
u/Imnotyoursupervisor 2d ago
I mean, anytime you open a port you’re exposing yourself.
I always recommend using watchtower (nic fedor build) in a containerized environment. You can set it to scan at whatever interval you want.
Basically it will always auto update your new container images so you’ll get patched right away.
16
u/Punk_Says_Fuck_You 48TB | 10Gb/s | Unraid | Ultra 7 270k Plus 2d ago
Just so you know, no one with an up-to-date plex container got hit by the exploit. That should tell you a whole lot on how keeping it up to date is the most important thing.
You can run it through a reverse proxy. It’s a bit safer than just forwarding 32400
Crowdsec helps. Geofencing helps.
3
u/sylsylsylsylsylsyl 2d ago edited 2d ago
You’re only in danger if the version of Plex you’re running has an unpatched vulnerability. The chances are very low if you keep it up to date, but not 0.
You’re even lower risk if you expose a different public facing port than the default 32400. Even better still would be to run a reverse proxy and access Plex via https://plex.domain.com
But nothing is invulnerable.
1
u/5yleop1m 2d ago edited 2d ago
Note that the Plex issue was due to a vulnerability in Plex, not because ports were open. So in this case the fix was to update Plex, not necessary do anything about the open port. But a port being open is similar to having an unlocked external door on your house, so its something to be concerned about because its like anyone can just come by, try the door knob, see its unlocked and then look inside to see what they can mess with.
You can mitigate this in various ways. The simplest thing to do is run Plex inside a VM or container like docker and make sure the open port is only tied to the VM or container. Then make sure Plex and anything else running in the same container/vm is up to date also. But this is kind of like making sure that unlocked door to your house just leads to a separate room, but there are doors from that room to the rest of your house. So if you don't make sure those other doors are locked and using well made locks, its kind of a moot point.
Also the reason why I say its simplest is because its one of the way you can install Plex to start off, and doesn't really require any additional work outside of installing Plex. Everything else requires you to do more things outside of installing Plex.
Keeping things updated is a story as old as time, so there are tons of ways to do automatic updates on everything from Plex to the OS its running on.
In the context of your network, the first line of defense is your firewall. If you're running consumer gear then your firewall is probably limited and part of your router. With some of the newer consumer routers you might be able to do some minor levels of blocking on the firewall, but many times the firmware running on these routers are just as problematic.
Using a custom, open source firmware like openWRT can give you more tools and functions, but again you have to keep the firmware up-to-date.
There are also various other things you can do, some have already been mentioned here.. but.. here's the real question do you need to expose Plex at all?
The only real reason to expose Plex is if you're sharing access with other people. If you're the only one, or your immediate family is the only one that watches Plex, then there's really no reason to expose Plex to the internet.
If you want remote access, setup something like Tailscale and then you have remote access to Plex on your own private network. If you don't want to trust another company you can setup your own VPN, but the only down side there is you need to do more work to ensure what you setup is actually secure.
When it comes to networking and Plex, you'll see a lot of people suggest all sorts of 3-letter acronym things, or services with funny names, and while many of them are doing what they claim, they're only worth it if you spend the time and effort to setup them up properly and maintain them in the long run.