Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2011.1005
A number of vulnerabilities have been identified in Drupal
third-party modules
6 October 2011
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: petition_node (Drupal third-party module)
Homebox (Drupal third-party module)
Rate (Drupal third-party module)
Echo (Drupal third-party module)
OG Features (Drupal third-party module)
Publisher: Drupal
Operating System: Windows
UNIX variants (UNIX, Linux, OSX)
Impact/Access: Cross-site Scripting -- Remote/Unauthenticated
Unauthorised Access -- Remote/Unauthenticated
Resolution: Patch/Upgrade
Original Bulletin:
http://drupal.org/node/1300238
http://drupal.org/node/1300552
http://drupal.org/node/1300558
http://drupal.org/node/1300610
http://drupal.org/node/1300642
Comment: This bulletin contains five (5) Drupal security advisories.
- --------------------------BEGIN INCLUDED TEXT--------------------
* Advisory ID: DRUPAL-SA-CONTRIB-2011-043
* Project: petition_node [1] (third-party module)
* Version: 6.x
* Date: 2011-October-05
* Security risk: Moderately critical [2]
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
- -------- DESCRIPTION ---------------------------------------------------------
Petition node module allows the creation of petition nodes to collect
signatures to show support for a cause.
The module contains a cross site scripting (XSS) vulnerability that can be
exploited when signing a petition.
This vulnerability is mitigated by the fact that it normally requires the
'sign petitions' permission in order to exploit it.
- -------- VERSIONS AFFECTED ---------------------------------------------------
* petition_node 6.x-1.x versions prior to 6.x-1.5.
Drupal core is not affected. If you do not use the contributed petition_node
[3] module, there is nothing you need to do.
- -------- SOLUTION ------------------------------------------------------------
Install the latest version:
* If you use the petition_node module for Drupal 6.x, upgrade to
petition_node 6.x-1.5 [4]
See also the petition_node [5] project page.
- -------- REPORTED BY ---------------------------------------------------------
* galooph [6]
- -------- FIXED BY ------------------------------------------------------------
* galooph [7] the module maintainer
* mlhess [8] of the Drupal Security Team
- -------- CONTACT AND MORE INFORMATION ----------------------------------------
The Drupal security team can be reached at security at drupal.org or via the
contact form at http://drupal.org/contact [9].
Learn more about the Drupal Security team and their policies [10], writing
secure code for Drupal [11], and securing your site [12].
[1] http://drupal.org/project/1075944
[2] http://drupal.org/security-team/risk-levels
[3] http://drupal.org/project/1075944
[4] http://drupal.org/node/1299412
[5] http://drupal.org/project/1075944
[6] http://drupal.org/user/241220
[7] http://drupal.org/user/241220
[8] http://drupal.org/user/102818
[9] http://drupal.org/contact
[10] http://drupal.org/security-team
[11] http://drupal.org/writing-secure-code
[12] http://drupal.org/security/secure-configuration
_______________________________________________
* Advisory ID: DRUPAL-SA-CONTRIB-2011-044
* Project: Homebox [1] (third-party module)
* Version: 6.x, 7.x
* Date: 2011-October-05
* Security risk: Moderately critical [2]
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting (XSS [3])
- -------- DESCRIPTION ---------------------------------------------------------
Homebox allows site administrators to create dashboards for their users,
using blocks as widgets. Blocks in a Homebox page are resizeable, and
reorderable by dragging.
Homebox OG is a submodule of Homebox which allows Organics Groups
administrators to specify a Homebox to be used as the group homepage for any
Organic Group. Homebox OG does not do sufficient filtering of user supplied
text which presents a cross site scripting vulnerability.
This vulnerability is mitigated by the fact that an attacker must have a user
account with a role permitted to create or edit an Organic Groups node.
- -------- VERSIONS AFFECTED ---------------------------------------------------
* Homebox 6.x-2.x versions.
* Homebox 6.x-3.x versions prior to 6.x-3.0-beta3.
* Homebox 7.x-2.x versions prior to 7.x-2.0-beta4.
Drupal core is not affected. If you do not use the contributed Homebox [4]
module, there is nothing you need to do.
- -------- SOLUTION ------------------------------------------------------------
Install the latest version:
* If you use the Homebox module for Drupal 6.x, upgrade to Homebox
6.x-3.0-beta5 [5] note that 6.x-2.x branch is no longer supported users of
6.x-2.x should upgrade to 6.x-3.x
* If you use the Homebox module for Drupal 7.x, upgrade to Homebox
7.x-2.0-beta6 [6]
If you do not use the contributed homebox_og module you do not need to
upgrade.
See also the Homebox [7] project page.
- -------- REPORTED BY ---------------------------------------------------------
* Greg Knaddison [8] of the Drupal Security Team
- -------- FIXED BY ------------------------------------------------------------
* Brian Vuyk [9] the module maintainer
- -------- COORDINATED BY ------------------------------------------------------
* Greg Knaddison [10] of the Drupal Security Team
- -------- CONTACT AND MORE INFORMATION ----------------------------------------
The Drupal security team can be reached at security at drupal.org or via the
contact form at http://drupal.org/contact [11].
Learn more about the Drupal Security team and their policies [12], writing
secure code for Drupal [13], and securing your site [14].
[1] http://drupal.org/project/homebox
[2] http://drupal.org/security-team/risk-levels
[3] http://en.wikipedia.org/wiki/Cross-site_scripting
[4] http://drupal.org/project/homebox
[5] http://drupal.org/node/1300578
[6] http://drupal.org/node/1300428
[7] http://drupal.org/project/homebox
[8] http://drupal.org/user/36762
[9] http://drupal.org/user/46854
[10] http://drupal.org/user/36762
[11] http://drupal.org/contact
[12] http://drupal.org/security-team
[13] http://drupal.org/writing-secure-code
[14] http://drupal.org/security/secure-configuration
_______________________________________________
* Advisory ID: DRUPAL-SA-CONTRIB-2011-045
* Project: Rate [1] (third-party module)
* Version: 6.x, 7.x
* Date: 2011-October-05
* Security risk: Moderately critical [2]
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting (XSS [3])
- -------- DESCRIPTION ---------------------------------------------------------
The Rate module provides flexible rate widgets. These widgets are refreshed
via AJAX after voting. The AJAX callback does not correctly handle certain
arguments obtained from the URL. By enticing a suitably privileged user to
visit a specially crafted URL, a malicious user is able to insert arbitrary
HTML and script code into the rate widget. Such a cross-site scripting attack
may lead to the malicious user gaining administrative access.
- -------- VERSIONS AFFECTED ---------------------------------------------------
* rate 6.x-1.x versions prior to 6.x-1.3 [4].
* rate 7.x-1.x versions prior to 7.x-1.2 [5].
Drupal core is not affected. If you do not use the contributed Rate [6]
module, there is nothing you need to do.
- -------- SOLUTION ------------------------------------------------------------
Install the latest version:
* If you use the Rate module for Drupal 6.x, upgrade to Rate 6.x-1.3 [7]
* If you use the Rate module for Drupal 7.x, upgrade to Rate 7.x-1.2 [8]
See also the Rate [9] project page.
- -------- REPORTED BY ---------------------------------------------------------
* Zakaria Rachid
- -------- FIXED BY ------------------------------------------------------------
* Maurits Lawende [10] the module maintainer
- -------- COORDINATED BY ------------------------------------------------------
* Greg Knaddison [11] of the Drupal Security Team
- -------- CONTACT AND MORE INFORMATION ----------------------------------------
The Drupal security team can be reached at security at drupal.org or via the
contact form at http://drupal.org/contact [12].
Learn more about the Drupal Security team and their policies [13], writing
secure code for Drupal [14], and securing your site [15].
[1] http://drupal.org/project/rate
[2] http://drupal.org/security-team/risk-levels
[3] http://en.wikipedia.org/wiki/Cross-site_scripting
[4] http://drupal.org/node/1299652
[5] http://drupal.org/node/1299654
[6] http://drupal.org/project/rate
[7] http://drupal.org/node/1299652
[8] http://drupal.org/node/1299654
[9] http://drupal.org/project/rate
[10] http://drupal.org/user/243897
[11] http://drupal.org/user/36762
[12] http://drupal.org/contact
[13] http://drupal.org/security-team
[14] http://drupal.org/writing-secure-code
[15] http://drupal.org/security/secure-configuration
_______________________________________________
* Advisory ID: DRUPAL-SA-CONTRIB-2011-046
* Project: Echo [1] (third-party module)
* Version: 6.x, 7.x, 8.x
* Date: 2011-October-05
* Security risk: Critical [2]
* Exploitable from: Remote
* Vulnerability: Multiple vulnerabilities
- -------- DESCRIPTION ---------------------------------------------------------
The Echo module generates a fully-themed Drupal page, returning the rendered
page as a text string and allowing other modules to style an HTML message as
if it had been generated by the live website.
The module does not properly sanitize user-supplied content, resulting in a
Cross-Site Scripting (XSS [3]) vulnerability. Additionally, the module allows
arbitrary content passed via the URL to be embedded on the site, rendering
the site vulnerable to phishing [4] exploits.
- -------- VERSIONS AFFECTED ---------------------------------------------------
* Echo 6.x-1.x versions prior to 6.x-1.7 [5].
* Echo 7.x-1.x versions prior to 7.x-1.7 [6].
* Echo 8.x-1.x versions prior to 8.x-1.7 [7].
Drupal core is not affected. If you do not use the contributed Echo [8]
module, there is nothing you need to do.
- -------- SOLUTION ------------------------------------------------------------
Install the latest version:
* If you use the Echo module for Drupal 6.x, upgrade to Echo 6.x-1.7 [9].
* If you use the Echo module for Drupal 7.x, upgrade to Echo 7.x-1.7 [10].
* If you use the Echo module for Drupal 8.x, upgrade to Echo 8.x-1.7 [11].
See also the Echo [12] project page.
- -------- REPORTED BY ---------------------------------------------------------
* Francesco Placella (plach [13])
- -------- FIXED BY ------------------------------------------------------------
* Bob Vincent (pillarsdotnet [14]) the module maintainer
- -------- COORDINATED BY ------------------------------------------------------
* mr.baileys [15] of the Drupal Security Team
- -------- CONTACT AND MORE INFORMATION ----------------------------------------
The Drupal security team can be reached at security at drupal.org or via the
contact form at http://drupal.org/contact [16].
Learn more about the Drupal Security team and their policies [17], writing
secure code for Drupal [18], and securing your site [19].
[1] http://drupal.org/project/echo
[2] http://drupal.org/security-team/risk-levels
[3] http://en.wikipedia.org/wiki/Cross-site_scripting
[4] http://en.wikipedia.org/wiki/Phishing
[5] http://drupal.org/node/1274528
[6] http://drupal.org/node/1274530
[7] http://drupal.org/node/1274532
[8] http://drupal.org/project/echo
[9] http://drupal.org/node/1274528
[10] http://drupal.org/node/1274530
[11] http://drupal.org/node/1274532
[12] http://drupal.org/project/echo
[13] http://drupal.org/user/183211
[14] http://drupal.org/user/36148
[15] http://drupal.org/user/383424
[16] http://drupal.org/contact
[17] http://drupal.org/security-team
[18] http://drupal.org/writing-secure-code
[19] http://drupal.org/security/secure-configuration
_______________________________________________
* Advisory ID: DRUPAL-SA-CONTRIB-2011-047
* Project: OG Features [1] (third-party module)
* Version: 6.x
* Date: 2011-October-05
* Security risk: Highly critical [2]
* Exploitable from: Remote
* Vulnerability: Access bypass
- -------- DESCRIPTION ---------------------------------------------------------
OG Features provides a mechanism for groups to enable or disable certain
bundles of functionality, of features, within the groups they administer. The
module is able to turn components on and off within given groups by
overriding the access callbacks of every menu item, and checking conditions
before passing it off to the original access callback.
When local task menu items are declared in hook_menu(), they often exclude an
access callback and access arguments, leaving it to be inherited by the
parent path. OG Features did not check for this condition, and thus granted
access to many pages that contained local tasks, regardless of roles or
permissions. Because of this, many administration pages are left open to
users, both anonymous and not, giving them control over the site.
- -------- VERSIONS AFFECTED ---------------------------------------------------
* OG Features 6.x-1.x versions prior to 6.x-1.2.
Drupal core is not affected. If you do not use the contributed OG Features
[3] module, there is nothing you need to do.
- -------- SOLUTION ------------------------------------------------------------
Install the latest version:
* If you use the OG Features module for Drupal 6.x, upgrade to OG Features
6.x-1.2 [4]
See also the OG Features [5] project page.
- -------- REPORTED BY ---------------------------------------------------------
* Imad Nabli [6]
- -------- FIXED BY ------------------------------------------------------------
* Mike Stefanello [7] the module maintainer
- -------- COORDINATED BY ------------------------------------------------------
* Greg Knaddison [8] of the Drupal Security Team
- -------- CONTACT AND MORE INFORMATION ----------------------------------------
The Drupal security team can be reached at security at drupal.org or via the
contact form at http://drupal.org/contact [9].
Learn more about the Drupal Security team and their policies [10], writing
secure code for Drupal [11], and securing your site [12].
[1] http://drupal.org/project/og_features
[2] http://drupal.org/security-team/risk-levels
[3] http://drupal.org/project/og_features
[4] http://drupal.org/node/1300644
[5] http://drupal.org/project/og_features
[6] http://drupal.org/user/1489142
[7] http://drupal.org/user/107190
[8] http://drupal.org/user/36762
[9] http://drupal.org/contact
[10] http://drupal.org/security-team
[11] http://drupal.org/writing-secure-code
[12] http://drupal.org/security/secure-configuration
- --------------------------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
===========================================================================
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
iQIVAwUBTo0tme4yVqjM2NGpAQLBcRAApu1Mu4sEOdYB5+5MUPNfOcSn/SNdu5ED
LVgRI9qHqvx31RIkRo3QpVGJsZKhXpfKUJnUuUCgwY1hVo+90RBdziKIZnnjVFP0
sQNt7LdeAc5wSpCS3twf9LMMugzEehiv9M/WkgXlrXGlPXu8PvrIZg8UH5pTp0Jx
mOes30gr1A+R2UUwnCTbH116jsoug2kU8NsoA2p+ReYho5a+Dk+eaGJekDIv5GNm
c/4EPrsZ++XyZBJe8ZGHfeMqVcaMdnnLxVLbLxG/aVS8rZuG+HOEm9FIZUG9uRzW
j/wwNKoguSO+WF9a/5QbxXSCNjdd8kYZisyRVoh9Otz4o/a9v4SVkA6/wKysPC75
gJP3jEvOSWwubAf0NouRwMuuaNa/3/oWp9PaHYsccq90a9Bz/PjM78FOSDdrczcd
umKVDqJHQchSxP/cO1HlPCLuHzH/gRN6E8wxXKAKILp2z8ySMDoixbBW4AoaDUcC
tW7Gt+K2KYhlhyZCJH2Rj6NAOHeGAgyxBn6aG8t1I4CPVeXqTsddIxntWYdPZHib
Jb5qFzfpi+2rDZO+DZcHEt8fZel98Hl3z5W3gm4UmA3ntTSkIWtL7/Br6TLdgSN7
HkoH9Ac2unQrshRm05JgAgdVlrakJlr/9VC3qxfyMg+WD7HJrXgEBj5LLIMJO0YX
kb+yh+Dbocw=
=f20q
-----END PGP SIGNATURE-----