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

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

                               ESB-2010.0881
A vulnerability has been identified in memcache (Drupal third-party module)
                             30 September 2010

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

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

Product:           memcache (Drupal third-party module)
Publisher:         Drupal
Operating System:  Windows
                   UNIX variants (UNIX, Linux, OSX)
Impact/Access:     Cross-site Scripting     -- Remote with User Interaction
                   Administrator Compromise -- Remote with User Interaction
Resolution:        Patch/Upgrade

Original Bulletin: 
   http://drupal.org/node/927016

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

  * Advisory ID: DRUPAL-SA-CONTRIB-2010-098
  * Project: memcache (third-party module)
  * Version: 5.x, 6.x
  * Date: 2010-September-29
  * Security risk: Moderately critical
  * Exploitable from: Remote
  * Vulnerability: Access bypass, Cross-Site Scripting

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

The Memcache project [1] provides an alternative cache backend which works
with memcached program to speed up high traffic sites.

The memcache backend caches the current $user object a little too
aggressively, which can lead to a role change not being recognized until the
user logs in again.

The memcache_admin module does not sanitize some of the user supplied data
before displaying it, leading to a Cross Site Scripting (XSS [2])
vulnerability which can be used by a malicious user to gain full
administrative access.

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

  * Memcache for Drupal 6.x versions prior to 6.x-1.6
  * Memcache for Drupal 5.x versions prior to 5.x-1.10

Drupal core is not affected. If you do not use the contributed Memcache [3]
backend there is nothing you need to do.

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

Install the latest version:

  * If you use the Memcache for Drupal 6.x, upgrade to Memcache 6.x-1.6 [4]
  * If you use the Memcache for Drupal 5.x, upgrade to Memcache 5.x-2.10 [5]

See also the Memcache project page [6].

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

  * Justin James Grevich (jgrevich) [7]
  * Moshe Weitzman [8], of the Drupal Security Team

- -------- FIXED BY ------------------------------------------------------------

  * Robert Douglass (robertDouglass) [9], module maintainer
  * Moshe Weitzman [10], of the Drupal Security Team

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

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


[1] http://drupal.org/project/memcache
[2] http://en.wikipedia.org/wiki/Cross-site_scripting
[3] http://drupal.org/project/memcache
[4] http://drupal.org/node/926474
[5] http://drupal.org/node/926478
[6] http://drupal.org/project/memcache
[7] http://drupal.org/user/355156
[8] http://drupal.org/user/31977
[9] http://drupal.org/user/5449
[10] http://drupal.org/user/23
[11] http://drupal.org/security-team
[12] http://drupal.org/contact

_______________________________________________

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

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

iD8DBQFMo+oQ/iFOrG6YcBERAqUMAJwP7s8AauKiiM5s2gLms6IItaeg8gCfTT1J
gqMvqjnzECHiuii3FzZryp8=
=HTBg
-----END PGP SIGNATURE-----