kp112 Posted February 20, 2014 Report Posted February 20, 2014 Drupal Slickgrid third party module version 7.x suffers from an access bypass vulnerability.View online: https://drupal.org/node/2200491 * Advisory ID: DRUPAL-SA-CONTRIB-2014-22 * Project: Slickgrid [1] (third-party module) * Version: 7.x * Date: 2014-February -22 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access bypass-------- DESCRIPTION---------------------------------------------------------The Slickgrid module is an implementation of the jQuery slickgrid plugin, alightening fast JavaScript grid/spreadsheet. It defines a slickgrid viewstyle, so all data can be output as an editable grid.The module doesn't check access sufficiently, allowing users to edit andchange field values of nodes they should not have access to change.-------- CVE IDENTIFIER(S) ISSUED-------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./-------- VERSIONS AFFECTED--------------------------------------------------- * Slickgrid 7.x-1.x versionsDrupal core is not affected. If you do not use the contributed Slickgrid [4]module, there is nothing you need to do.-------- SOLUTION------------------------------------------------------------Install the latest version: * If you use the Slickgrid module for Drupal 7.x, upgrade to Slickgrid 7.x-2.0 [5]Also see the Slickgrid [6] project page.-------- REPORTED BY--------------------------------------------------------- * Tim Wood [7]-------- FIXED BY------------------------------------------------------------ * Ben Scott [8] * Simon Rycroft [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/slickgrid[2] http://drupal.org/security-team/risk-levels[3] http://cve.mitre.org/[4] http://drupal.org/project/slickgrid[5] https://drupal.org/node/2200475[6] http://drupal.org/project/slickgrid[7] http://drupal.org/user/23373[8] http://drupal.org/user/149339[9] http://drupal.org/user/151544[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 Quote