- Security-news - lists.drupal.org

SA-CONTRIB-2013-054 - Fast Permissions Administration - Access Bypass
by security-news＠drupal.org 26 Jun '13

26 Jun '13

View online: https://drupal.org/node/2028813 * Advisory ID: DRUPAL-SA-CONTRIB-2013-054 * Project: Fast Permissions Administration [1] (third-party module) * Version: 6.x, 7.x * Date: 2013-June-26 * Security risk: Highly critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The Fast Permissions Administration module enables you to use inline filters on the permissions page, as well as loading the permissions form through a modal dialog. The module doesn't sufficiently check user access for the modal content callback, allowing unauthorized access to the permissions edit form. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Fast Permissions Administration 6.x-2.x versions prior to 6.x-2.5. * Fast Permissions Administration 7.x-2.x versions prior to 7.x-2.3. Drupal core is not affected. If you do not use the contributed Fast Permissions Administration [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Fast Permissions Administration module for Drupal 6.x, upgrade to Fast Permissions Administration 6.x-2.5 [5] * If you use the Fast Permissions Administration module for Drupal 7.x, upgrade to Fast Permissions Administration 7.x-2.3 [6] Also see the Fast Permissions Administration [7] project page. -------- REPORTED BY --------------------------------------------------------- * Philip Boden [8] -------- FIXED BY ------------------------------------------------------------ * Corey Aufang [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [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/fpa [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/fpa [5] https://drupal.org/node/2028417 [6] https://drupal.org/node/2028421 [7] http://drupal.org/project/fpa [8] http://drupal.org/user/329794 [9] http://drupal.org/user/163737 [10] http://drupal.org/user/262198 [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-136 - Apache Solr Search Autocomplete - Cross Site Scripting (XSS)
by security-news＠drupal.org 26 Jun '13

26 Jun '13

View online: https://drupal.org/node/1762734 * Advisory ID: DRUPAL-SA-CONTRIB-2012-136 * Project: Apache Solr Autocomplete [1] (third-party module) * Version: 6.x, 7.x * Date: 2012-August-29 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Apache Solr Search Autocomplete module enables you to add autocomplete capabilities to the search text field for the Apache Solr Search Integration module. The module doesn't sufficiently filter the autocomplete results sent back from the Drupal site, so under the scenario where someone provided a URL with a specially-crafted search string embedded in it, the attacker could have a user execute arbitrary Javascript when clicking or focusing on the autocomplete text field. This vulnerability is mitigated by the fact that the attacked user must click or otherwise give focus to the text widget to have the Javascript activate. CVE: CVE-2012-6573 -------- VERSIONS AFFECTED --------------------------------------------------- * Apache Solr Autocomplete 6.x-1.x versions prior to 6.x-1.4. * Apache Solr Autocomplete 7.x-1.x versions prior to 7.x-1.3. Drupal core is not affected. If you do not use the contributed Apache Solr Autocomplete [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version. * If you use the Apache Solr Autocomplete module for Drupal 6.x, upgrade to Apache Solr Autocomplete 6.x-1.4 [4] * If you use the Apache Solr Autocomplete module for Drupal 7.x, upgrade to Apache Solr Autocomplete 7.x-1.3 [5] Also see the Apache Solr Autocomplete [6] project page. -------- REPORTED BY --------------------------------------------------------- * drupaledmonk [7] -------- FIXED BY ------------------------------------------------------------ * Alejandro Garza [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [9] 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 [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. [1] http://drupal.org/project/apachesolr_autocomplete [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/apachesolr_autocomplete [4] https://drupal.org/node/1762684 [5] https://drupal.org/node/1762686 [6] http://drupal.org/project/apachesolr_autocomplete [7] http://drupal.org/user/263391 [8] http://drupal.org/user/153120 [9] http://drupal.org/user/36762 [10] http://drupal.org/contact [11] http://drupal.org/security-team [12] http://drupal.org/writing-secure-code [13] http://drupal.org/security/secure-configuration

