Message-Id: <20121219212708.304AE110049@www7.drupal.org>
Date: Wed, 19 Dec 2012 21:27:08 +0000 (UTC)
From: security-news@...pal.org
To: security-news@...pal.org
Subject: [Security-news] SA-CONTRIB-2012-174 - Context -
	Information	Disclosure

View online: http://drupal.org/node/1870550

  * Advisory ID: DRUPAL-SA-CONTRIB-2012-174
  * Project: Context [1] (third-party module)
  * Version: 6.x, 7.x
  * Date: 2012-12-19
  * Security risk: Less critical [2]
  * Exploitable from: Remote
  * Vulnerability: Information Disclosure

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

Context has functionality that renders block content for use with its inline
editor. When these requests are made the context module does not sufficiently
ensure that users have access to the block. A malicious user could send a
specially crafted request and get access to block content they should not be
able to see.

This vulnerability is mitigated by the fact that an attacker must know the
identifiers for the block containing sensitive information and that the
block's code must render that sensitive information when requested by a user
without privileges to see this information.


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

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

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

  * Context 6.x-3.x versions prior to 6.x-3.1.
  * Context 7.x-3.x versions prior to 7.x-3.0-beta6.

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

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

Install the latest version:

  * If you use the Context module for Drupal 6.x, upgrade to Context 6.x-3.1
    [5]
  * If you use the Context module for Drupal 7.x, upgrade to Context
    7.x-3.0-beta6 [6]

Also see the Context [7] project page.

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

  * Fox (hefox) [8] of the Drupal Security Team

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

  * Fox (hefox) [9] the module maintainer
  * tekante [10] the module maintainer

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

  * Fox (hefox) [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 http://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].


[1] http://drupal.org/project/context
[2] http://drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] http://drupal.org/project/context
[5] http://drupal.org/node/1870518
[6] http://drupal.org/node/1869910
[7] http://drupal.org/project/context
[8] http://drupal.org/user/426416
[9] http://drupal.org/user/426416
[10] http://drupal.org/user/640024
[11] http://drupal.org/user/426416
[12] http://drupal.org/contact
[13] http://drupal.org/security-team
[14] http://drupal.org/writing-secure-code
[15] http://drupal.org/security/secure-configuration

_______________________________________________
Security-news mailing list
Security-news@...pal.org
Unsubscribe at http://lists.drupal.org/mailman/listinfo/security-news

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

Powered by blists - more mailing lists