[39364] in bugtraq

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

[DRUPAL-SA-2005-002] Drupal 4.6.2 / 4.5.4 fixes input validation issue

daemon@ATHENA.MIT.EDU (Uwe Hermann)
Thu Jun 30 13:37:34 2005

X-Envelope-To: bugtraq@securityfocus.com
Date: Wed, 29 Jun 2005 23:38:46 +0200
From: Uwe Hermann <uwe@hermann-uwe.de>
To: bugtraq@securityfocus.com, full-disclosure@lists.grok.org.uk,
        phpsec@phparch.com
Message-ID: <20050629213846.GA480@forest>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8"
Content-Disposition: inline


--ibTvN161/egqYuK8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

----------------------------------------------------------------------------
Drupal security advisory                                  DRUPAL-SA-2005-002
----------------------------------------------------------------------------
Advisory ID:    DRUPAL-SA-2005-002
Date:           2005-jun-29
Security risk:  highly critical
Impact:         system access
Where:          from remote
Vulnerability:  arbitrary PHP code execution
----------------------------------------------------------------------------

Description
-----------
Kuba Zygmunt discovered a flaw in the input validation routines of Drupal's
filter mechanism.  An attacker could execute arbitrary PHP code on a target=
=20
site when public comments or postings are allowed.

Versions affected
-----------------
Drupal 4.5.0, 4.5.1, 4.5.2, 4.5.3
Drupal 4.6.0, 4.6.1

Solution
--------
Either disable public comments and postings, or upgrade to the latest Drupal
version:
- If you cannot upgrade immediately, you can secure your site by disabling
  public postings and comments.  Log in as an administrator, go to
  "administer >> access control" and make sure that untrusted roles don't
  have the permissions to submit or edit content.
- If you are running Drupal 4.5.x, then upgrade to Drupal 4.5.4.
- If you are running Drupal 4.6.x, then upgrade to Drupal 4.6.2.

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


// Uwe Hermann, 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

--ibTvN161/egqYuK8
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)

iD8DBQFCwxTmXdVoV3jWIbQRAr1PAJ9zzJjUmBGUbQDlQUTMYhOgHsalpgCfUIdY
pByQlUhEWr14w8CnvQEhu34=
=usID
-----END PGP SIGNATURE-----

--ibTvN161/egqYuK8--

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