1 0

SA-CONTRIB-2013-053 - Login Security - Multiple Vulnerabilities
by security-news＠drupal.org 19 Jun '13

19 Jun '13

View online: https://drupal.org/node/2023585 * Advisory ID: DRUPAL-SA-CONTRIB-2013-053 * Project: Login Security [1] (third-party module) * Version: 6.x, 7.x * Date: 2013-June-19 * Security risk: Critical [2] * Exploitable from: Remote * Vulnerability: Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- Login Security module adds additional access controls to the login form of Drupal. When Login Security is configured to use the delay feature, frequent or concurrent failed attempts to login can consume all the web serving processes, causing a denial of service. It is possible to bypass Login Security features when soft blocking is disabled. This is due to the incorrect use of string filtering in the module which can cause the module to skip all checks. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Login Security 6.x-1.x versions prior to 6.x-1.2. * Login Security 7.x-1.x versions prior to 7.x-1.2. Drupal core is not affected. If you do not use the contributed Login Security [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Login Security module for Drupal 6.x, upgrade to Login Security 6.x-1.3 [5] * If you use the Login Security module for Drupal 7.x, upgrade to Login Security 7.x-1.3 [6] Also see the Login Security [7] project page. -------- REPORTED BY --------------------------------------------------------- * David Stoline [8] and Heine Deelstra [9] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * David Norman [10] the module maintainer * Chris Yu [11] -------- COORDINATED BY ------------------------------------------------------ * David Stoline [12] 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 [13]. Learn more about the Drupal Security team and their policies [14], writing secure code for Drupal [15], and securing your site [16]. [1] http://drupal.org/project/login_security [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/login_security [5] https://drupal.org/node/2023503 [6] https://drupal.org/node/2023507 [7] http://drupal.org/project/login_security [8] http://drupal.org/user/329570 [9] http://drupal.org/user/17943 [10] http://drupal.org/user/972 [11] http://drupal.org/user/202205 [12] http://drupal.org/user/329570 [13] http://drupal.org/contact [14] http://drupal.org/security-team [15] http://drupal.org/writing-secure-code [16] http://drupal.org/security/secure-configuration

1 0

SA-CONTRIB-2013-052 - Display Suite - Cross Site Scripting (XSS)
by security-news＠drupal.org 12 Jun '13

12 Jun '13

View online: https://drupal.org/node/2017933 * Advisory ID: DRUPAL-SA-CONTRIB-2013-052 * Project: Display Suite [1] (third-party module) * Version: 7.x * Date: 2013-June-12 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Display Suite allows you to take full control over how your content is displayed using a drag and drop interface. In certain situations, Display Suite does not properly sanitize entity bundle labels, allowing a malicious user to embed scripts within a page, resulting in a Cross-site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker has to be able to create entity bundle labels of some sort, which usually needs a higher level permission such as administer taxonomy. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Display Suite 7.x-1.x versions prior to 7.x-1.7. * Display Suite 7.x-2.x versions prior to 7.x-2.3. Drupal core is not affected. If you do not use the contributed Display Suite [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the first branch of Display Suite module for Drupal 7.x, upgrade to Display Suite 7.x-1.8 [5] * If you use the second branch of Display Suite module for Drupal 7.x, upgrade to Display Suite 7.x-2.4 [6] Also see the Display Suite [7] project page. -------- REPORTED BY --------------------------------------------------------- * Francisco José Cruz Romanos [8] -------- FIXED BY ------------------------------------------------------------ * Francisco José Cruz Romanos [9] * Kristof De Jaeger [10] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [11] 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 [12]. Learn more about the Drupal Security team and their policies [13], writing secure code for Drupal [14], and securing your site [15]. [1] http://drupal.org/project/ds [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/ds [5] https://drupal.org/node/2017639 [6] https://drupal.org/node/2017641 [7] http://drupal.org/project/ds [8] http://drupal.org/user/848238 [9] http://drupal.org/user/848238 [10] http://drupal.org/user/107403 [11] http://drupal.org/user/262198 [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

