Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2009.1116
Cross-site scripting and Privilege Escalation
vulnerabilities identified in Drupal third-party modules
30 July 2009
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Date (Drupal third-party module)
Calendar (Drupal third-party module)
Bibliography Module (Drupal third-party module)
Live (Drupal third-party module)
Publisher: Drupal
Operating System: UNIX variants (UNIX, Linux, OSX)
Windows
Impact/Access: Increased Privileges -- Existing Account
Resolution: Upgrade
Original Bulletin:
http://drupal.org/node/534636
http://drupal.org/node/534652
http://drupal.org/node/534842
http://drupal.org/node/534914
Comment: This bulletin contains four (4) Drupal Security Advisories.
- --------------------------BEGIN INCLUDED TEXT--------------------
* Advisory ID: DRUPAL-SA-CONTRIB-2009-046
* Project: Date (third-party module)
* Version: 6.x
* Date: 2009-July-29
* Security risk: Moderately critical
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
- -------- DESCRIPTION
- ---------------------------------------------------------
The Date module provides a date CCK field that can be added to any content
type. The Date Tools module that is bundled with Date module does not
properly escape user input when displaying labels for fields on a content
type. A malicious user with the 'use date tools' permission of the Date Tools
sub-module, or the 'administer content types' permission could attempt a
cross site scripting [1] (XSS) attack when creating a new content type,
leading to the user gaining full administrative access.
- -------- VERSIONS AFFECTED
- ---------------------------------------------------
* Date for Drupal 6.x prior to 6.x-2.3
Drupal core is not affected. If you do not use the contributed Date module,
there is nothing you need to do.
- -------- SOLUTION
- ------------------------------------------------------------
Upgrade to the latest version:
* If you use Date for Drupal 6.x upgrade to Date 6.x-2.3 [2]
Note that the 'use date tools' permission has been renamed as 'administer
date tools' to clarify that this is an administrative permission (it allows
the creation of new content types via a wizard form). You will need to
re-assign this permission to any roles that were using it. See also the Date
project page [3].
- -------- REPORTED BY
- ---------------------------------------------------------
Stella Power [4] of the Drupal Security Team
- -------- FIXED BY
- ------------------------------------------------------------
Stella Power [5] and Karen Stevenson [6], the project maintainer.
- -------- 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/Cross-site_scripting
[2] http://drupal.org/node/534332
[3] http://drupal.org/project/date
[4] http://drupal.org/user/66894
[5] http://drupal.org/user/66894
[6] http://drupal.org/user/45874
- ---------------------------------------------------------
* Advisory ID: DRUPAL-SA-CONTRIB-2009-047
* Project: Calendar (third-party module)
* Version: 6.x
* Date: 2009-July-29
* Security risk: Moderately critical
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
- -------- DESCRIPTION
- ---------------------------------------------------------
The Calendar module enables Views module to display any Date module date
field as a calendar. The module does not properly escape user input when
displaying titles of content types that have Date fields. A user with
permission to create new content types (including via the Date module's Date
Tools sub-module) could attempt a cross site scripting [1] (XSS) attack,
leading to the user gaining full administrative access.
- -------- VERSIONS AFFECTED
- ---------------------------------------------------
* Calendar for Drupal 6.x prior to 6.x-2.2
Drupal core is not affected. If you do not use the contributed Calendar
module, there is nothing you need to do.
- -------- SOLUTION
- ------------------------------------------------------------
Upgrade to the latest version:
* If you use Calendar for Drupal 6.x upgrade to Calendar 6.x-2.2 [2]
See also the Calendar project page [3].
- -------- REPORTED BY
- ---------------------------------------------------------
Justin C. Klein Keane [4]
- -------- FIXED BY
- ------------------------------------------------------------
Justin C. Klein Keane [5]
- -------- 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/Cross-site_scripting
[2] http://drupal.org/node/534336
[3] http://drupal.org/project/calendar
[4] http://drupal.org/user/302225
[5] http://drupal.org/user/302225
- ---------------------------------------------------------
* Advisory ID: DRUPAL-SA-CONTRIB-2009-048
* Project: Bibliography Module (third-party module)
* Version: 5.x, 6.x
* Date: 2009-July-29
* Security risk: Moderately critical
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
- -------- DESCRIPTION
- ---------------------------------------------------------
The Bibliography module (Biblio) allows users to manage and display lists of
scholarly publications. The module contains a cross site scripting
vulnerability because it does not properly sanitize output of titles before
display. A user who has the permission to create content displayed by the
Bibliography module could attempt a cross site scripting [1] (XSS) attack
which may lead to the user gaining full administrative access.
- -------- VERSIONS AFFECTED
- ---------------------------------------------------
* Bibliography Module versions 6.x prior to 6.x-1.6
* Bibliography Module versions 5.x prior to 5.x-1.17
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.6 [2]
* If you use the Bibliography Module for Drupal 5.x upgrade to Bibliography
Module 5.x-1.17 [3]
See also the Bibliography Module project page [4].
- -------- REPORTED BY
- ---------------------------------------------------------
Justin Klein Keane [5].
- -------- FIXED BY
- ------------------------------------------------------------
Justin Klein Keane [6] and Ron Jerome [7] (the Bibliography 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/534744
[3] http://drupal.org/node/534752
[4] http://drupal.org/project/biblio
[5] http://drupal.org/user/302225
[6] http://drupal.org/user/302225
[7] http://drupal.org/user/54997
- ---------------------------------------------------------
* Advisory ID: DRUPAL-SA-CONTRIB-2009-049
* Project: Live (third-party module)
* Version: 6.x
* Date: 2009-July-29
* Security risk: Highly critical
* Exploitable from: Remote
* Vulnerability: Impersonation, privilege escalation
- -------- DESCRIPTION
- ---------------------------------------------------------
The Live module provides dynamic previews of content. When editing certain
content (nodes), the current user becomes logged in as the content's original
author.
- -------- VERSIONS AFFECTED
- ---------------------------------------------------
* Live for Drupal 6.x prior to 6.x-1.2
Drupal core is not affected. If you do not use the contributed Live module,
there is nothing you need to do.
- -------- SOLUTION
- ------------------------------------------------------------
Upgrade to the latest version:
* If you use Live for Drupal 6.x upgrade to Live 6.x-1.2 [1]
See also the Live project page [2].
- -------- REPORTED BY
- ---------------------------------------------------------
Roderik Muit [3]
- -------- FIXED BY
- ------------------------------------------------------------
frjo [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] http://drupal.org/node/534976
[2] http://drupal.org/project/live
[3] http://drupal.org/user/8841
[4] http://drupal.org/user/5546
- --------------------------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
iD8DBQFKcQGqNVH5XJJInbgRAnbkAJ9ezQHF+ynf7GIh1LZEnmdvB9U5zgCcCgSB
CHMzr2B8TxypeftkDsNvR1Y=
=PEy2
-----END PGP SIGNATURE-----