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

* Advisory ID: DRUPAL-SA-CONTRIB-2015-175 * Project: Block Class [1] (third-party module) * Version: 7.x * Date: 2015-December-16 * Security risk: 19/25 ( Critical) AC:None/A:Admin/CI:All/II:All/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting

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

This module enables you to add custom classes to blocks. The module doesn't sufficiently scrub class names written by a malicious block class administrator. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Administer block classes".

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

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

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

* block_class 7.x-2.x versions prior to 7.x-2.2.

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

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

Install the latest version:

* If you use the block_class module for Drupal 7.x, upgrade to block_class 7.x-2.2 [5]

Also see the Block Class [6] project page.

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

* Neil Drumm [7] of the Drupal Security Team

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

* Berend de Boer [8] the module maintainer

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

* Ben Dougherty [9] of the Drupal Security Team * Owen Barton [10] 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 [11].

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

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

[1] https://www.drupal.org/project/block_class [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/block_class [5] https://www.drupal.org/node/2636498 [6] https://www.drupal.org/project/block_class [7] https://www.drupal.org/user/23 [8] https://www.drupal.org/user/143552 [9] https://www.drupal.org/user/1852732 [10] https://www.drupal.org/user/19668 [11] https://www.drupal.org/contact [12] https://www.drupal.org/security-team [13] https://www.drupal.org/writing-secure-code [14] https://www.drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity