[39068] in bugtraq

home help back first fref pref prev next nref lref last post

[DRUPAL-SA-2005-001] New Drupal release fixes critical security issue

daemon@ATHENA.MIT.EDU (Uwe Hermann)
Fri Jun 3 14:17:43 2005

Date: Fri, 3 Jun 2005 12:47:42 +0200
From: Uwe Hermann <uwe@hermann-uwe.de>
To: bugtraq@securityfocus.com
Cc: full-disclosure@lists.grok.org.uk
Message-ID: <20050603104742.GA4176@forest>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="fUYQa+Pmc3FrFX/N"
Content-Disposition: inline


--fUYQa+Pmc3FrFX/N
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

----------------------------------------------------------------------------
Drupal security advisory                                  DRUPAL-SA-2005-001
----------------------------------------------------------------------------
Advisory ID:    DRUPAL-SA-2005-001
Date:           2005-jun-01
Security risk:  highly critical
Impact:         system access
Where:          from remote
Vulnerability:  privilege escalation
----------------------------------------------------------------------------

Description
-----------
The Drupal Security Team has found that the privilege system of Drupal can=
=20
be circumvented in a very special case because an input check is not=20
implemented properly.

Versions affected
-----------------
Drupal 4.4.0, 4.4.1, 4.4.2
Drupal 4.5.0, 4.5.1, 4.5.2
Drupal 4.6.0

Impact
------
If public registration is allowed then it is possible for an attacker
to obtain additional user roles. As a result, an attacker could grant=20
himself administration privileges.

Solution
--------
Either upgrade or disable public registration: =20
- If you are running Drupal 4.4.x, then upgrade to Drupal 4.4.3.
- If you are running Drupal 4.5.2, then upgrade to Drupal 4.5.3.
- If you are running Drupal 4.6.0, then upgrade to Drupal 4.6.1.
- If you cannot upgrade immediately, you can secure your site by=20
  disabling the public registration of Drupal accounts from Drupal's user
  administration screen. Log-in as an administrator, go to "administer >>=
=20
  users >> configure" and set the "Public registrations" option to "Only=20
  site administrators can create new user accounts".

Contact
-------
The security contact for Drupal can be reached at security@drupal.org=20
or using the form at http://drupal.org/contact.


// Uwe Herman, on behalf of the Drupal Security Team.
--=20
Uwe Hermann <uwe@hermann-uwe.de>
http://www.hermann-uwe.de                 | http://www.crazy-hacks.org
http://www.it-services-uh.de              | http://www.phpmeat.org
http://www.unmaintained-free-software.org | http://www.holsham-traders.de

--fUYQa+Pmc3FrFX/N
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCoDVOXdVoV3jWIbQRAscxAKCP0GxxIwInvcEjaoxEDBMbSOE5bgCfc/i/
I7veUhxFppC1O0xI8tpCSyc=
=2kW0
-----END PGP SIGNATURE-----

--fUYQa+Pmc3FrFX/N--

home help back first fref pref prev next nref lref last post