[Security-news] Open Atrium - Moderately Critical - Access Bypass - SA-CONTRIB-2016-003

security-news at drupal.org security-news at drupal.org
Wed Jan 27 20:24:03 UTC 2016


View online: https://www.drupal.org/node/2657654

   * Advisory ID: DRUPAL-SA-CONTRIB-2016-003
   * Project: Open Atrium [1]     (third-party module)
   * Version: 7.x
   * Date: 2016-January-27
   * Security risk: 13/25 ( Moderately Critical)
     AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Uncommon [2]
   * Vulnerability: Access bypass

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

Open Atrium allows you to control access via a hierarchy of public and
private spaces and sub-spaces.  If a public sub-space is created within a
private parent-space, the content nodes of the public sub-space are
accessible to users who are not members of the parent private space.

This issue only affects sites that use private sub-spaces.


-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------

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

-------- VERSIONS AFFECTED
---------------------------------------------------

   * Open Atrium 7.x-2.x versions prior to 7.x-2.53.

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

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

   * Upgrade to the latest version, 7.x-2.53 [5]

If you are not able to fully upgrade to the latest version, ensure private
sub-spaces are directly marked as private and are not seen publicly in a
private parent space.

Also see the Open Atrium [6] project page.

-------- REPORTED BY
---------------------------------------------------------

   * Mike Potter [7], Open Atrium maintainer.

-------- FIXED BY
------------------------------------------------------------

   * Mike Potter [8], Open Atrium maintainer.
   * Scott Henry [9], Open Atrium co-maintainer.

-------- COORDINATED BY
------------------------------------------------------

   * Hunter Fox [10] of the Drupal Security Team
   * Ben Jeavons [11] 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 https://www.drupal.org/contact [12].

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

Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [16]


[1] https://www.drupal.org/project/openatrium
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/openatrium
[5] https://www.drupal.org/node/2657640
[6] https://www.drupal.org/project/openatrium
[7] https://www.drupal.org/u/mpotter
[8] https://www.drupal.org/u/mpotter
[9] https://www.drupal.org/u/scottalan
[10] https://www.drupal.org/user/426416
[11] https://www.drupal.org/u/coltrane
[12] https://www.drupal.org/contact
[13] https://www.drupal.org/security-team
[14] https://www.drupal.org/writing-secure-code
[15] https://www.drupal.org/security/secure-configuration
[16] https://twitter.com/drupalsecurity



More information about the Security-news mailing list