* Advisory ID: DRUPAL-SA-CONTRIB-2011-042
* Project: Views Bulk Operations (VBO) [1] (third-party module)
* Version: 6.x
* Date: 2011-September-21
* Security risk: Moderately critical [2]
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
The Views Bulk Operations (VBO) module allows actions and rules to be run on
the selected views rows (nodes, terms, user, etc). It also bundles several
convenient actions. One of those actions allows the bulk modification of
taxonomy terms on a node.
When using the "Modify node taxonomy terms" action to modify taxonomy, and
the vocabulary has user tagging enabled, the vocabulary help (if any) is
shown without being filtered first, leading to a cross site scripting
vulnerability.
This vulnerability is mitigated by the fact that it normally requires the
'administer taxonomy' permission in order to exploit it.
-------- VERSIONS AFFECTED
---------------------------------------------------
Versions prior to 6.x-1.11
Drupal core is not affected. If you do not use the contributed Views Bulk
Operations (VBO) [3] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Views Bulk Operations module for Drupal 6.x, upgrade to
6.x-1.11 [4]
See also the Views Bulk Operations (VBO) [5] project page.
-------- REPORTED BY
---------------------------------------------------------
* Jim Berry [6]
-------- FIXED BY
------------------------------------------------------------
* Karim Ratib [7] the module maintainer
-------- 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 [8].
Learn more about the Drupal Security team and their policies [9], writing
secure code for Drupal [10], and securing your site [11].
[1] http://drupal.org/project/views_bulk_operations
[2] http://drupal.org/security-team/risk-levels
[3] http://drupal.org/project/views_bulk_operations
[4] http://drupal.org/node/1286778
[5] http://drupal.org/project/views_bulk_operations
[6] http://drupal.org/user/240748
[7] http://drupal.org/user/48424
[8] http://drupal.org/contact
[9] http://drupal.org/security-team
[10] http://drupal.org/writing-secure-code
[11] http://drupal.org/security/secure-configuration
* Advisory ID: SA-CONTRIB-2011-041
* Project: Hostmaster (Aegir) [1] (third-party module)
* Version: 6.x
* Date: 2011-September-21
* Security risk: Moderately critical [2]
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
Hostmaster (Aegir) provides a system for managing Drupal sites.
The theme in Hostmaster, Eldir, does not sanitize the custom body classes
correctly leading to a cross site scripting (XSS) vulnerability that can be
exploited when a user is made to view a specially crafted URL. If the user is
logged into an administrative account then the script can take actions using
their permissions or disclose sensitive information to a third party.
This vulnerability is mitigated by the fact that user being attacked must be
logged into Aegir with a privileged account and tricked into visiting a
specially crafted URL.
-------- VERSIONS AFFECTED
---------------------------------------------------
* Hostmaster (Aegir) 6.x-1.x versions prior to 6.x-1.4 [3].
Drupal core is not affected. If you do not use the contributed Hostmaster
(Aegir) [4] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Follow the upgrade instructions in the release notes for the Aegir 1.4
release which can be found at: http://community.aegirproject.org/1.4 [5]
Please note that if you have installed Aegir using the debian packages,
manual intervention is currently required, and you should read the release
notes at the above link for more information.
See also the Hostmaster (Aegir) [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* Khawer Masood and affiliated security team
-------- FIXED BY
------------------------------------------------------------
* Steven Jones [7] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Greg Knaddison (greggles) [8]
-------- 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/hostmaster
[2] http://drupal.org/security-team/risk-levels
[3] http://drupal.org/node/1286402
[4] http://drupal.org/project/hostmaster
[5] http://community.aegirproject.org/1.4
[6] http://drupal.org/project/hostmaster
[7] http://drupal.org/user/99644
[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
* Advisory ID: DRUPAL-SA-CONTRIB-2011-040
* Project: Author Pane [1] (third-party module)
* Version: 6.x
* Date: 2011-September-7
* Security risk: Less critical [2]
* Exploitable from: Remote
* Vulnerability: Access bypass
-------- DESCRIPTION
---------------------------------------------------------
The Author Pane module provides information about users on a site. This
module has integration with several other modules including the user
locations of the Location module. If you enabled display of user locations
the Author Pane module may have shown user locations to site visitors who did
not have the permission "view all user locations" permission.
-------- VERSIONS AFFECTED
---------------------------------------------------
* Author Pane 6.x-2.x versions prior to 6.x-2.2.
Drupal core is not affected. If you do not use the contributed Author Pane
[3] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Author Pane module for Drupal 6.x, upgrade to Author Pane
6.x-2.2 [4]
See also the Author Pane [5] project page.
-------- REPORTED BY
---------------------------------------------------------
* Tony Brooke (silentway) [6]
* Skispcs [7]
-------- FIXED BY
------------------------------------------------------------
* Michelle [8] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Greg Knaddison [9] 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 [10].
Learn more about the Drupal Security team and their policies [11], writing
secure code for Drupal [12], and securing your site [13].
[1] http://drupal.org/project/author_pane
[2] http://drupal.org/security-team/risk-levels
[3] http://drupal.org/project/author_pane
[4] http://drupal.org//drupal.org/node/1271388
[5] http://drupal.org/project/author_pane
[6] http://drupal.org/user/414872
[7] http://drupal.org/user/667658
[8] http://drupal.org/user/23570
[9] http://drupal.org/user/36762
[10] http://drupal.org/contact
[11] http://drupal.org/security-team
[12] http://drupal.org/writing-secure-code
[13] http://drupal.org/security/secure-configuration