FortiGate units can be used to remotely manage FortiSwitch units, which is also known as using a FortiSwitch in FortiLink mode. FortiLink defines the management interface and the remote management protocol between the FortiGate and FortiSwitch. Different FortiGate models support remote management for varying numbers of FortiSwitches, as shown. : Plex will do its best to appropriately find and match the content. However, a failure to separate content such as movies and TV shows may result in unexpected or incorrect behavior. In the above example, it is the main folder of each type of content (e.g. /Movies, /Music, /TV Shows ) that you would typically specify as the content location.

For years I was dedicated to my craft of buying records of vinyl, ripping the songs to WAV and Djing alongside my digital collection of music compiled over years from various sources. More recently, I've found myself almost entirely converted to the use of Spotify! However, some of my more obscure soundcloud downloads and vinyl rips are missing from Spotify and so an Azure based Plex server, and the Plex app on my laptop and phone are the perfect solution.

I followed the steps from this video https://youtu.be/ylklaOXz8Fc with a few tweaks along the way.

Virtual Machine

Download Plex Media Server from https://www.plex.tv/media-server-downloads/. In this tutorial, I will use a Linux VM and so downloaded the Linux version of Plex.
Create a resource group. Mine is called 'Plex'.
Inside 'Plex' RG, create a storage account. Mine is called 'alexplex'.
Once created, inside your storage account e.g. 'alexplex', click File shares (under File Service) and add a File share. Mine is called 'plex' and I set the Quota as 1024.
Inside 'Plex' RG, create a virtual network. Mine is called 'plex-vnet'.
Inside 'Plex' RG, create a Linux virtual machine. I used the most recent Ubuntu Server OS image available on the Azure Marketplace. I used a B1s VM and mine is called 'plex-LVM1'.
Link the previously created storage to the VM.
Click on Network Security Group, and add an inbound rule for 1001 port.
Validate and Deploy VM. Once deployed, copy the public IP address for the VM.

PuTTy

As I'm using a Linux VM, I am going to use PuTTy. Download PuTTy from https://www.ssh.com/ssh/putty/linux/
Open PuTTy and paste your VM's IP address into the Host Name field.
Click the plus next to SSH on the left panel, then click Tunnels.
Enter 8888 into the Source port field and localhost:32400 in Destination field.
Click Session on the left panel, save this PuTTy configuration, and then click Open.
Enter your password to log in to the VM.
Enter the following commands:

Plex

Open a browser window and type http://localhost:8888/web into the address bar.
Log in with your Plex account and go through the steps to setup the Plex Server.
When at the main Plex homescreen and ready to add media, return to the Azure Portal.
Find your File share e.g. 'plex' and click Connect.
Copy the command for Linux.
Open PuTTy and run this command to mount your file share to a directory on the VM.
Return to Plex, and click to Add Library. Browse for Media Folder and select the folder on your file share.

Azure Storage Explorer

Open Azure Storage Explorer. You may need to install this if it is not installed on your local machine.
Add your Azure account and sign in
Find your File share e.g. 'plex' and start to add your media from your local machine to the File share
Open Plex and see your files begin to show :)

Plex has patched and mitigated three vulnerabilities affecting Plex Media Server for Windows that could enable attackers to take full control of the underlying system when chained together.

Plex Media Server is a desktop app and the backend server for the Plex media streaming service, designed for streaming movies, TV shows, music, and photo collections to over the Internet and on local area networks.

The three vulnerabilities tracked CVE-2020-5740, CVE-2020-5741, and CVE-2020-5742 were found by Tenable security researcher Chris Lyne and reported to Plex on May 31st.

If attackers chain together exploits for all these security flaws, they could remotely execute code as SYSTEM, fully taking over the operating system, gain access to all files, deploy backdoors, or move laterally to other devices on the same network.

R-undelete serial key. The Plex Security Team rolled out patches for CVE-2020-5740 on April 24 and for CVE-2020-5741 on May 7, and mitigated CVE-2020-5742 via server-side changes. Onenote for mac picture wrap texture.

Phishing attacks leading to system takeover

According to a proof-of-concept attack described by Lyne here, threat actors who would want to take control of machines running unpatched Plex Media Server installation would have to start with a phishing email disguised as an email notification and designed to redirect the targeted Plex admin users to an attacker-controlled Plex Media Server.

If they fall for their trick and log into the malicious server, 'the attacker can forge requests to the victim’s media server' by abusing the weak cross-origin resource sharing (CORS) policy bug behind CVE-2020-5742 to steal their X-Plex-Token.

Even if the attack stops here, the malicious actors would still have access to the victims' private media, and gain the capability to change server settings, restart reboot media server services, and more.

'As of June 15, 2020, Plex has deployed a mitigation on authentication pages server side to notify users if they are logging into an application not hosted by Plex,' Tenable explains.

In the next step, attackers would have to use the stolen admin authentication token to execute arbitrary Python code remotely with the privileges of the media server by exploiting the CVE-2020-5741 flaw in the Plex Media Server plugin framework.

This would enable them to install backdoors on the compromised systems, as well as pivot to other devices on the server's local area network.

Next, the attackers have to exploit the CVE-2020-5740 vulnerability to elevate their privileges to SYSTEM on Windows systems, effectively completely taking over the underlying system and gaining access to all the files.

'After a successful phishing attack, using the acquired X-Plex-Token, CVE-2020–5741 could be exploited to execute code with the privileges of the media server process,' as Lyne explains.

'The level of access could then be escalated to SYSTEM by exploiting CVE-2020–5740 in the Plex Update Service. At this point, the media server would be completely compromised.'

Update to the latest version to mitigate

Fortigate Rules Plex Media Server Free

To make sure that their servers are safe from attacks designed to exploit these flaws, users are urged to update the latest version.

'We have rolled out a change in our update distribution servers. This change will protect Plex Media Server version 1.18.2 or newer,' the Plex Security Team said. 'Plex Media Server installations older than 1.18.2 will still be exploitable and we highly encourage users on older releases to upgrade.'

'Additionally, Plex Media Server versions 1.19.1.2701 & 1.19.2.2702 (and newer) features additional hardening in the updater infrastructure to protect against future vulnerabilities. We recommended for all users to update to one of these releases.'

Plex also mitigated CVE-2020-5742 by enabling automatic alerts on authentication pages server-side to notify Plex users when they are logging into a media server that's not hosted by Plex.

'Plex Media Server will not automatically update by default but users can enable this within their settings,' Tenable also