February 2015 - Security-news

SA-CONTRIB-2015-052 - RESTful Web Services - Access Bypass
by security-news＠drupal.org 18 Feb '15

18 Feb '15

View online: https://www.drupal.org/node/2428863 * Advisory ID: DRUPAL-SA-CONTRIB-2015-052 * Project: RESTful Web Services [1] (third-party module) * Version: 7.x * Date: 2015-February-18 * Security risk: 12/25 ( Moderately Critical) AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to expose Drupal entities as RESTful web services. It provides a machine-readable interface to exchange resources in JSON, XML and RDF. The RESTWS Basic Auth submodule doesn't sufficiently disable page caching for authenticated requests thereby leaking potentially confidential data to unauthorized users. This vulnerability is mitigated by the fact that the RESTWS Basic Auth submodule must be enabled, page caching must be enabled and permissions for a resource containing sensitive data must be enabled (for example the User resource). -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * RESTWS 7.x-1.x versions prior to 7.x-1.5. * RESTWS 7.x-2.x versions prior to 7.x-2.3. Drupal core is not affected. If you do not use the contributed RESTful Web Services [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the RESTWS module for Drupal 7.x, upgrade to RESTWS 7.x-1.5 [5] or RESTWS 7.x-2.3 [6] Also see the RESTful Web Services [7] project page. -------- REPORTED BY --------------------------------------------------------- * Jason Little [8] -------- FIXED BY ------------------------------------------------------------ * Klaus Purer [9] the module maintainer and member of the Drupal Security Team -------- 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 https://www.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]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/restws [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/restws [5] https://www.drupal.org/node/2428857 [6] https://www.drupal.org/node/2428855 [7] https://www.drupal.org/project/restws [8] https://www.drupal.org/user/143477 [9] https://www.drupal.org/u/klausi [10] https://www.drupal.org/u/klausi [11] https://www.drupal.org/contact [12] https://www.drupal.org/security-team [13] https://www.drupal.org/writing-secure-code [14] https://www.drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-051 - Term Queue - Cross Site Scripting (XSS)
by security-news＠drupal.org 18 Feb '15

18 Feb '15

View online: https://www.drupal.org/node/2428853 * Advisory ID: DRUPAL-SA-CONTRIB-2015-051 * Project: Term Queue [1] (third-party module) * Version: 6.x * Date: 2015-February-18 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Term Queue module allows you to create lists of taxonomy terms and display them in a block. The module doesn't sufficiently sanitize user supplied text in some administration pages, thereby exposing a Cross Site Scripting vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "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 --------------------------------------------------- * Term Queue 6.x-1.0 Drupal core is not affected. If you do not use the contributed Term Queue [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Term Queue module for Drupal 6.x, upgrade to Term Queue 6.x-1.1 [5] Also see the Term Queue [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Edward Crompton [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [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 https://www.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]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [14] [1] https://www.drupal.org/project/term_queue [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/term_queue [5] https://www.drupal.org/node/2428483 [6] https://www.drupal.org/project/term_queue [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/u/eddie_c [9] https://www.drupal.org/user/2301194 [10] https://www.drupal.org/contact [11] https://www.drupal.org/security-team [12] https://www.drupal.org/writing-secure-code [13] https://www.drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-050 - Services Basic Authentication - Access bypass - Unsupported
by security-news＠drupal.org 18 Feb '15

18 Feb '15

View online: https://www.drupal.org/node/2428851 * Advisory ID: DRUPAL-SA-CONTRIB-2015-050 * Project: Services Basic Authentication [1] (third-party module) * Version: 7.x * Date: 2015-February-18 * Security risk: 15/25 ( Critical) AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:All [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- Services Basic Authentication module adds HTTP basic authentication for Services module. A user could get unauthorized access to resources under some circumstances. This vulnerability is mitigated by the fact that the authentication works correctly when page caching is disabled. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * All versions of Services Basic Authentication module. Drupal core is not affected. If you do not use the contributed Services Basic Authentication [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Services Basic Authentication module you should uninstall it Also see the Services Basic Authentication [5] project page. -------- REPORTED BY --------------------------------------------------------- * Marvin Whitfield [6] * Matt Supko [7] -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [8] of the Drupal Security Team * Mori Sugimoto [9] of the Drupal Security Team * Pere Orga [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 https://www.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]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/services_basic_auth [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/services_basic_auth [5] https://www.drupal.org/project/services_basic_auth [6] https://www.drupal.org/user/631814 [7] https://www.drupal.org/user/499020 [8] https://www.drupal.org/user/36762 [9] https://www.drupal.org/user/82971 [10] https://www.drupal.org/user/2301194 [11] https://www.drupal.org/contact [12] https://www.drupal.org/security-team [13] https://www.drupal.org/writing-secure-code [14] https://www.drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-049 - Navigate - Cross Site Scripting (XSS)
by security-news＠drupal.org 18 Feb '15

18 Feb '15

View online: https://www.drupal.org/node/2428815 * Advisory ID: DRUPAL-SA-CONTRIB-2015-049 * Project: Navigate [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-February-18 * Security risk: 16/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Navigate is a customizable navigation bar for Drupal. The module doesn't sufficiently sanitize user input when displaying the Navigate bar. Because the vulnerability is a Reflected Cross Site Scripting, the only mitigating factor is that the victim 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 --------------------------------------------------- * Navigate 6.x-1.x versions prior to 6.x-1.1. * Navigate 7.x-1.x versions prior to 7.x-1.1. Drupal core is not affected. If you do not use the contributed Navigate [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Navigate module for Drupal 6.x, upgrade to Navigate 6.x-1.1 [5] * If you use the Navigate module for Drupal 7.x, upgrade to Navigate 7.x-1.1 [6] Also see the Navigate [7] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [8] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Amit Goyal [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [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 https://www.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]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/navigate [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/navigate [5] https://www.drupal.org/node/2428505 [6] https://www.drupal.org/node/2428503 [7] https://www.drupal.org/project/navigate [8] https://www.drupal.org/user/2301194 [9] https://www.drupal.org/user/56441 [10] https://www.drupal.org/user/2301194 [11] https://www.drupal.org/contact [12] https://www.drupal.org/security-team [13] https://www.drupal.org/writing-secure-code [14] https://www.drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-048 - Avatar Uploader - Arbitrary PHP code execution
by security-news＠drupal.org 18 Feb '15

18 Feb '15

View online: https://www.drupal.org/node/2428793 * Advisory ID: DRUPAL-SA-CONTRIB-2015-048 * Project: Avatar Uploader [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-February-18 * Security risk: 16/25 ( Critical) AC:None/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Arbitrary PHP code execution -------- DESCRIPTION --------------------------------------------------------- Avatar Uploader module provides an alternative way to upload user pictures. The module doesn't sufficiently enforce file extensions when an avatar is uploaded, allowing users to bypass Drupal's normal file upload protections to install malicious HTML or executable code to the server. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "upload avatar file", and that the fix for SA-2006-006 - Drupal Core - Execution of arbitrary files in certain Apache configurations [3] should prevent code execution in typical Apache configurations. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [4] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Avatar Uploader 6.x-1.x versions prior to 6.x-1.3. Drupal core is not affected. If you do not use the contributed Avatar Uploader [5] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Avatar Uploader module for Drupal 6.x, upgrade to Avatar Uploader 6.x-1.3 [6] Also see the Avatar Uploader [7] project page. -------- REPORTED BY --------------------------------------------------------- * Liran Tal [8] -------- FIXED BY ------------------------------------------------------------ * Robbin Gaoxin Zhao [9], the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [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 https://www.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]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/avatar-uploader [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/node/65409 [4] http://cve.mitre.org/ [5] https://www.drupal.org/project/avatar-uploader [6] https://www.drupal.org/node/2427069 [7] https://www.drupal.org/project/avatar-uploader [8] https://www.drupal.org/user/1315712 [9] https://www.drupal.org/user/616818 [10] https://www.drupal.org/user/2301194 [11] https://www.drupal.org/contact [12] https://www.drupal.org/security-team [13] https://www.drupal.org/writing-secure-code [14] https://www.drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-047 - Panopoly Magic - Cross Site Scripting (XSS)
by security-news＠drupal.org 18 Feb '15

