Security-news September 2012

security-news@drupal.org

1 participants
12 discussions

SA-CONTRIB-2012-138 - Exposed Filter Data - Cross Site Scripting (XSS)
by security-news＠drupal.org 05 Sep '12

05 Sep '12

View online: http://drupal.org/node/1775582 * Advisory ID: DRUPAL-SA-CONTRIB-2012-138 * Project: Exposed Filter Data [1] (third-party module) * Version: 6.x * Date: 2012-September-05 * Security risk: Critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Exposed Filter Data facilitates displaying data posted to Views via an exposed filter. The module does not properly sanitize user-supplied data prior to output, leading to a Cross-Site Scripting (XSS) vulnerability. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Exposed Filter Data 6.x-1.x versions prior to 6.x-1.2. Drupal core is not affected. If you do not use the contributed Exposed Filter Data [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Exposed Filter Data module for Drupal 6.x, upgrade to Exposed Filter Data 6.x-1.2 [4]. * The 7.x-1.x branch is not vulnerable. If you use Exposed Filter Data for Drupal 7.x, there is nothing you need to do. Also see the Exposed Filter Data [5] project page. -------- REPORTED BY --------------------------------------------------------- * Joe Tsui [6] * ekes [7] -------- FIXED BY ------------------------------------------------------------ * Shushu Inbar [8], the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Michael Hess (mlhess [9]) of the Drupal Security Team * Ivo Van Geertruyen (mr.baileys [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 http://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]. [1] http://drupal.org/project/exposed_filter_data [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/exposed_filter_data [4] http://drupal.org/node/1774636 [5] http://drupal.org/project/exposed_filter_data [6] https://drupal.org/user/125025 [7] http://drupal.org/user/10083 [8] https://drupal.org/user/99513 [9] http://drupal.org/user/102818 [10] http://drupal.org/user/383424 [11] http://drupal.org/contact [12] http://drupal.org/security-team [13] http://drupal.org/writing-secure-code [14] http://drupal.org/security/secure-configuration

1 0

SA-CONTRIB-2012-137 - Heartbeat - Cross Site Request Forgery (CSRF) in heartbeat_comments
by security-news＠drupal.org 05 Sep '12

05 Sep '12

View online: http://drupal.org/node/1775470 * Advisory ID: DRUPAL-SA-CONTRIB-2012-137 * Project: Heartbeat [1] (third-party module) * Version: 6.x, 7.x * Date: 2012-September-5 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- This module enables you to display activity for events on a site. The module doesn't sufficiently check the heartbeat comment post values making it possible for an attacker to cause a user to unknowingly make comments. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * heartbeat_comments 6.x-4.x versions prior to 6.x-4.11. * heartbeat_comments 7.x-1.x versions prior to 7.x-1.0. Drupal core is not affected. If you do not use the contributed Heartbeat [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the heartbeat_comments or shouts module for Drupal 6.x, upgrade to heartbeat 6.x-4.12 [4] * If you use the heartbeat_comments module for Drupal 7.x, upgrade to heartbeat 7.x-1.1 [5] Also see the Heartbeat [6] project page. -------- REPORTED BY --------------------------------------------------------- * Greg Knaddison [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Stalski [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [9] of the Drupal Security Team * Matt Chapman [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 http://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]. [1] http://drupal.org/project/heartbeat [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/heartbeat [4] http://drupal.org/node/1774140 [5] http://drupal.org/node/1774160 [6] http://drupal.org/project/heartbeat [7] http://drupal.org/user/36762 [8] http://drupal.org/user/322618 [9] http://drupal.org/user/36762 [10] http://drupal.org/user/143172 [11] http://drupal.org/contact [12] http://drupal.org/security-team [13] http://drupal.org/writing-secure-code [14] http://drupal.org/security/secure-configuration

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Security-news September 2012