- Advisory ID: DRUPAL-SA-2007-018
- Project: Drupal core
- Version: 4.7.x, 5.x
- Date: 2007-July-26
- Security risk: Moderately critical
- Exploitable from: Remote
- Vulnerability: Multiple cross site scripting vulnerabilities
Some server variables are not escaped consistently. When a malicious user is able to entice a victim to visit a specially crafted link or webpage, arbitrary HTML and script code can be injected and executed in the context of the victim’s session on the targeted website.
Custom content type names are not escaped consistently. A malicious user with the ‘administer content types’ permission would be able to inject and execute arbitrary HTML and script code on the website.
Revoking the ‘administer content types’ permission provides an immediate workaround.
Wikipedia has more information about cross site scripting (XSS).
- Drupal 4.7.x before version 4.7.7.
- Drupal 5.x before version 5.2.
Install the latest version:
- If you are running Drupal 4.7.x then upgrade to Drupal 4.7.7.
- If you are running Drupal 5.x then upgrade to Drupal 5.2.
If you are unable to upgrade immediately, you can apply a patch to secure your installation until you are able to do a proper upgrade.
settings.php is one of the files containing vulnerable code. It is therefore critical to replace all of your sites’ settings.php files in subdirectories of
sites with the new one from the archive. After you have replaced the files, make sure to edit the value of the $db_url variable to be identical to the value in your old settings.php. This is the information that determines how Drupal connects to a database.
- The server variables issue was reported by David Caylor.
- Content type naming issues were reported by Karthik.
The security team wishes to thank Dave, Morten Wulff, Brenda Wallace, Fernando Silva, Gerhard Killesreiter, Brandon Bergren, Bart Jansens and Neil Drumm for technical assistance.
The security contact for Drupal can be reached at security at drupal.org or via the form at http://drupal.org/contact.