Security-news June 2013

security-news@drupal.org

1 participants
5 discussions

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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Security-news June 2013