• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question Are Plesk servers susceptible to TLS BREACH attacks? (cve-2013-3587)

Mark_NLD

Basic Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.66 Update #2
Hello everyone,

A well known vulnerability scanner reported that our Plesk server (Ubuntu 22, Obsidian 18.0.66 Update #2) is vulnerable for TLS BREACH attacks (cve-2013-3587).
The vulnerability scanner checks if the remote web server has HTTP compression enabled and if it does report the vulnerability. But even with HTTP compression enabled the web application hosted on the web server might not be vulnerable.

Should I disable HTTP compression on all our Plesk servers? Or has Plesk mitigated this thread in another way?

Looking forward to your feedback!

Regards,
Mark
 
Those would fall under Nginx and Apache, and Plesk does a good job at making sure that the versions is pretty up to date. Considering the age of the vulnerability it's safe to assume that as long as you've been keeping plesk up to date then apache and nginx would be up to date as well which would had patched it out assuming it was vulnerable to begin with.

Also I've been reading up on it and I've read that a good number of vulnerability scanners would still report that vulnerability just because you have compression enabled (like you've mention).
 
Back
Top