A serious vulnerability in Drupal was re-announced recently. The vulnerability carries the advisory ID of SA-CORE-2014-005 and applies to all Drupal sites running version 7.xx. According to the Public Service Announcement, vulnerable, un-patched sites running Drupal, started getting compromised within about 7 hours of the original vulnerability announcement on October 15, 2014.
Drupal observed vulnerable websites getting attacked starting from 7.32 hours after the initial statement, which did not allow for a lot of time to patch the site. Also, simply patching the site now will not help if your site was already compromised, as the attackers might have left backdoors for later use. There is no way to be certain that every backdoor was found and it is advised restore the affected website using a backup, or even to start from scratch.
According to Mark Stockley of Sophos, of the Internet’s 1 billion websites, somewhere between 1.9% and 5.1% use Drupal. Of these, somewhere between 65%-84% use the affected Drupal 7.xx. Based on this, he estimates that the number of affected websites can be as high as 12 million.
It is advised for every site affected to follow these steps to restore your website using a backup:
- Take the website offline by replacing it with a static HTML page
- Notify the server’s administrator emphasizing that other sites or applications hosted on the same server might have been compromised via a backdoor installed by the initial attack
- Consider obtaining a new server, or otherwise remove all the website’s files and database from the server. (Keep a copy safe for later analysis.)
- Restore the website (Drupal files, uploaded files and database) from backups from before 15 October 2014
- Update or patch the restored Drupal core code
- Put the restored and patched/updated website back online
- Manually redo any desired changes made to the website since the date of the restored backup
- Audit anything merged from the compromised website, such as custom code, configuration, files or other artifacts, to confirm they are correct and have not been tampered with.
For more information, you might be interested in reading the official FAQ on the vulnerability.
Enjoyed this post? Subscribe to our newsletter and don’t miss a thing!