• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Question jvm on plesk Obsidian (log4j exploit)

SalvadorS

Regular Pleskian
Hello,

I have a debian server with Plesk Obsidian and I found a folder:


/usr/lib/jvm


lrwxrwxrwx 1 root root 24 may 6 2014 default-java -> java-1.7.0-openjdk-amd64
lrwxrwxrwx 1 root root 20 may 19 2017 java-1.7.0-openjdk-amd64 -> java-7-openjdk-amd64
drwxr-xr-x 5 root root 4096 ago 3 2017 java-7-openjdk-amd64
drwxr-xr-x 8 root root 4096 ene 3 2018 java-8-oracle
drwxr-xr-x 9 root root 4096 ago 3 2017 jdk-8-oracle-x64
drwxr-xr-x 7 root root 4096 ago 3 2017 jre-8-oracle-x64

I don´t know why is that there as I don´t use java, tomcat, servlets...

Thinking in log4j exploit, how can i delete this? delete the folder and thats all?
 
Plesk does not use Java internally, so Plesk is not affected by this vulnerability. Since Tomcat support in Plesk was dropped in Plesk 17.8, Plesk does not support users' Java-based applications.

I think you have to remove all java related packages on OS level.
 
Back
Top