kp112 Posted February 20, 2014 Report Posted February 20, 2014 (edited) Drupal Maestro third party module version 7.x suffers from a cross site scripting vulnerability.View online: https://drupal.org/node/2200453 * Advisory ID: DRUPAL-SA-CONTRIB-2014-021 * Project: Maestro [1] (third-party module) * Version: 7.x * Date: 2014-February-19 * Security risk: Less critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting-------- DESCRIPTION---------------------------------------------------------The Maestro module enables you to create complex workflows, automatingbusiness processes.The module doesn't sufficiently filter Role or Organic Group names whendisplaying them in the workflow details.This vulnerability is mitigated by the fact that an attacker must have a rolewith the permission to create Drupal Roles or Organic Groups.-------- CVE IDENTIFIER(S) ISSUED-------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./-------- VERSIONS AFFECTED--------------------------------------------------- * Maestro 7.x-1.x versions prior to 7.x-1.4.Drupal core is not affected. If you do not use the contributed Maestro [4]module, there is nothing you need to do.-------- SOLUTION------------------------------------------------------------Install the latest version: * If you use the Maestro module for Drupal 7.x, upgrade to Maestro 7.x-1.4 [5]Also see the Maestro [6] project page.-------- REPORTED BY--------------------------------------------------------- * Aron Novak [7]-------- FIXED BY------------------------------------------------------------ * Aron Novak [8], the reporter * Randy Kolenko [9] the module maintainer-------- COORDINATED BY------------------------------------------------------ * Greg Knaddison [10] of the Drupal Security Team * Michael Hess [11] of the Drupal Security Team-------- CONTACT AND MORE INFORMATION----------------------------------------The Drupal security team can be reached at security at drupal.org or via thecontact form at http://drupal.org/contact [12].Learn more about the Drupal Security team and their policies [13], writingsecure code for Drupal [14], and securing your site [15].Follow the Drupal Security Team on Twitter athttps://twitter.com/drupalsecurity [16][1] http://drupal.org/project/maestro[2] http://drupal.org/security-team/risk-levels[3] http://cve.mitre.org/[4] http://drupal.org/project/maestro[5] https://drupal.org/node/2013653[6] http://drupal.org/project/maestro[7] http://drupal.org/user/61864[8] http://drupal.org/user/61864[9] http://drupal.org/user/704970[10] https://drupal.org/user/36762[11] https://drupal.org/user/102818/[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[16] https://twitter.com/drupalsecurity Edited February 20, 2014 by kp112 Quote
