Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2009.0416 -- [Win][UNIX/Linux]
Drupal core and Drupal third-party modules: Multiple Vulnerabilities
23 July 2009
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Drupal core
Exif (third-party module)
News Page (third-party module)
Node Access User Reference (third-party module)
Fivestar (third-party module)
Publisher: Drupal
Operating System: UNIX variants (UNIX, Linux, OSX)
Windows
Impact: Execute Arbitrary Code/Commands
Access Confidential Data
Cross-site Request Forgery
Cross-site Scripting
Inappropriate Access
Access: Remote/Unauthenticated
CVE Names: CVE-2009-2572 CVE-2009-1501 CVE-2009-1505
CVE-2009-1507
Original Bulletin: http://drupal.org/node/448958
http://drupal.org/node/449014
http://drupal.org/node/449030
http://drupal.org/node/449042
http://drupal.org/node/449078
Comment: This bulletin references five (5) Drupal Advisories.
Revision History: July 23 2009: Added CVE Reference
May 4 2009: Added CVEs
April 30 2009: Initial Release
- --------------------------BEGIN INCLUDED TEXT--------------------
* Advisory ID: DRUPAL-SA-CORE-2009-005
* Project: Drupal core
* Version: 5.x, 6.x
* Date: 2009-April-29
* Security risk: Moderately critical
* Exploitable from: Remote
* Vulnerability: Cross site scripting
- -------- DESCRIPTION ---------------------------------------------------------
When outputting user-supplied data Drupal strips potentially dangerous HTML
attributes and tags or escapes characters which have a special meaning in
HTML. This output filtering secures the site against cross site scripting
attacks via user input. Certain byte sequences that are valid in the UTF-8
specification are potentially dangerous when interpreted as UTF-7. Internet
Explorer 6 and 7 may decode these characters as UTF-7 if they appear before
the <meta http-equiv="Content-Type" /> tag that specifies the page content as
UTF-8, despite the fact that Drupal also sends a real HTTP header specifying
the content as UTF-8. This behaviour enables malicious users to insert and
execute Javascript in the context of the website if site visitors are allowed
to post content. Wikipedia has more information about cross site scripting
[1] (XSS). In addition, Drupal core also has a very limited information
disclosure vulnerability under very specific conditions. If a user is tricked
into visiting the site via a specially crafted URL and then submits a form
(such as the search box) from that page, the information in their form
submission may be directed to a third-party site determined by the URL and
thus disclosed to the third party. The third party site may then execute a
CSRF [2] attack against the submitted form. This vulnerability is limited to
forms present on the frontpage. The user login form is not vulnerable.
- -------- VERSIONS AFFECTED ---------------------------------------------------
* Drupal 5.x before version 5.17.
* Drupal 6.x before version 6.11.
- -------- SOLUTION ------------------------------------------------------------
Install the latest version:
* If you are running Drupal 6.x then upgrade to Drupal 6.11 [3].
* If you are running Drupal 5.x then upgrade to Drupal 5.17 [4].
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. Theses patches
fix the security vulnerability, but does not contain other fixes which were
released in Drupal 5.17 or Drupal 6.11.
* To patch Drupal 6.10 use SA-CORE-2009-005-6.10.patch [5].
* To patch Drupal 5.16 use SA-CORE-2009-005-5.16.patch [6].
As an alternate solution if you are unable to upgrade immediately, you can
alter your page template following the pattern in the core changes. Open your
theme's main page.tpl.php file as well as any other page templates like
page-node.tpl.php or page-front.tpl.php and move the line that is printing
$head (<?php print $head ?>) above line with the <title> tag, so that it is
the first item after the <head>.
- -------- REPORTED BY ---------------------------------------------------------
The UTF-7 XSS issue was reported by pod.Edge. The information disclosure
vulnerability was reported by Moritz Naumann [7].
- -------- FIXED BY ------------------------------------------------------------
The Drupal security team
- -------- CONTACT -------------------------------------------------------------
The security team for Drupal can be reached at security at drupal.org or via
the form at http://drupal.org/contact.
[1] http://en.wikipedia.org/wiki/Xss
[2] http://en.wikipedia.org/wiki/Cross-site_request_forgery
[3] http://ftp.drupal.org/files/projects/drupal-6.11.tar.gz
[4] http://ftp.drupal.org/files/projects/drupal-5.17.tar.gz
[5] http://drupal.org/files/sa-core-2009-005/SA-CORE-2009-005-6.10.patch
[6] http://drupal.org/files/sa-core-2009-005/SA-CORE-2009-005-5.16.patch
[7] http://moritz-naumann.com/
- -------------------------------------------------------------------------------
* Advisory ID: DRUPAL-SA-CONTRIB-2009-0xx
* Project: Exif (third-party module)
* Version: 5.x, 6.x
* Date: 2009-April-29
* Security risk: Moderately critical
* Exploitable from: Remote
* Vulnerability: Cross-site scripting
- -------- DESCRIPTION ---------------------------------------------------------
The Exif module enables users to display EXIF tags in images on the site.
EXIF tags are not properly filtered for HTML input, allowing users with
permission to upload images to inject arbitrary code into the site using a
specially crafted image. Such a cross site scripting [1] (XSS) attack may
lead to a malicious user gaining full administrative access.
- -------- VERSIONS AFFECTED ---------------------------------------------------
* Exif 5.x-1.x prior to 5.x-1.2
* Exif 6.x-1.x-dev prior to April 13, 2009
Drupal core is not affected. If you do not use the contributed Exif module,
there is nothing you need to do.
- -------- SOLUTION ------------------------------------------------------------
Install the latest version:
* If you use Exif 5.x-1.x upgrade to Exif 5.x-1.2 [2].
* Although development versions are not supported, a fix is available; If
you use Exif 6.x-1.x-dev prior to April 13, 2009, upgrade to latest Exif
6.x-1.x-dev [3].
See also the Exif project page [4].
- -------- REPORTED BY ---------------------------------------------------------
Jakub Suchy [5] of the Drupal security team and Michael Hess [6].
- -------- FIXED BY ------------------------------------------------------------
James Gilliland [7] and rapsli [8].
- -------- CONTACT -------------------------------------------------------------
The security team for Drupal can be reached at security at drupal.org or via
the form at http://drupal.org/contact.
[1] http://en.wikipedia.org/wiki/Cross-site_scripting
[2] http://drupal.org/node/448862
[3] http://drupal.org/node/363274
[4] http://drupal.org/project/exif
[5] http://drupal.org/user/31977
[6] http://drupal.org/user/102818
[7] http://drupal.org/user/48673
[8] http://drupal.org/user/140802
- -------------------------------------------------------------------------------
* Advisory ID: DRUPAL-SA-CONTRIB-2009-023
* Project: News Page
* Versions: 5.x
* Date: 2009-April-29
* Security risk: Moderately critical
* Exploitable from: Remote
* Vulnerability: SQL injection
- -------- DESCRIPTION ---------------------------------------------------------
The News Page module provides a node content type which displays feed items
from an aggregator category, filtered by keywords entered into the 'Include
Words' field of the node. Unfortunately the News Page module uses keywords
directly in SQL queries without being sanitized, allowing SQL injection
attacks [1] by malicious users who have access to create and edit News Page
nodes.
- -------- VERSIONS AFFECTED ---------------------------------------------------
* Versions of News Page for Drupal 5.x prior to 5.x-1.2
Drupal core is not affected. If you do not use the News Page module, there is
nothing you need to do.
- -------- SOLUTION ------------------------------------------------------------
Install the latest version.
* If you use News Page for Drupal 5.x upgrade to 5.x-1.2 [2]
Also see the News Page project page [3].
- -------- REPORTED BY ---------------------------------------------------------
Robert Castelo (Robert Castelo [4])
- -------- FIXED BY ------------------------------------------------------------
Robert Castelo (Robert Castelo [5])
- -------- CONTACT -------------------------------------------------------------
The security contact for Drupal can be reached at security at drupal.org or
via the form at http://drupal.org/contact and by selecting the security
issues category.
[1] http://en.wikipedia.org/wiki/SQL_injection
[2] http://drupal.org/node/448988
[3] http://drupal.org/project/news_page
[4] http://drupal.org/user/3555
[5] http://drupal.org/user/3555
- -------------------------------------------------------------------------------
* Advisory ID: DRUPAL-SA-CONTRIB-2009-024
* Project: Node Access User Reference (third-party module)
* Version: 5.x, 6.x
* Date: 2009-April-29
* Security risk: Critical
* Exploitable from: Remote
* Vulnerability: Access bypass
- -------- DESCRIPTION ---------------------------------------------------------
Node Access User Reference enables administrators to automatically grant node
access (view, update, or delete) to a node where the user is referenced by
CCK user reference. When such a field is saved with an empty value, Node
Access User Reference mistakes this for a reference to the anonymous user,
and allows non logged in visitors to view or author the node in question.
- -------- VERSIONS AFFECTED ---------------------------------------------------
* Node Access User Reference 5.x prior to 5.x-2.0-beta4
* Node Access User Reference 6.x prior to 6.x-2.0-beta6
Drupal core is not affected. If you do not use the contributed Node Access
User Reference module, there is nothing you need to do.
- -------- SOLUTION ------------------------------------------------------------
Install the latest version:
* If you use Node Access User Reference 5.x upgrade to Node Access User
Reference 5.x-2.0-beta4 [1].
* If you use Node Access User Reference 6.x upgrade to Node Access User
Reference 5.x-2.0-beta4 [2].
See also the Node Access User Reference project page [3].
- -------- REPORTED BY ---------------------------------------------------------
Jakub Suchy [4] of the Drupal security team and Bob Geiger [5].
- -------- FIXED BY ------------------------------------------------------------
Daniel Braksator [6].
- -------- CONTACT -------------------------------------------------------------
The security team for Drupal can be reached at security at drupal.org or via
the form at http://drupal.org/contact.
[1] http://drupal.org/node/448390
[2] http://drupal.org/node/448392
[3] http://drupal.org/project/nodeaccess_userreference
[4] http://drupal.org/user/31977
[5] http://drupal.org/user/380770
[6] http://drupal.org/user/134005
- ------------------------------------------------------------------------------
* Advisory ID: DRUPAL-SA-CONTRIB-2009-025
* Project: Fivestar (third-party module)
* Version: 5.x, 6.x
* Date: 2009-April-29
* Security risk: Not critical
* Exploitable from: Remote
* Vulnerability: Cross-site request forgery
- -------- DESCRIPTION ---------------------------------------------------------
The Fivestar module provides a voting widget for content and records votes
using Ajax. The URL used by the javascript to register votes is vulnerable to
cross-site request forgeries (CSRF [1]) making it possible for users to
unknowingly vote for content.
- -------- VERSIONS AFFECTED ---------------------------------------------------
* Fivestar 5.x-1.x prior to 5.x-1.14
* Fivestar 6.x-1.x prior to 6.x-1.14
Drupal core is not affected. If you do not use the contributed Fivestar
module, there is nothing you need to do.
- -------- SOLUTION ------------------------------------------------------------
Install the latest version:
* If you use Fivestar 5.x-1.x upgrade to Fivestar 5.x-1.14 [2]
* If you use Fivestar 6.x-1.x upgrade to Fivestar 6.x-1.14 [3]
See also the Fivestar project page [4].
- -------- REPORTED BY ---------------------------------------------------------
John Morahan [5] of the Drupal security team.
- -------- FIXED BY ------------------------------------------------------------
Nate Haug (quicksketch) [6] and Moshe Weitzman [7].
- -------- CONTACT -------------------------------------------------------------
The security team for Drupal can be reached at security at drupal.org or via
the form at http://drupal.org/contact.
[1] http://en.wikipedia.org/wiki/Csrf
[2] http://drupal.org/node/449028
[3] http://drupal.org/node/449026
[4] http://drupal.org/project/fivestar
[5] http://drupal.org/user/58170
[6] http://drupal.org/user/35821
[7] http://drupal.org/user/23
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
http://www.auscert.org.au/render.html?cid=1980
If you believe that your computer system has been compromised or attacked in
any way, we encourage you to let us know by completing the secure National IT
Incident Reporting Form at:
http://www.auscert.org.au/render.html?it=3192
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iD8DBQFKZ8+zNVH5XJJInbgRAtz/AJ93Wq8KTjTKFzvtOc4Nj5F5mrTJOgCfRkIA
CwPIS/p0owTdFp1/MWpsaWg=
=Qjnc
-----END PGP SIGNATURE-----