The published exploit chain was part of a proof-of-concept attack that the first researcher included when submitting a bug report to Plex. The complex code completes a series of steps, including performing an unauthenticated SSRF, a loopback pivot, a security token theft, a payload delivery, and finally the execution of the payload. The bug finder said he used AI “heavily” to develop the exploit chain. Steps included:
- Recon: Break the system into logical components. Map every path from user input to a dangerous sink.
- Hunt: Focused vulnerability hunt per component.
- Verify: Spawn a separate agent to try to disprove each finding. If it can’t refute the bug, it’s likely real.
- Chain: Find
“This was not a matter of telling the LLM ‘go hack Plex,’” the researcher wrote. “It was hours of iterative work, dead ends, and reprioritization. All of the judgment calls on what to look for and what to prioritize were mine. The LLM speeds this process up significantly, allowing me to stay at a higher level and simply guide the process.”
Plex representatives didn’t immediate respond to questions.
Anyone using Plex should ensure it’s running version 1.43.3. The software can be configured to install updates automatically, or users can manually download and install them. Given the active exploitation, outdated versions should be updated immediately. Beyond that, users should devote care to properly securing the media servers. The safest option is to restrict its access to local networks with no exposure to the Internet. This option prevents being able to use many useful features, though. One option when connecting a device to the open Internet is to route traffic through a reverse proxy, instead of using the default port 32400. Users should also use only secure Plex apps. And of course, strong passwords are a must.
