517052 - Advisory ID: DRUPAL-SA-CORE-2009-008

Status: RESOLVED FIXED

(Websites Graveyard :: spreadthunderbird.com, defect)

Description

[Paul Booker]

* Advisory ID: DRUPAL-SA-CORE-2009-008
 * Project: Drupal core
 * Version: 5.x, 6.x
 * Date: 2009-September-16
 * Security risk: Critical
 * Exploitable from: Remote
 * Vulnerability: Multiple vulnerabilities

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

Multiple vulnerabilities and weaknesses were discovered in Drupal.
.... OpenID association cross site request forgeries

The OpenID module in Drupal 6 allows users to create an account or log into a
Drupal site using one or more OpenID identities. The core OpenID module does
not correctly implement Form API for the form that allows one to link user
accounts with OpenID identifiers. A malicious user is therefore able to use
cross site request forgeries [1] to add attacker controlled OpenID identities
to existing accounts. These OpenID identities can then be used to gain access
to the affected accounts. This issue affects Drupal 6.x only.
.... OpenID impersonation

The OpenID module is not a compliant implementation of the OpenID
Authentication 2.0 specification. An implementation error allows a user to
access the account of another user when they share the same OpenID 2.0
provider. This issue affects Drupal 6.x only.
.... File upload

File uploads with certain extensions are not correctly processed by the File
API. This may lead to the creation of files that are executable by Apache.
The .htaccess that is saved into the files directory by Drupal should
normally prevent execution. The files are only executable when the server is
configured to ignore the directives in the .htaccess file. This issue affects
Drupal 6.x only.
.... Session fixation

Drupal doesn't regenerate the session ID when an anonymous user follows the
one time login link used to confirm email addresses and reset forgotten
passwords. This enables a malicious user to fix and reuse the session id of a
victim under certain circumstances. This issue affects Drupal 5.x only.
-------- VERSIONS AFFECTED ---------------------------------------------------

 * Drupal 6.x before version 6.14.
 * Drupal 5.x before version 5.20.

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

Install the latest version:
 * If you are running Drupal 6.x then upgrade to Drupal 6.14 [2].
 * If you are running Drupal 5.x then upgrade to Drupal 5.20 [3].

If you are unable to upgrade immediately, you can apply a patch to secure
your installation until you are able to do a proper upgrade. Theses patches
fix the security vulnerabilities, but do not contain other fixes which were
released in Drupal 6.14 or Drupal 5.20.
 * To patch Drupal 6.13 use SA-CORE-2009-008-6.13.patch [4].
 * To patch Drupal 5.19 use SA-CORE-2009-008-5.19.patch [5].

*Important note*: Some users using OpenID might not be able to use the
existing OpenID associations to login after the upgrade. These users should
use the one time login via password recovery to get access to their user
account and re-add desired associations. These users likely had issues with
OpenID logins prior to the upgrade.
-------- REPORTED BY ---------------------------------------------------------

The session fixation issue was reported by Noel Sharpe [6]. OpenID
impersonation was reported by Robert Metcalf [7]. OpenID association CSRF was
reported by Heine Deelstra [8] (*). The file upload issue was reported by
Heine Deelstra [9] (*). (*) Member of the Drupal security team
-------- FIXED BY ------------------------------------------------------------

The session fixation issue was fixed by Jakub Suchy [10]. The OpenID and file
upload issues were fixed by Heine Deelstra [11].
-------- CONTACT -------------------------------------------------------------

The security team 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_request_forgery
[2] http://ftp.drupal.org/files/projects/drupal-6.14.tar.gz
[3] http://ftp.drupal.org/files/projects/drupal-5.20.tar.gz
[4] http://drupal.org/files/sa-core-2009-008/SA-CORE-2009-008-6.13.patch
[5] http://drupal.org/files/sa-core-2009-008/SA-CORE-2009-008-5.19.patch
[6] http://drupal.org/user/551958
[7] http://drupal.org/user/581142
[8] http://drupal.org/user/17943
[9] http://drupal.org/user/17943
[10] http://drupal.org/user/31977
[11] http://drupal.org/user/17943

_______________________________________________
Security-news mailing list
[e-mail]
http://lists.drupal.org/listinfo/security-news

Comment 1

[Philippe M. Chiasson (:gozer)]

Package built and deployed in staging

=============================================================================
 Package                 Arch       Version          Repository        Size  
=============================================================================
Updating:
 drupal                  noarch     6.14-1.centos5   momo-testing     1.1 M

Comment 2

[Paul Booker]

Thanks. Please push changes through to production.

Comment 3

[Philippe M. Chiasson (:gozer)]

Production updated and restarted. Please verify and close this bug

Comment 4

[Paul Booker]

Drupal core has no been upgraded on production, seems to be working fine.