lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date: Wed, 23 Oct 2013 18:12:44 +0000 (UTC)
Subject: [Security-news] SA-CONTRIB-2013-081 - Spaces -
	Access bypass

View online:

  * Advisory ID: DRUPAL-SA-CONTRIB-2013-081
  * Project: Spaces [1] (third-party module)
  * Version: 6.x
  * Date: 2013-10-23
  * Security risk: Less critical [2]
  * Exploitable from: Remote
  * Vulnerability: Access bypass

-------- DESCRIPTION  

This module enables you to make configuration options generally available
only at the sitewide level to be configurable and overridden by individual
"spaces" on a Drupal site.

The spaces submodule, Spaces OG, doesn't properly handle deleting of organic
group group spaces when the option to move to a new group is selected.
Instead of moving the content to a new group, the content is left orphaned,
and for deleted private groups, that content will then be viewable by anyone
with "access content" permission when the site's or content's access is

The issue is mitigated by needing to be using the submodule spaces OG, and
needing the site users to be in the situation of deleting a group and using
that move option, and needing the content's access to be rebuilt.


  * /A CVE identifier [3] will be requested, and added upon issuance, in
    accordance with Drupal Security Team processes./


  * Spaces 6.x-3.x versions prior to 6.x-3.7.

Drupal core is not affected. If you do not use the contributed Spaces [4]
module, there is nothing you need to do.

-------- SOLUTION  

Install the latest version:

  * If you use the Spaces module for Drupal 6.x, upgrade to Spaces 6.x-3.7 [5]

Also see the Spaces [6] project page.

-------- REPORTED BY  

  * Hunter Fox [7] of the Drupal Security Team

-------- FIXED BY  

  * Tobby Hagler [8] a module maintainer
  * Hunter Fox [9] of the Drupal Security Team, module maintainer.


  * Hunter Fox [10] of the Drupal Security Team


The Drupal security team can be reached at security at or via the
contact form at [11].

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


Security-news mailing list
Unsubscribe at

Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia -

Powered by blists - more mailing lists