FEDORA-EPEL-2011-3672

security update in Fedora EPEL 6 for drupal7

Status: stable 8 years ago

Remember to log in as user 1 prior to the RPM update, to perform the DB upgrade via http://yoursite/update.php.

  • Advisory ID: DRUPAL-SA-CORE-2011-002
  • Project: Drupal core [1]
  • Version: 7.x
  • Date: 2011-JUNE-29
  • Security risk: Highly critical [2]
  • Exploitable from: Remote
  • Vulnerability: Access bypass

-------- DESCRIPTION

.... Access bypass in node listings

Listings showing nodes but not JOINing the node table show all nodes regardless of restrictions imposed by the node_access system. In core, this affects the taxonomy and the forum subsystem.

Note that fixing this issue in contributed modules requires a backwards-compatible API change for modules listing nodes. See http://drupal.org/node/1204572 [3] for more details.

This issue affects Drupal 7.x only.

-------- VERSIONS AFFECTED

  • Drupal 7.0, 7.1 and 7.2.

-------- SOLUTION

Install the latest version:

  • If you are running Drupal 7.x then upgrade to Drupal 7.3 or 7.4.

The Security Team has released both a pure security update without other bug fixes and a security update combined with other bug fixes and improvements. You can choose to either only include the security update for an immediate fix (which might require less quality assurance and testing) or more fixes and improvements alongside the security fixes by choosing between Drupal 7.3 and Drupal 7.4. Read the announcement [4] for more information.

See also the Drupal core [5] project page.

-------- REPORTED BY

  • The access bypass was reported independently by numerous people, including Sascha Grossenbacher [6], Khaled Alhourani [7], and Ben Ford [8].

-------- FIXED BY

  • The access bypass was fixed by Károly Négyesi [9], member of the Drupal security team

-------- CONTACT AND MORE INFORMATION

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

Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13].

[1] http://drupal.org/project/drupal [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/node/1204572 [4] http://drupal.org/drupal-7.4 [5] http://drupal.org/project/drupal [6] http://drupal.org/user/214652 [7] http://drupal.org/user/265439 [8] http://drupal.org/user/12534 [9] http://drupal.org/user/9446 [10] http://drupal.org/contact [11] http://drupal.org/security-team [12] http://drupal.org/writing-secure-code [13] http://drupal.org/security/secure-configuration

Comments 6

This update has been submitted for testing by limb.

This update has been pushed to testing

Seems fine with new installation.

karma: +1

This update has reached 14 days in testing and can be pushed to stable now if the maintainer wishes

This update has been submitted for stable by limb.

This update has been pushed to stable

Add Comment & Feedback

Please login to add feedback.

Content Type
RPM
Status
stable
Test Gating
Submitted by
Update Type
security
Update Severity
unspecified
Karma
+1
stable threshold: 3
unstable threshold: -3
Autopush (karma)
Disabled
Autopush (time)
Disabled
Dates
submitted 8 years ago
in testing 8 years ago
in stable 8 years ago

Related Bugs 2

00 #706736 Put modules and themes directories under /etc/drupal7/all/
00 #717874 CVE-2011-2687 Remote access bypass vulnerability in Drupal 7

Automated Test Results