18 Feb '15

View online: https://www.drupal.org/node/2428799 * Advisory ID: DRUPAL-SA-CONTRIB-2015-047 * Project: Panopoly Magic [1] (third-party module) * Version: 7.x * Date: 2015-February-18 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module enables live previews of Panels panes in the modal dialog for adding or editing them. The module doesn't sufficiently filter the pane title when re-rendering the live preview. This vulnerability is mitigated by the fact that an attacker must have permission to add or edit Panels panes. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Panopoly Magic 7.x-1.x versions prior to 7.x-1.17. Drupal core is not affected. If you do not use the contributed Panopoly Magic [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Panopoly Magic module for Drupal 7.x, upgrade to Panopoly Magic 7.x-1.17 [5] Also see the Panopoly Magic [6] project page. -------- REPORTED BY --------------------------------------------------------- * David Snopek [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * David Snopek [8] of the Drupal Security Team * Matt Cheney [9] -------- COORDINATED BY ------------------------------------------------------ * David Snopek [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 https://www.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]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/panopoly_magic [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/panopoly_magic [5] https://www.drupal.org/node/2428749 [6] https://www.drupal.org/project/panopoly_magic [7] https://www.drupal.org/u/dsnopek [8] https://www.drupal.org/u/dsnopek [9] https://www.drupal.org/u/populist [10] https://www.drupal.org/u/dsnopek [11] https://www.drupal.org/contact [12] https://www.drupal.org/security-team [13] https://www.drupal.org/writing-secure-code [14] https://www.drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-046 - Taxonomy Tools - Cross Site Scripting (XSS)
by security-news＠drupal.org 11 Feb '15

11 Feb '15

View online: https://www.drupal.org/node/2424355 * Advisory ID: DRUPAL-SA-CONTRIB-2015-046 * Project: Taxonomy Tools [1] (third-party module) * Version: 7.x * Date: 2015-February-11 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Taxonomy Tools module provides alternative ways of managing taxonomy terms. The module doesn't sufficiently escape node and taxonomy term titles when displaying them, allowing a malicious user to inject code. This vulnerability is mitigated by the fact that an attacker must have a role with permission to create or edit nodes or taxonomy terms. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Taxonomy Tools 7.x-1.x versions prior to 7.x-1.4. Drupal core is not affected. If you do not use the contributed Taxonomy Tools [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Taxonomy Tools module for Drupal 7.x, upgrade to Taxonomy Tools 7.x-1.4 [5] Also see the Taxonomy Tools [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Mārtiņš Bērtiņš [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Rick Manelius [9] of the Drupal Security Team * Aaron Ott [10] 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 https://www.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]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/taxonomy_tools [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/taxonomy_tools [5] https://www.drupal.org/node/2424059 [6] https://www.drupal.org/project/taxonomy_tools [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/1181510 [9] https://www.drupal.org/user/680072 [10] https://www.drupal.org/user/154069 [11] https://www.drupal.org/contact [12] https://www.drupal.org/security-team [13] https://www.drupal.org/writing-secure-code [14] https://www.drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-045 - Node Access Product - Cross Site Scripting (XSS) - Unsupported
by security-news＠drupal.org 11 Feb '15

11 Feb '15

