• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Horde arbitrary file inclusion vulnerability

ok, but what can we do now? This fix is for Horde "standalone", what about the "Plesk-IMP"?
 
The link I posted also has links to patches against 3.1.6. Maybe you can modify them so they apply cleanly on psa-horde. Otherwise you'll just have to bug Parallels about it and/or wait for a Plesk update.
 
a fix for 8.3 was requested from Plesk development, so waiting for reply

permanently in 8.4 only
 
The link I posted also has links to patches against 3.1.6. Maybe you can modify them so they apply cleanly on psa-horde. Otherwise you'll just have to bug Parallels about it and/or wait for a Plesk update.

is there any fix for horde 3.1.5 ? my plesk installation uses it:

# rpm -qa|grep horde
psa-horde-3.1.5-suse10.2.build83071218.20
 
It is not clear to me if this requires the attacker to login using genuine credentials or if no authentication is required.

Can anyone enlighten me please?


The patch appears simple but I don't want to apply it in case it breaks the Plesk-modified version.


Faris.
 
I believe the specific SQL injection rules that get it are 340013, and 340017. We've also got a virtual patch for it now, which doesnt have an ID number yet.
 
Back
Top