Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2009.1299.2
Drupal third-party modules: Multiple Vulnerabilities
7 October 2009
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: OpenID (third-party module)
Comment RSS (third-party module)
Date (third-party module)
Publisher: Drupal
Operating System: UNIX variants (UNIX, Linux, OSX)
Windows
Impact/Access: Cross-site Request Forgery -- Existing Account
Cross-site Scripting -- Existing Account
Read-only Data Access -- Remote/Unauthenticated
Unauthorised Access -- Existing Account
Resolution: Patch/Upgrade
CVE Names: CVE-2009-3568
Original Bulletin:
http://drupal.org/node/579478
http://drupal.org/node/579280
http://drupal.org/node/579144
Comment: This bulletin references three (3) Drupal Advisories.
Revision History: October 7 2009: CVE reference added
September 17 2009: Initial Release
- --------------------------BEGIN INCLUDED TEXT--------------------
* Advisory ID: DRUPAL-SA-CONTRIB-2009-059
* Project: OpenID (third-party module)
* Version: 5.x
* Date: 2009-September-16
* Security risk: Critical
* Exploitable from: Remote
* Vulnerability: Impersonation, cross site request forgery
- -------- DESCRIPTION
- ---------------------------------------------------------
The contributed OpenID module for Drupal 5 allows users to create an account
or log into a Drupal site using one or more OpenID identities. The module
does not correctly implement Form API for the form that allows one to link
user accounts with OpenID identifiers. A malicious user is therefore able to
use cross site request forgeries [1] to add attacker controlled OpenID
identities to existing accounts. These OpenID identities can then be used to
gain access to the affected accounts.
.... OpenID impersonation
The OpenID module is not a compliant implementation of the OpenID
Authentication 2.0 specification. An implementation error allows a user to
access the account of another user when they share the same OpenID 2.0
provider.
- -------- VERSIONS AFFECTED
- ---------------------------------------------------
* OpenID for Drupal 5.x prior to 5.x-1.3
Drupal 6.x core has a similar issue, see SA-CORE-2009-008 [2] for details.
- -------- SOLUTION
- ------------------------------------------------------------
Upgrade to the latest version:
* If you use OpenID for Drupal 5.x upgrade to OpenID 5.x-1.3 [3]
*Important note*: Some users using OpenID might not be able to use the
existing OpenID associations to login after the upgrade. These users should
use the one time login via password recovery to get access to their user
account and re-add desired associations. These users likely had issues with
OpenID logins prior to the upgrade. See also the OpenID project page [4].
- -------- REPORTED BY
- ---------------------------------------------------------
The OpenID impersonation was reported by Robert Metcalf [5]. The OpenID
association CSRF was reported by Heine Deelstra [6] (*). (*) Member of the
Drupal security team.
- -------- FIXED BY
- ------------------------------------------------------------
The issues were fixed by Heine Deelstra [7].
- -------- 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_request_forgery
[2] http://drupal.org/node/579482
[3] http://drupal.org/node/579470
[4] http://drupal.org/project/openid
[5] http://drupal.org/user/581142
[6] http://drupal.org/user/17943
[7] http://drupal.org/user/17943
_______________________________________________
* Advisory ID: DRUPAL-SA-CONTRIB-2009-058
* Project: Comment RSS (third-party module)
* Version: 5.x, 6.x
* Date: 2009-September-16
* Security risk: Less critical
* Exploitable from: Remote
* Vulnerability: Access bypass
- -------- DESCRIPTION
- ---------------------------------------------------------
The Comment RSS [1] module provides RSS feeds for comments on individual
nodes. The link to this feed contains the node's title. Adding the link to
the RSS feed was not respecting access permissions, potentially exposing
content not available otherwise.
- -------- VERSIONS AFFECTED
- ---------------------------------------------------
* Comment RSS for Drupal 5.x before Comment RSS 5.x-2.2
* Comment RSS for Drupal 6.x before Comment RSS 6.x-2.2
Drupal core is not affected. If you do not use the contributed Comment RSS
module, there is nothing you need to do.
- -------- SOLUTION
- ------------------------------------------------------------
Install the latest version:
* If you use Drupal 5.x upgrade to Comment RSS 5.x-2.2 [2].
* If you use Drupal 6.x upgrade to Comment RSS 6.x-2.2 [3].
See also the Comment RSS [4] project page.
- -------- REPORTED BY
- ---------------------------------------------------------
Dave Reid [5] of the Drupal Security Team [6] and co-maintainer of the
Comment RSS module
- -------- FIXED BY
- ------------------------------------------------------------
Dave Reid [7]
- -------- 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/project/commentrss
[2] http://drupal.org/node/579292
[3] http://drupal.org/node/579290
[4] http://drupal.org/project/commentrss
[5] http://drupal.org/user/53892
[6] http://drupal.org/security-team
[7] http://drupal.org/user/53892
_______________________________________________
* Advisory ID: DRUPAL-SA-CONTRIB-2009-057
* Project: Date (third-party module)
* Version: 5.x, 6.x
* Date: 2009-September-16
* 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 module does not properly escape user data correctly in some
cases when setting the page title. A malicious user with permission to post
date content could attempt a cross site scripting [1] (XSS) attack when
creating or editing content, leading to the user gaining full administrative
access.
- -------- VERSIONS AFFECTED
- ---------------------------------------------------
* Date for Drupal 6.x prior to 6.x-2.4
* Date for Drupal 6.x prior to 5.x-2.8
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.4 [2]
* If you use Date for Drupal 5.x upgrade to Date 5.x-2.8 [3]
See also the Date project page [4].
- -------- REPORTED BY
- ---------------------------------------------------------
The Acquia, Inc. support team
- -------- FIXED BY
- ------------------------------------------------------------
Karen Stevenson [5], 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/579000
[3] http://drupal.org/node/578998
[4] http://drupal.org/project/date
[5] http://drupal.org/user/45874
- --------------------------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
iD8DBQFKzAKlNVH5XJJInbgRAhiCAJ9oB37YeNbZIYf5VAOkj63jjAxZoACfTql7
bstlAwwgN+AoavaxXMZ7oZ0=
=f8AL
-----END PGP SIGNATURE-----