1 0

SA-CONTRIB-2013-051 - Services - Cross site request forgery (CSRF)
by security-news＠drupal.org 05 Jun '13

05 Jun '13

View online: https://drupal.org/node/2012982 * Advisory ID: DRUPAL-SA-CONTRIB-2013-051 * Project: Services [1] (third-party module) * Version: 6.x, 7.x * Date: 2013-June-05 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- This module enables you to expose an API to third party systems using REST, XML-RPC or other protocols. The module doesn't sufficiently verify writing requests (POST, PUT, DELETE) with session cookie authentication, thereby exposing a Cross Site Request Forgery vulnerability. This vulnerability is mitigated by the fact that session based authentication must be enabled for an endpoint. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Services 6.x-3.x versions. * Services 7.x-3.x versions prior to 7.x-3.4. Drupal core is not affected. If you do not use the contributed Services [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version or uninstall the module. * If you use the Services module for Drupal 7.x, upgrade to Services 7.x-3.4 [5] * If you use the Services module for Drupal 6.x, uninstall the module. Note that Services clients using session authentication now should supply a special X-CSRF-Token header with a token that can be retrieved from http://example.com/services/session/token [6]. This is needed for writing HTTP methods calls (POST, PUT, DELETE). Also see the Services [7] project page. -------- REPORTED BY --------------------------------------------------------- * Klaus Purer [8] of the Drupal Security Team * Fredrik Lassen [9] -------- FIXED BY ------------------------------------------------------------ * Yuriy Gerasimov [10] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [11] 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 [12]. Learn more about the Drupal Security team and their policies [13], writing secure code for Drupal [14], and securing your site [15]. [1] http://drupal.org/project/services [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/services [5] https://drupal.org/node/2012366 [6] http://example.com/services/session/token [7] http://drupal.org/project/services [8] http://drupal.org/user/262198 [9] http://drupal.org/user/243377 [10] http://drupal.org/user/257311 [11] http://drupal.org/user/262198 [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

1 0

SA-CONTRIB-2013-050 - Webform - Cross Site Scripting (XSS)
by security-news＠drupal.org 30 May '13

30 May '13

View online: https://drupal.org/node/2007460 * Advisory ID: DRUPAL-SA-CONTRIB-2013-050 * Project: Webform [1] (third-party module) * Version: 6.x * Date: 2013-May-29 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Webform module allows the creation of custom webforms and surveys. Webform module does not sanitize the labels of created components (fields) when displaying a list of components to be used in e-mails or downloaded CSV files. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "edit own webform content" or "edit all webform content". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Webform 6.x-3.x versions prior to 6.x-3.19. Drupal core is not affected. If you do not use the contributed Webform [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Webform module for Drupal 6, install the latest version, Webform 6.x-3.19 [5]. Drupal 7 versions of this module are not affected. Also see the Webform [6] project page. -------- REPORTED BY --------------------------------------------------------- * Justin C. Klein Keane [7] -------- FIXED BY ------------------------------------------------------------ * Nate Haug [8] the module maintainer * Justin C. Klein Keane [9] -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [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/webform [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/webform [5] http://drupal.org/node/2007390 [6] http://drupal.org/project/webform [7] http://drupal.org/user/302225 [8] http://drupal.org/user/35821 [9] http://drupal.org/user/302225 [10] https://drupal.org/user/36762 [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-2013-049 - Node access user reference - Access Bypass
by security-news＠drupal.org 29 May '13

29 May '13

