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  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Date: Wed, 19 Dec 2012 21:27:08 +0000 (UTC)
Subject: [Security-news] SA-CONTRIB-2012-174 - Context -
	Information	Disclosure

View online:

  * 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.


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


  * 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
  * 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


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


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

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


Security-news mailing list
Unsubscribe at

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

Powered by blists - more mailing lists