Remote Plex Server

Jun 01, 2015 If I understand your situation, both sonarr and your download client are running locally, and you have a remote file server that happens to run Plex as well. So, depending on your OS, you should tell sonarr to put files in remoteserver path to series. Plex Media Server’s remote access function is usually so smooth to set up that it’s practically magic. But if you’re having trouble accessing your movies from afar, we’re here to help. If you primarily use Plex Media Server for watching content on your local network (like streaming your favorite shows to your HDTV or smartphone), you. Mar 27, 2019 Remote Access Enable access to your Plex Media Server from outside your local network so that you can reach it when away from home or for sharing content with family or close, personal friends. You can do this under Settings Server Remote Access in Plex Web App. Related Page: Plex Web App. Jul 14, 2016 While logged into your Plex Media Server’s web control panel, select the Settings icon from the upper right toolbar. Within the Settings menu select, the “Server” tab. Then, from the left hand navigation pane, select “Remote Access”.

Plex Media Server systems are actively being abused by DDoS-for-hire services as a UDP reflection/amplification vector in Distributed Denial of Service (DDoS) attacks.

Plex Media Server provides users with a streaming system compatible with the Windows, macOS, Linux, and FreeBSD platforms, as well as network-attached storage (NAS) devices, Docker containers, and more.

Connect

Netscout says that amplified PMSSDP DDoS attacks observed since November 2020 have been abusing UDP/32414 SSDP HTTP/U responses from exposed broadband Internet access routers and redirected towards attackers' targets.

This junk traffic reflected onto victims' servers is sourced from Simple Service Discovery Protocol (SSDP) probes sent by Plex through the G’Day Mate (GDM) protocol for local network service discovery.

Remote Plex Server

'The total number of attacks from Jan 1, 2020, to present day, clocked in at approximately 5,700 (compared to the more than 11 million attacks in total we saw during the same time frame),' Richard Hummel, Manager of Threat Intelligence at Netscout told BleepingComputer in an email interview.

'We’ve seen its use as far back as November when activity ramped up, but most of the time, we see its use is in multi-vector attacks rather than as a primary vector, which can result in some uncertainty in finding an exact day it began to be used,' Hummel said when asked of the first time PMSSDP was observed as a DDoS attack amplification vector.

Abused in single and multi-vector DDoS attacks

Attacks abusing this UDP reflection/amplification attack vector by targeting PMSSDP reflectors/amplifiers on the UDP/32414 port have an amplification ratio of ~4.68:1 and peak at ~3 Gbps.

Plex

However, as Netscout said, 'multi-vector (2–10 vectors) and omni-vector (11 or more vectors) attacks incorporating PMSSDP range from the low tens of Gbps up to 218 Gbps.'

Attackers can exploit roughly 27,000 exposed devices running Plex Media Server to amplify and reflect DDoS traffic onto their targets systems.

'It should be noted that a single-vector PMSSDP reflection/amplification attack of ~2 Gbps – ~3 Gbps in size is often sufficient to have a significant negative impact on the availability of targeted networks/servers/services,' Netscout added.

'The incidence of both single-vector and multi-/omni-vector reflection/amplification attacks leveraging PMSSDP has increased significantly since November of 2020, indicating its perceived utility to attackers.'

Added to booter services' arsenal

As it regularly happens with newer DDoS attack vectors, PMSSDP has also been weaponized and is now actively used by booter/stresser DDoS-for-hire services.

These platforms are regularly used by pranksters or threat actors without the skills or time to invest in establishing their own DDoS attack infrastructure.

Booters' services are rented to launch large-scale DDoS attacks targeting servers or sites to trigger a denial of service that usually brings them down or disrupts online services.

In January, Baidu Security Lab also reported observing DDoS attacks using Plex as an amplification vector.

According to a subsequent report from ZoomEye, not all Plex Media Server versions can be abused by attackers.

'After testing by Baidu Lab researchers, it was found that the version of Plex used to attack was less than version 1.21, so it can be inferred that version 1.21 of Plex released in late January this year has fixed this problem (although no relevant information has been seen in the plex official Security bulletin),' ZoomEye said.

PMSSDP DDoS mitigation

Broadband Internet access operators with PMSSDP reflectors/amplifiers exposed on their networks by customers can experience 'partial or full interruption of end-customer broadband Internet access, as well as additional service disruption due to access, distribution, aggregation, core, peering, or transit link capacity consumption.'

While filtering all traffic on UDP/32414 can mitigate such attacks, this could also cause legitimate traffic and connections to get blocked.

To mitigate the impact of such attacks, organizations can quarantine end-customer nodes exposed to attacks and/or filter UDP/32414 traffic on abusable nodes.

'Network operators should perform reconnaissance to identify abusable PMSSDP reflectors/amplifiers on their networks and/or the networks of their customers,' Netscout added.

'It is strongly recommended that SSDP be disabled by default on operator-supplied broadband Internet access CPE, and that guidance on disabling SSDP on common CPE makes/models be supplied to end-customers.'

DHS-CISA provides guidance on how to avoid becoming a DDoS victim, how to detect DDoS attacks, as well as on what measures to take while being DDoSed.

Earlier this month, Netscout reported that Windows Remote Desktop Protocol (RDP) servers are now also being abused by DDoS-for-hire services as a reflection/amplification DDoS vector.

In 2019, Netscout also detected DDoS attacks abusing the macOS Apple Remote Management Service (ARMS) as an amplification vector.

ARMS-abusing DDoS attacks observed at the time peaked at 70 Gbps, with an amplification ratio of 35.5:1.

Update: Added statements from Richard Hummel, Manager of Threat Intelligence at Netscout.

Update 2: A Plex spokesperson told BleepingComputer that the company is testing a patch that provides an additional layer of protection to exposed servers.

The researchers who reported on this issue did not provide any prior disclosure, but Plex is now aware of the problem and is actively working on addressing it. This issue appears to be limited to a small number of media server owners who have misconfigured their firewalls by allowing UDP traffic on device-discovery ports from the public internet to reach their servers, and our current understanding is that it does not allow an attacker to compromise any Plex user's device security or privacy. Plex is testing a simple patch that adds an extra layer of protection for those servers that may have been accidentally exposed and will release it shortly.

Related Articles:

My local Plex Media Server running on Arch Linux appears in all of my local devices as a remote server. My local devices are two Raspberry Pi’s running RasPlex, and various wired and wifi computers running the web client. In the web client, my local library shows as “remote” instead of “nearby”:

and on the RasPlex devices I have to set the “remote” bandwidth to “Direct Play” or they request transcoding.

I’ve read through this thread: forums.plex.tv/discussion/219522/local-plex-server-showing-as-remote and double-checked to make sure that plex.direct DNS lookups are working properly. DNS rebinding doesn’t apply to me because I have a “real” home network address (199.85.99.0); I’m not using RFC1918 space. I wonder if that’s the problem? Do the clients check for “device on the same subnet” or are they actually checking for RFC1918 addresses?

Plex Remote Access Setup

Remote Plex Server

Remove Plex Server And Reinstall

I’ve configured Plex Media Server to treat my entire network as “local” using “199.85.99.0/255.255.255.0” but that hasn’t helped.

I’m not sure where to go from here - any assistance would be appreciated!