Date: 04 March 2010
Click here for printable version
Click here for PGP verifiable version
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2010.0222
Drupal Third-party modules : Multiple vulnerabilities
4 March 2010
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: AddThis Button (third-party module)
Internationalization (third-party module)
Workflow (third-party module)
eTracker (third-party module)
Publisher: Drupal
Operating System: UNIX variants (UNIX, Linux, OSX)
Windows
Impact/Access: Execute Arbitrary Code/Commands -- Remote/Unauthenticated
Cross-site Scripting -- Remote with User Interaction
Resolution: Patch/Upgrade
Original Bulletin:
http://drupal.org/node/731568
http://drupal.org/node/731632
http://drupal.org/node/731624
http://drupal.org/node/731682
Comment: This bulletin contains four (4) Drupal security advisories.
- --------------------------BEGIN INCLUDED TEXT--------------------
* Advisory ID: DRUPAL-SA-CONTRIB-2010-021
* Project: AddThis Button (third-party module)
* Version: 6.x, 5.x
* Date: 2010-March-03
* Security risk: Less Critical
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
- -------- DESCRIPTION
- ---------------------------------------------------------
The AddThis module provides an easy way to share content to over 230
supported services such as Facebook, Email and Twitter. The module did not
sanitize some user-supplied data before displaying it, leading to a Cross
Site Scripting (XSS [1]) vulnerability. Only users with the 'administer
addthis' permission were able to exploit this vulnerability.
- -------- VERSIONS AFFECTED
- ---------------------------------------------------
* AddThis Button module prior to 6.x-2.9 [2]
* AddThis Button module prior to 5.x-2.2 [3]
Drupal core is not affected. If you do not use the contributed AddThis Button
module, there is nothing you need to do.
- -------- SOLUTION
- ------------------------------------------------------------
Install the latest version:
* If you use AddThis Button for Drupal 5.x upgrade to AddThis Button 6.x-2.9
[4].
* If you use AddThis Button for Drupal 6.x upgrade to AddThis Button 5.x-2.2
[5].
See also the AddThis Button project page [6].
- -------- REPORTED BY
- ---------------------------------------------------------
* Vesa Palmu (wesku [7]), the module maintainer
* Dave Hansen-Lange (dalin [8])
- -------- FIXED BY
- ------------------------------------------------------------
* Vesa Palmu (wesku [9]), the module 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/731576
[3] http://drupal.org/node/731578
[4] http://drupal.org/node/731576
[5] http://drupal.org/node/731578
[6] http://drupal.org/project/addthis
[7] http://drupal.org/user/75070
[8] http://drupal.org/user/18981
[9] http://drupal.org/user/75070
_______________________________________________
* Advisory ID: DRUPAL-SA-CONTRIB-2010-022
* Project: Internationalization (third-party module)
* Version: 6.x-1.x 5.x-2.x
* Date: 2010-March-03
* Security risk: Highly Critical
* Exploitable from: Remote
* Vulnerability: Arbitrary code execution
- -------- DESCRIPTION
- ---------------------------------------------------------
The Internationalization module enables translation of user defined strings
using Drupal's locale interface. Some of these user defined strings have
Input formats associated with them. As translators can translate texts before
they go through the Input filters, using some filters like the PHP filter for
such strings allows translators to add arbitrary PHP code as part of the
translated string, which will be executed by the filters. Other filters
besides PHP filter may be dangerous too and as a general rule translators
shouldn't be allowed to translate text with Input filters they're not allowed
to use.
- -------- VERSIONS AFFECTED
- ---------------------------------------------------
* Internationalization 6.x-2.x prior to 6.x-1.3 [1]
* Internationalization 5.x-2.x prior to 5.x-2.6 [2]
Drupal core is not affected. If you do not use the contributed
Internationalization module, there is nothing you need to do. Also if you are
not using Internationalization's 'String translation' (i18nstrings) module
together with 'Views translation' (i18nviews) or 'Block translation'
(i18nblocks) you don't need to update, though it is advisable to run the
latest version.
- -------- SOLUTION
- ------------------------------------------------------------
Install the latest version:
* If you use Internationalization for Drupal 6.x upgrade to
Internationalization 6.x-1.3 [3] and follow these steps:
* Visit the /Administer > Site configuration > Languages > Configure >
String translation/ page
* Check the Input formats that are safe for translators and the Safe text
groups if you are using other contributed modules that rely on
Internationalization's String translation features.
Note: Checking all of them will cause the module to work as previous
versions overriding all security checks, which may be useful if you are
not using dangerous Input filters or translators are trusted users.
* Go to /Administer > Site building > Translate interface > Refresh/ and
refresh strings for all the text groups. This will remove dangerous
texts from the translation system. They cannot be translated anymore.
* If you use Internationalization for Drupal 5.x upgrade to
Internationalization 5.x-2.6 [4]. The new version will just drop the
'Views translation' feature. There are no plans to update this feature to
work safely with Internationalization 5.x
See also the Internationalization project page [5].
- -------- REPORTED BY
- ---------------------------------------------------------
* sinasquax [6]
* Antonio Ospite [7]
- -------- FIXED BY
- ------------------------------------------------------------
* Jose Reyero [8], the module 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://drupal.org/node/731590
[2] http://drupal.org/node/731586
[3] http://drupal.org/node/731590
[4] http://drupal.org/node/731586
[5] http://drupal.org/project/i18n
[6] http://drupal.org/user/460020
[7] http://drupal.org/user/234884
[8] http://drupal.org/user/4299
_______________________________________________
* Advisory ID: DRUPAL-SA-CONTRIB-2010-023
* Project: Workflow (third-party module)
* Version: 6.x, 5.x
* Date: 2010-March-03
* Security risk: Less Critical
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
- -------- DESCRIPTION
- ---------------------------------------------------------
When used in combination with the Token module, the Workflow module does not
escape the text entered into the Comment field of the workflow fieldset on
the node form. This allows a user with the permission to change the workflow
state of a node to perform a Cross Site Scripting (XSS [1]) attack if a
workflow has been assigned to that content type and the option to "Show a
comment field in the workflow section of the editing form" or "Show a comment
field in the workflow section of the workflow tab form" is checked in the
workflow settings. Both are checked by default.
- -------- VERSIONS AFFECTED
- ---------------------------------------------------
* Workflow 6.x-1.x prior to 6.x-1.4 [2]
* Workflow 5.x-2.x prior to 5.x-2.6 [3]
Drupal core is not affected. If you do not use the contributed Workflow
module and the contributed Token module, there is nothing you need to do.
- -------- SOLUTION
- ------------------------------------------------------------
Install the latest version:
* If you use Workflow 6.x-1.x, upgrade to Workflow 6.x-1.4 [4]
* If you use Workflow 5.x-2.x, upgrade to Workflow 5.x-2.6 [5]
See also the Workflow project page [6].
- -------- REPORTED BY
- ---------------------------------------------------------
* George Cassie (gcassie [7])
- -------- FIXED BY
- ------------------------------------------------------------
* John VanDyk (jvandyk [8]), module 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/731648
[3] http://drupal.org/node/731644
[4] http://drupal.org/node/731648
[5] http://drupal.org/node/731644
[6] http://drupal.org/project/workflow
[7] http://drupal.org/user/80260
[8] http://drupal.org/user/2375
_______________________________________________
* Advisory ID: DRUPAL-SA-CONTRIB-2010-024
* Project: eTracker (third-party module)
* Version: 6.x-1.1
* Date: 2010-March-03
* Security risk: Moderately Critical
* Exploitable from: Remote
* Vulnerability: Cross Site Scripting
- -------- DESCRIPTION
- ---------------------------------------------------------
The eTracker module provides integration of a Drupal site with the eTracker
web traffic analysis service and takes the current URL as a parameter to
track what pages have been visited. The URL from the browser is forwarded to
JavaScript in the current page, and because the URL wasn't sanitised, it
could have allowed cross-site scripting attacks by appending malicious code
to the URL.
- -------- VERSIONS AFFECTED
- ---------------------------------------------------
* eTracker prior to 6.x-1.2.
Drupal core is not affected. If you do not use the contributed eTracker
module, there is nothing you need to do.
- -------- SOLUTION
- ------------------------------------------------------------
Install the latest version:
* If you use eTracker for Drupal 6.x upgrade to eTracker 6.x-1.2 [1]
See also the eTracker project page [2].
- -------- REPORTED BY
- ---------------------------------------------------------
* Andreas Harder
- -------- FIXED BY
- ------------------------------------------------------------
* Jürgen Haas (jurgenhaas [3]), the module 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://drupal.org/node/731018
[2] http://drupal.org/project/eTracker
[3] http://drupal.org/user/168924
_______________________________________________
- --------------------------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
iD8DBQFLjvYO/iFOrG6YcBERAkOsAJ9I+8JefjQYRTEhyq3DNOevHTPRjQCgtSQY
WEo6WleTqEjJMvPEWTo0lmU=
=d8wP
-----END PGP SIGNATURE-----
|