Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2009.1359.2
Drupal third-party modules: Multiple Vulnerabilities
1 October 2009
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: XML sitemap
Bibliography
Browscap
Organic Groups
Dex: Contact Information Manager
Boost
Shared Sign On
Publisher: Drupal
Operating System: Windows
UNIX variants (UNIX, Linux, OSX)
Impact/Access: Cross-site Scripting -- Remote/Unauthenticated
Create Arbitrary Files -- Remote/Unauthenticated
Cross-site Request Forgery -- Remote/Unauthenticated
Resolution: Patch/Upgrade
CVE Names: CVE-2009-3488 CVE-2009-3479
Original Bulletin:
http://drupal.org/node/591724
http://drupal.org/node/592192
http://drupal.org/node/592272
http://drupal.org/node/592358
http://drupal.org/node/592394
http://drupal.org/node/592490
http://drupal.org/node/592488
Comment: This bulletin contains seven (7) Drupal Security Advisories.
Drupal Core is not affected by any of these vulnerabilities.
Revision History: October 1 2009: Added CVE References
October 1 2009: Initial Release
- --------------------------BEGIN INCLUDED TEXT--------------------
* Advisory ID: DRUPAL-SA-CONTRIB-2009-063
* Project: XML sitemap (third-party module)
* Version: 5.x
* Date: 2009-September-30
* Security risk: Less critical
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
- -------- DESCRIPTION -------------------------------------------------------
The XML sitemap module creates a sitemap that conforms to the sitemaps.org
specification. It also allows users with the 'administer site configuration'
permission to add additional custom links to be included in the sitemap. In
the additional links interface, the module does not properly sanitize the
output of the link paths before display, leading to a cross-site scripting
(XSS [1]) vulnerability. Such an attack may lead to a malicious user gaining
full administrative access.
- -------- VERSIONS AFFECTED -------------------------------------------------
* XML sitemap versions 5.x prior to 5.x-1.7
Drupal core is not affected. If you do not use the contributed XML sitemap
module, there is nothing you need to do.
- -------- SOLUTION ----------------------------------------------------------
Install the latest version:
* If you use the XML sitemap for Drupal 5.x upgrade to XML sitemap 5.x-1.7
[2]
See also the XML sitemap module project page [3].
- -------- IMPORTANT NOTES ---------------------------------------------------
This vulnerability was publicly disclosed. If you find a security
vulnerability, please contact the Security team rather than posting a public
issue. If you are a module maintainer, do not commit any security-related
code fixes unless you have coordinated with the Security team.
- -------- REPORTED BY -------------------------------------------------------
This vulnerability was publicly disclosed.
- -------- FIXED BY ----------------------------------------------------------
Dave Reid [4] of the Drupal Security Team and module co-maintainer.
- -------- 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/591732
[3] http://drupal.org/project/xmlsitemap
[4] http://drupal.org/user/53892
* Advisory ID: DRUPAL-SA-CONTRIB-2009-064
* Project: Bibliography module (third-party module)
* Version: 6.x
* Date: 2009-September-30
* Security risk: Moderately critical
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
- -------- DESCRIPTION -------------------------------------------------------
The Bibliography module (also known as Biblio) allows users manage and
display lists of scholarly publications. The Biblio module creates customized
views in order to display these listings, and these listings contain text
entered by users with the 'create biblio' permission. In some cases, the
module does not properly sanitize the text, leading to a cross-site scripting
(XSS [1]) vulnerability. Such an attack may lead to a malicious user gaining
full administrative access.
- -------- VERSIONS AFFECTED -------------------------------------------------
* Bibliography module versions 6.x prior to 6.x-1.7
Drupal core is not affected. If you do not use the contributed Bibliography
module, there is nothing you need to do.
- -------- SOLUTION ----------------------------------------------------------
Install the latest version:
* If you use the Bibliography module for Drupal 6.x upgrade to Bibliography
module 6.x-1.7 [2]
See also the Bibliography module project page [3].
- -------- REPORTED BY -------------------------------------------------------
Justin C. Klein Keane [4]
- -------- FIXED BY ----------------------------------------------------------
Ron Jerome [5] the module maintainer.
- -------- 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/592174
[3] http://drupal.org/project/biblio
[4] http://drupal.org/user/302225
[5] http://drupal.org/user/54997
* Advisory ID: DRUPAL-SA-CONTRIB-2009-065
* Project: Browscap (third-party module)
* Version: 5.x, 6.x
* Date: 2009-September-30
* Security risk: Critical
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
- -------- DESCRIPTION -------------------------------------------------------
The Browscap module provides a way to identify the visitors to your site
based on the user agent in their browser. It can also record these user agent
strings and provide reports about them. When displaying reports about
visitors, the module does not properly sanitize the user agent strings before
display, leading to a cross-site scripting (XSS [1]) vulnerability. Such an
attack may lead to a malicious user gaining full administrative access.
Mitigating factors: this only impacts sites which use the "Monitor browsers"
feature.
- -------- VERSIONS AFFECTED -------------------------------------------------
* Browscap versions 6.x prior to 6.x-1.1
* Browscap versions 5.x prior to 5.x-1.1
Drupal core is not affected. If you do not use the contributed Browscap
module, there is nothing you need to do.
- -------- SOLUTION ----------------------------------------------------------
Install the latest version:
* If you use the Browscap for Drupal 6.x upgrade to Browscap 6.x-1.1 [2]
* If you use the Browscap for Drupal 5.x upgrade to Browscap 5.x-1.1 [3]
See also the Browscap module project page [4].
- -------- REPORTED BY -------------------------------------------------------
Greg Knaddison [5] of the Drupal Security Team
- -------- FIXED BY ----------------------------------------------------------
Greg Knaddison [6] of the Drupal Security Team with help from Rob Loach [7]
and Mike Ryan [8] and Dave Reid [9] of 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/Cross-site_scripting
[2] http://drupal.org/node/592264
[3] http://drupal.org/node/592262
[4] http://drupal.org/project/browscap
[5] http://drupal.org/user/36762
[6] http://drupal.org/user/36762
[7] http://drupal.org/user/61114
[8] http://drupal.org/user/4420
[9] http://drupal.org/user/53892
* Advisory ID: DRUPAL-SA-CONTRIB-2009-066
* Project: Organic Groups (third-party module)
* Version: 5.x, 6.x
* Date: 2009-September-30
* Security risk: Moderately Critical
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
- -------- DESCRIPTION -------------------------------------------------------
The Organic Groups (OG) module provides a way to organize users and content
into groups. When displaying group nodes, the module does not properly
sanitize all user-entered text, leading to a cross-site scripting (XSS [1])
vulnerability. Users with permission to create or edit groups nodes (which
may be any node types assigned by the site administrator) may carry out the
attack. Such an attack may lead to a malicious user gaining full
administrative access.
- -------- VERSIONS AFFECTED -------------------------------------------------
* Organic Groups 6.x-1.x prior to 6.x-1.4
* Organic Groups 5.x-8.x prior to 5.x-8.1
* Organic Groups 5.x-7.x prior to 5.x-7.4
* Organic Groups 6.x-2.0 existing release is not affected.
Drupal core is not affected. If you do not use the contributed Organic Groups
module, there is nothing you need to do.
- -------- SOLUTION ----------------------------------------------------------
Install the latest version:
* If you use the Organic Groups for Drupal 6.x-1.x upgrade to OG 6.x-1.4 [2]
* If you use the Organic Groups for Drupal 5.x-8.x upgrade to OG 5.x-8.1 [3]
* If you use the Organic Groups for Drupal 5.x-7.x upgrade to OG 5.x-7.4 [4]
See also the Organic Groups module project page [5].
- -------- REPORTED BY -------------------------------------------------------
John Morahan [6] of the Drupal Security Team
- -------- FIXED BY ----------------------------------------------------------
John Morahan [7] and Derek Wright [8], both of 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/Cross-site_scripting
[2] http://drupal.org/node/592410
[3] http://drupal.org/node/592412
[4] http://drupal.org/node/592414
[5] http://drupal.org/project/og
[6] http://drupal.org/user/58170
[7] http://drupal.org/user/58170
[8] http://drupal.org/user/46549
* Advisory ID: DRUPAL-SA-CONTRIB-2009-067
* Project: Dex: Contact Information Manager (third-party module)
* Version: 5.x, 6.x
* Date: 2009-Sept-30
* Security risk: Critical
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
- -------- DESCRIPTION -------------------------------------------------------
The Dex: Contact Information Manager module enables contact information
management with Google Maps and Yahoo Maps compatible geocoding. The module
suffers from a Cross Site Scripting (XSS) vulnerability. Such an attack may
lead to a malicious user gaining full administrative access. This module is
no longer maintained. The releases have been unpublished and it is
recommended that it be disabled and uninstalled if in use.
- -------- VERSIONS AFFECTED -------------------------------------------------
* Dex versions 6.x up to and including 6.x-1.0-rc1
* Dex versions 5.x up to and including 5.x-1.0
Drupal core is not affected. If you do not use the contributed Dex module,
there is nothing you need to do.
- -------- SOLUTION ----------------------------------------------------------
There is no solution available. It is recommended that you disable and
uninstall the Dex module if is in use on your site.
- -------- REPORTED BY -------------------------------------------------------
* Reported by Stéphane Corlosquet [1] of the Drupal security team.
- -------- HANDLED BY --------------------------------------------------------
* On behalf of Drupal security team, this SA has been handled by Peter
Wolanin [2], Stéphane Corlosquet [3] and Jakub Suchy [4]
- -------- CONTACT -----------------------------------------------------------
The security contact for Drupal can be reached at security at drupal.org or
via the form at http://drupal.org/contact.
[1] drupal.org/user/52142
[2] http://drupal.org/user/49851
[3] drupal.org/user/52142
[4] http://drupal.org/user/31977
* Advisory ID: DRUPAL-SA-CONTRIB-2009-068
* Project: Boost (third-party module)
* Version: 6.x-1.*
* Date: 2009-09-30
* Security risk: Low
* Exploitable from: Remote
* Vulnerability: Filesystem Directory Creation
- -------- DESCRIPTION -------------------------------------------------------
The Boost module provides a static file-based cache of Drupal pages for
anonymous users. A vulnerability in the module allows an attacker to create
new directories inside the webroot that the web server can write to. Existing
directories cannot be changed using this vulnerability, but it can be used to
affect the system by creating enough directories to reach the 35,000 limit.
- -------- VERSIONS AFFECTED -------------------------------------------------
* Boost module before version 6.x-1.03
Drupal core is not affected. If you do not use the contributed Boost module,
there is nothing you need to do.
- -------- SOLUTION ----------------------------------------------------------
Install the latest version:
* If you use the Boost module for Drupal 6.x upgrade to Boost module
6.x-1.03 [1]
- -------- REPORTED BY -------------------------------------------------------
Hans Rossel [2]
- -------- FIXED BY ----------------------------------------------------------
Mike Carper [3] the module maintainer.
- -------- CONTACT -----------------------------------------------------------
The security contact for Drupal can be reached at security at drupal.org [4]
or via the form at http://drupal.org/contact [5].
[1] http://drupal.org/node/592470
[2] http://drupal.org/user/39422
[3] http://drupal.org/user/282446
[4] http://drupal.org
[5] http://drupal.org/contact
* Advisory ID: DRUPAL-SA-CONTRIB-2009-069
* Project: Shared Sign On (third-party module)
* Version: 5.x, 6.x
* Date: 2009 September 30
* Security risk: Critical
* Exploitable from: Remote
* Vulnerability: Multiple vulnerabilities
- -------- DESCRIPTION -------------------------------------------------------
The Shared Sign On module enables users to log into one Drupal site and be
automatically logged into multiple related Drupal sites. The module suffers
multiple vulnerabilities, including Cross Site Request Forgeries (CSRF [1])
and Session fixation problem (Session Fixation [2]). This problem allows an
attacker to hijack the account of a logged in user by tricking them into
visiting a seemingly innocent page.
- -------- VERSIONS AFFECTED -------------------------------------------------
* Versions of Shared Sign On for both Drupal 5.x and Drupal 6.x
Drupal core is not affected. If you do not use the contributed Shared Sign On
module, there is nothing you need to do.
- -------- SOLUTION ----------------------------------------------------------
The Shared Sign On module is marked as un-supported. A separate project
called Single Sign On [3] has been created as a replacement. Download the
Single Sign On module and carefully read the README.txt as there is a risk of
breaking a site if instructions are not carried out correctly.
- -------- REPORTED BY -------------------------------------------------------
* Reported by Jose A. Reyero [4] and Steven Wittens [5].
- -------- FIXED BY ----------------------------------------------------------
* Fixed by Steven Wittens [6] of Strutta Inc. and Jakub Suchy [7] of Drupal
Security team and Heine Deelstra [8] of Drupal Security Team.
- -------- CONTACT -----------------------------------------------------------
The security contact 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://en.wikipedia.org/wiki/Session_fixation
[3] http://drupal.org/project/sso
[4] http://drupal.org/user/4299
[5] http://drupal.org/user/10
[6] http://drupal.org/user/10
[7] http://drupal.org/user/31977
[8] http://drupal.org/user/17943
- --------------------------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
iD8DBQFKxBidNVH5XJJInbgRAneeAJ4xwu688DXu+4X5Cf6h0onGEtFg6QCcDFRT
jMf4Wh6qQm58xKCQtxwbJ98=
=VEEC
-----END PGP SIGNATURE-----