View online: https://www.drupal.org/node/2424349 * Advisory ID: DRUPAL-SA-CONTRIB-2015-045 * Project: Node access product [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-February-11 * Security risk: 11/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:None/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Node Access Product module provides 'Node access' settings for product nodes, whereby users who purchase the product are granted view access to content, which can be predefined either by taxonomy, by node, or by Views. The module doesn't sufficiently sanitize node titles leading to the possibility of cross-site scripting by an attacker. This vulnerability is mitigated by the fact that an attacker must have a role with permission to create/edit 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 --------------------------------------------------- * All versions of Node Access Product Drupal core is not affected. If you do not use the contributed Node Access Product [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Node Access Product module you should uninstall it. Also see the Node access product [5] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Rick Manelius [7] of the Drupal Security Team * Aaron Ott [8] 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 https://www.drupal.org/contact [9]. Learn more about the Drupal Security team and their policies [10], writing secure code for Drupal [11], and securing your site [12]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [13] [1] https://www.drupal.org/project/nap [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/nap [5] https://www.drupal.org/project/nap [6] https://www.drupal.org/user/2301194 [7] https://www.drupal.org/user/680072 [8] https://www.drupal.org/user/154069 [9] https://www.drupal.org/contact [10] https://www.drupal.org/security-team [11] https://www.drupal.org/writing-secure-code [12] https://www.drupal.org/security/secure-configuration [13] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-044 - Taxonomy Path - Cross Site Scripting (XSS)
by security-news＠drupal.org 11 Feb '15

11 Feb '15

View online: https://www.drupal.org/node/2424439 * Advisory ID: DRUPAL-SA-CONTRIB-2015-044 * Project: Taxonomy Path [1] (third-party module) * Version: 7.x * Date: 2015-February-11 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Taxonomy Path module enables you to create custom links to taxonomy terms within a display mode. The module doesn't sufficiently sanitize user provided text in the provided "Link to path" field formatter, thereby exposing a Cross Site Scripting vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with permission to create/edit taxonomy terms. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Taxonomy Path 7.x-1.x versions prior to 7.x-1.2. Drupal core is not affected. If you do not use the contributed Taxonomy Path [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Taxonomy Path module for Drupal 7.x, upgrade to Taxonomy Path 7.x-1.2 [5] Also see the Taxonomy Path [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * William Hurley [8] the module maintainer * Pere Orga [9] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [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 https://www.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]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/taxonomy_path [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/taxonomy_path [5] https://www.drupal.org/node/2424411 [6] https://www.drupal.org/project/taxonomy_path [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/654480 [9] https://www.drupal.org/user/2301194 [10] https://www.drupal.org/user/2301194 [11] https://www.drupal.org/contact [12] https://www.drupal.org/security-team [13] https://www.drupal.org/writing-secure-code [14] https://www.drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-043 - Commerce Balanced Payments - Multiple vulnerabilities
by security-news＠drupal.org 11 Feb '15

11 Feb '15

View online: https://www.drupal.org/node/2424435 * Advisory ID: DRUPAL-SA-CONTRIB-2015-043 * Project: Commerce Balanced Payments [1] (third-party module) * Version: 7.x * Date: 2015-February-11 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting, Cross Site Request Forgery, Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- Commerce Balanced Payments module integrates Drupal Commerce with the Balanced Payments third-party service. The module doesn't sufficiently sanitize user supplied text in the Bank Account Listing Page, thereby exposing a Cross Site Scripting vulnerability. Also, some URLs were not protected against CSRF. A malicious user can cause another user to delete their configured bank accounts by getting their browser to make a request to a specially-crafted 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 --------------------------------------------------- * All versions of Commerce Balanced Payments. Drupal core is not affected. If you do not use the contributed Commerce Balanced Payments [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Commerce Balanced Payments module you should uninstall it. Also see the Commerce Balanced Payments [5] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [7] 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 https://www.drupal.org/contact [8]. Learn more about the Drupal Security team and their policies [9], writing secure code for Drupal [10], and securing your site [11]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [12] [1] https://www.drupal.org/project/commerce_balanced_payments [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/commerce_balanced_payments [5] https://www.drupal.org/project/commerce_balanced_payments [6] https://www.drupal.org/user/2301194 [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/contact [9] https://www.drupal.org/security-team [10] https://www.drupal.org/writing-secure-code [11] https://www.drupal.org/security/secure-configuration [12] https://twitter.com/drupalsecurity

1 0