script '/usr/local/ispconfig/interface/web/login_up.php3' not found or unable to stat

Discussion in 'General' started by cbj4074, Oct 9, 2012.

  1. cbj4074

    cbj4074 Member

    Hi, everyone,

    I've been seeing the following types of entries in /var/log/apache2/error.log, at a rate of 10 entries per second:

    [Tue Oct 09 05:53:11 2012] [error] [client XXX.XXX.XXX.XXX] script '/usr/local/ispconfig/interface/web/login_up.php3' not found or unable to stat
    What might the user-agent be doing (or attempting to do) that would cause such a message to be logged?

    In particular, I'm curious as to why the logged message references a file-system path, as opposed to a URL. This seems to indicate that the user-agent is targeting a specific PHP script that attempts to load a different PHP script from the file-system.
    Last edited: Oct 9, 2012
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Did you had plesk installed on that server before as there is a script with that name in pleask but not in ispconfig:

    so maybe there is a script from plesk or a script developed for plesk installed on the server that searches for this script or an attacker thinks that this is a plesk install. When you access the script by http, the path /usr/local/ispconfig/interface/web/login_up.php3 is the equivalent to /login_up.php3 of the ispconfig controlpanel vhost, so it might be that the script can not identify that its not plesk while searching for the script.
  3. cbj4074

    cbj4074 Member

    Hi, Till, thanks for your response.

    Plesk has never been installed on this server, but ISPConfig is configured to use the same port that Plesk uses (8443). This is probably why the probing software thought that the server is running Plesk.

    What you say regarding the file path translation makes sense.

    It sounds like I can ignore these probes, as they will never be successful if they're looking for Plesk.

    Thanks again for the thorough explanation!

Share This Page