View online: http://drupal.org/node/2007122 * Advisory ID: DRUPAL-SA-CONTRIB-2013-049 * Project: Node access user reference [1] (third-party module) * Version: 6.x, 7.x * Date: 2013-May-29 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module allows different access permissions to be given to authors, referenced users and non-referenced users. When an author has created content containing a user reference field (with author update/delete grants enabled) and the author's user account is later deleted, content created by them can be edited by anonymous users. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * nodeaccess_userreference 6.x-3.x versions prior to 6.x-3.5. * nodeaccess_userreference 7.x-3.x versions prior to 7.x-3.10. Drupal core is not affected. If you do not use the contributed Node access user reference [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the nodeaccess_userreference module for Drupal 6.x, upgrade to nodeaccess_userreference 6.x-3.5 [5] * If you use the nodeaccess_userreference module for Drupal 7.x, upgrade to nodeaccess_userreference 7.x-3.10 [6] Also see the Node access user reference [7] project page. -------- REPORTED BY --------------------------------------------------------- * Jamie Wiseman [8] -------- FIXED BY ------------------------------------------------------------ * Jamie Wiseman [9] * Dan Smith [10] provisional member of the Drupal Security Team * Chris Hales [11] and Greg Knaddison [12] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Dan Smith [13] provisional member 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 [14]. Learn more about the Drupal Security team and their policies [15], writing secure code for Drupal [16], and securing your site [17]. [1] http://drupal.org/project/nodeaccess_userreference [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/nodeaccess_userreference [5] http://drupal.org/node/2007072 [6] http://drupal.org/node/2007078 [7] http://drupal.org/project/nodeaccess_userreference [8] http://drupal.org/user/16327 [9] http://drupal.org/user/16327 [10] http://drupal.org/user/241220 [11] http://drupal.org/user/347249 [12] http://drupal.org/user/36762 [13] http://drupal.org/user/241220 [14] http://drupal.org/contact [15] http://drupal.org/security-team [16] http://drupal.org/writing-secure-code [17] http://drupal.org/security/secure-configuration

1 0

SA-CONTRIB-2013-048 - Edit Limit - Access Bypass
by security-news＠drupal.org 29 May '13

29 May '13

View online: http://drupal.org/node/2007048 * Advisory ID: DRUPAL-SA-CONTRIB-2013-048 * Project: Edit Limit [1] (third-party module) * Version: 7.x * Date: 2013-May-29 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- Edit Limit enables you to set time and count-based limits on how and when a user can edit nodes or comments. The module doesn't sufficiently check user access when editing comments to see if the user has the necessary permissions to edit a comment outside of the limits applied by this module. This makes it possible for a user who can edit their own comments to edit the comments of any other user. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "edit comments". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Edit Limit 7.x-1.x versions prior to 7.x-1.3. Drupal core is not affected. If you do not use the contributed Edit Limit [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Edit Limit module for Drupal 7.x, upgrade to Edit Limit 7.x-1.3 [5] Also see the Edit Limit [6] project page. -------- REPORTED BY --------------------------------------------------------- * Morten Fangel [7] -------- FIXED BY ------------------------------------------------------------ * Quade [8] the module maintainer * Morten Fangel [9] -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [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/edit_limit [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/edit_limit [5] http://drupal.org/node/2006188 [6] http://drupal.org/project/edit_limit [7] http://drupal.org/user/376055 [8] http://drupal.org/user/71791 [9] http://drupal.org/user/376055 [10] http://drupal.org/user/36762 [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-2013-047 - Google Authenticator login - Access Bypass
by security-news＠drupal.org 15 May '13

15 May '13

