-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                  ESB-2008.0885 -- [Win][UNIX/Linux][OSX]
        Talk, Mailhandler (Drupal third-party modules) - Cross site
                         scripting, SQL injection
                             18 September 2008

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:              Talk
                      Mailhandler
Publisher:            Drupal
Operating System:     UNIX variants (UNIX, Linux, OSX)
                      Windows
Impact:               Execute Arbitrary Code/Commands
                      Cross-site Scripting
Access:               Remote/Unauthenticated

Original Bulletin:    http://drupal.org/node/309758
                      http://drupal.org/node/309769

- --------------------------BEGIN INCLUDED TEXT--------------------

- ------------SA-2008-049 - TALK - MULTIPLE VULNERABILITIES------------

  * Advisory ID: DRUPAL-SA-2008-049

  * Project: Talk (third-party module)

  * Version: 5.x, 6.x

  * Date: 2008-September-17

  * Security risk: Moderately critical

  * Exploitable from: Remote

  * Vulnerability: Cross site scripting, Node access bypass

- ------------DESCRIPTION------------

The Talk module for Drupal 5.x and 6.x creates a "Talk" tab for nodes 
in which the comments belonging to the node are displayed.

Two vulnerabilities and weaknesses were discovered in the contributed Talk
module.

CROSS SITE SCRIPTING

The node title is treated as if it was safe text, and is not escaped before
being displayed. This allows users to insert arbitrary HTML and script code 
into the Talk pages. Wikipedia has more information about such cross site 
scripting [http://en.wikipedia.org/wiki/Xss ] (XSS) attacks.

NODE ACCESS BYPASS

To view the comments of a normal node, you must view the node page itself, 
and thus you must always have access to view a node before you can view its
comments. The Talk module bypassed this by displaying comments on a separate
page and not confirming that a user has access to view the node before
displaying the comments.

- ------------VERSIONS AFFECTED------------

  * Talk for Drupal 5.x before version 5.x-1.3

  * Talk for Drupal 6.x before version 6.x-1.5

Drupal core is not affected. If you do not use the contributed Talk module,
there is nothing you need to do.

- ------------SOLUTION------------

Install the latest version:

  * If you currently use Talk 5.x-1.x upgrade to Talk 5.x-1.3 [
http://drupal.org/node/309760 ]

  * If you currently use Talk 6.x-1.x upgrade to Talk 6.x-1.5 [
http://drupal.org/node/309759 ]

See also the Talk project page [ http://drupal.org/project/talk ].

- ------------REPORTED BY------------

  * christefano [ http://drupal.org/user/104 ]

- ------------CONTACT------------

The security contact for Drupal can be reached at security at drupal.org or 
via the form at [ http://drupal.org/contact ].


- ------------SA-2008-050 - MAILHANDLER - SQL INJECTION------------

  * Advisory ID: DRUPAL-SA-2008-050

  * Project: Mailhandler (third-party module)

  * Versions: 5.x and 6.x

  * Date: 2008-September-17

  * Security risk: Critical

  * Exploitable from: Remote

  * Vulnerability: SQL injection

- ------------DESCRIPTION------------

The Mailhandler module allows users to create or edit nodes and comments via
email. One vulnerability was found in the module.

SQL Injection

Mailhandler does not properly use the Drupal database API and inserts values
from mails directly into queries. This can be exploited to perform SQL 
Injection attacks [ http://en.wikipedia.org/wiki/Sql_injection ]. These 
attacks may lead to a malicious user gaining administrator access.

- ------------VERSIONS AFFECTED------------

  * Versions of Mailhandler for Drupal 5.x prior to 5.x-1.4

  * Versions of Mailhandler for Drupal 6.x prior to 6.x-1.4

Drupal core is not affected. If you do not use the Mailhandler module, there 
is nothing you need to do.

- ------------SOLUTION------------

Install the latest version.

  * If you use Mailhandler for Drupal 5.x upgrade to Mailhandler 5.x-1.4 
    [http://drupal.org/node/309771 ]

  * If you use Mailhandler for Drupal 6.x upgrade to Mailhandler 6.x-1.4 
    [http://drupal.org/node/309770 ]

Also see the Mailhandler project page 
[ http://drupal.org/project/mailhandler].

- ------------REPORTED BY------------

  * The SQL injection vulnerability was reported by the module maintainer 
    Zohar Stolar [ http://drupal.org/user/48488 ].

- ------------CONTACT------------

The security contact for Drupal can be reached at security at drupal.org or 
via the form at [ http://drupal.org/contact ] and by selecting the security 
issues category.

- --------------------------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

iQCVAwUBSNGiSih9+71yA2DNAQJcPQP/SSgeE0W7F/jGrK8TLbgur/m52jDiH4ko
TUL3+/ywlosY8JsdNETajdmKp/nQ5+y2OasLGPYT3aR6zGuQhW7ldegVldv977Sj
129XH2Inzs2hPhkvkSjstj7zssZ/DujTixHDBN+sk8+WiKnQj+JYtM9vH5E5m8cI
Naqs+vLwYzk=
=JGrb
-----END PGP SIGNATURE-----