Latest revision as of 17:31, 27 July 2014

I'm not a native English speaker. Please correct my mistakes.

In Contao Forum, reports came about changed files, which malicious code was attached.
The problem itself can not be attributed to a vulnerability in Contao, but will be distributed over other ways of the server, eg vulnerable WP plugins, hacked servers, hacked FTP logins, etc.

Forum

Questions about the Bot Detection module will be answered in Forum
Errors and requests can be reported in the Issue Tracker.

Translations

Translations can be performed on Transifex

Installation

The installation of the module occurs about the extension Repository in back end of Contao.
A manual installation is possible. Download the ZIP file from Extension Repository, unzip and transfer it.
A directory should have been created "/system/modules/integrity_check".
Then call /contao/install.php - Perform Update Database.

Example of an Infection

How now looks like such a hack?
The attachment to the file index.php looked like this (shortened):

#c3284d#
echo(gzinflate(base64_decode("ZZBNisMwDIX.......T7oD")));
#/c3284d#

Or like this (shortened):

<script type="text/javascript"> 
function frmAdd() { 
var ifrm = document.createElement('iframe'); 
....
}; 
window.onload = frmAdd; 
</script>

Site one the black list

When you does not react fast enough, and Google notices this, the page is set to the "black list". Browsers like Firefox use this to warn against unauthorized access to it. It looks like this:

Function of the module

In the current version, the most important PHP files are checked for modifications.
This files will be checked:

• index.php
• cron.php (from version 1.1.0)
• contao/index.php
• contao/main.php
• .htaccess (from version 3.1.0)

Special warning tests:

• Check for new Contao versions (from version 3.4.0)
• Check for install tool locking (from version 3.4.0)

Time of verification

This test is performed automatically (Contao-Cron), see the section Technical Details.

Detection

The check is identical to the official Contao check tool, that means via MD5 checksums. Checksums are available for comparison for Contao from 2.10.0.
From version 1.1.0, check via timestamps is possible.

Using

In the backend, you can see the results: System - System Log. Normally if everything is OK, no message appears. In its own module debug mode then there is only a message::

• Checking files for integrity is completed.

If modifications were detected, a message is generated for each file:

• Integrity status for file index.php is: Corrupt [MD5]
• Integrity status for cron.php file is corrupted [Timestamp]
  • It was checked by time stamp, possible from version 1.1.0.

An information is available via System Log and mail, see the section Technical Details.

Technical Details

Creating integrity check

The integrity check need a check plan. This can be used for any of the files for the time, the art of check and the action.

Time intervals

• in Contao 2.10: daily, weekly, monthly
• in Contao 2.11: hourly, daily, weekly, monthly
• in Contao 3.0: minutely(manual), hourly, daily, weekly, monthly

Art of check

The detection of a change in the file is possible via:

• MD5 checksum
• Timestamps

Action

• System log: Message in the system log (backend)
• Mail to Admin: a mail is sent to the admin of the Contao installation.
  • It will then creates also automatically an entry in the System log (from version 1.1.0)

Notes

System-Log und Mail

From version 1.1.0 automatically gets an entry in the system log when a mail is sent.

In Version 1.0.0, if you want to have both types of information, you creates the check twice, each with one of the actions:

Here is an example only for the index.php. This is of course also for the other files.

There can be only one!

It is possible in the integrity check overview to create multiple checks. It basically makes no sense. Therefore, it is ensured that there can be only an integrity check, which is activated. If you switch a new integrity check active, all other existing tests are automatically switched inactive.

Protection against infection

Well, a general protection is probably not possible.
But there is a possibility that the malicious code is not executed. There is a ticket to GitHub, it is accepted for Contao 3. Here is the short info for Contao 2.
Edit the index.php, go to the method "run" in the last line, should be the line of 269th (2.11.5) Before the curly bracket insert an exit; or insert a row for it. Here is from line 268 as an example:

        }
    }

change to:

        }
        exit;
    }

Note: Now, the Integrity Check Tool as well as the Contao Check Tool report a change. Use the check vie timestamp now.

--BugBuster (talk) 18:31, 27 July 2014 (CEST)