View online: http://drupal.org/node/1995706 * Advisory ID: DRUPAL-SA-CONTRIB-2013-047 * Project: Google Authenticator login [1] (third-party module) * Version: 6.x, 7.x * Date: 2013-May-15 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module will allow you to add Time-based One-time Password Algorithm (also called "Two Step Authentication" or "Multi-Factor Authentication") support to user logins. It works with Google's Authenticator app system and support most (if not all) OATH based HOTP/TOTP systems. .... Accidental removal of account configuration. In certain scenarios, Google Authenticator login incorrectly determines the user's account name. The change in account name could cause the two-factor authentication for existing accounts to be lost, allowing users to log in using just username and password. This vulnerability is mitigated by the fact while Google Authenticator login's additional verification is by-passed, a username and password are still required to log in. .... One Time Password (OTP) replay If an attacker can intercept a login request with a username, password and OTP, an attacker could use this same data again to login to the website. This vulnerability is mitigated by the fact that an attacker who can intercept a login request with this level of detail can usually also intercept the ongoing session identifying token. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Google Authenticator login 6.x-1.x versions prior to 6.x-1.2. * Google Authenticator login 7.x-1.x versions prior to 7.x-1.4. Drupal core is not affected. If you do not use the contributed Google Authenticator login [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Google Authenticator login module for Drupal 6.x, upgrade to Google Authenticator login module 6.x-1.2 [5] * If you use the Google Authenticator login module for Drupal 7.x, upgrade to Google Authenticator login module 7.x-1.4 [6] Also see the Google Authenticator login [7] project page. -------- REPORTED BY --------------------------------------------------------- * Ivo Van Geertruyen [8] of the Drupal Security Team * Lode Vanstechelman [9] -------- FIXED BY ------------------------------------------------------------ * Peter Droogmans [10] the module maintainer * Jelle Sebreghts [11] the module maintainer * Ivo Van Geertruyen [12] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Ivo Van Geertruyen [13] 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 [14]. Learn more about the Drupal Security team and their policies [15], writing secure code for Drupal [16], and securing your site [17]. [1] http://drupal.org/project/ga_login [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/ga_login [5] http://drupal.org/node/1995634 [6] http://drupal.org/node/1995482 [7] http://drupal.org/project/ga_login [8] http://drupal.org/user/383424 [9] http://drupal.org/user/657472 [10] http://drupal.org/user/105002 [11] http://drupal.org/user/829198 [12] http://drupal.org/user/383424 [13] http://drupal.org/user/383424 [14] http://drupal.org/contact [15] http://drupal.org/security-team [16] http://drupal.org/writing-secure-code [17] http://drupal.org/security/secure-configuration

1 0

SA-CONTRIB-2013-046 - Filebrowser - Reflected Cross Site Scripting (XSS)
by security-news＠drupal.org 01 May '13

01 May '13

View online: http://drupal.org/node/1984212 * Advisory ID: DRUPAL-SA-CONTRIB-2013-046 * Project: Filebrowser [1] (third-party module) * Version: 6.x * Date: 2013-May-1 * Security risk: Highly critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Filebrowser module allows site administrators to expose a particular file system folder and all of its subfolders with an FTP-like interface to site visitors. The module doesn't sufficiently sanitize user input when presenting lists of files. Because the vulnerability is /Reflected/ Cross Site Scripting, the only mitigating factor is that an authenticated user must be tricked into visiting a specially crafted malicious url. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Filebrowser 6.x-2.x versions prior to 6.x-2.2. Drupal core is not affected. If you do not use the contributed Filebrowser [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Filebrowser module for Drupal 6.x, upgrade to Filebrowser 6.x-2.2 [5] Also see the Filebrowser [6] project page. -------- REPORTED BY --------------------------------------------------------- * Paweł Krawczyk [7] -------- FIXED BY ------------------------------------------------------------ * Yoran Brault [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Lee Rowlands [9] 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 [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. [1] http://drupal.org/project/filebrowser [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/filebrowser [5] http://drupal.org/node/1983356 [6] http://drupal.org/project/filebrowser [7] http://drupal.org/user/243792 [8] http://drupal.org/user/46153 [9] http://drupal.org/user/395439 [10] http://drupal.org/contact [11] http://drupal.org/security-team [12] http://drupal.org/writing-secure-code [13] http://drupal.org/security/secure-configuration

1 0