Security-news January 2015

security-news@drupal.org

1 participants
33 discussions

SA-CONTRIB-2015-013 - Field Display Label - Cross Site Scripting (XSS)
by security-news＠drupal.org 07 Jan '15

07 Jan '15

View online: https://www.drupal.org/node/2403489 * Advisory ID: DRUPAL-SA-CONTRIB-2015-013 * Project: Field Display Label [1] (third-party module) * Version: 7.x * Date: 2015-January-07 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module enables you to use a different label for displaying fields from the label used when viewing the field in a form. The module doesn't sufficiently sanitize the alternate field label in content types settings. This vulnerability is mitigated by the fact that an attacker must have a role with the permission to add or edit fields on an entity. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Field Display Label 7.x-1.x versions prior to 7.x-1.2. Drupal core is not affected. If you do not use the contributed Field Display Label [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Field Display Label module for Drupal 7.x, upgrade to Field Display Label 7.x-1.3 [5] Also see the Field Display Label [6] project page. -------- REPORTED BY --------------------------------------------------------- * Nickolay Leshchev [7] -------- FIXED BY ------------------------------------------------------------ * Nickolay Leshchev [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 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/field_display_label [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/field_display_label [5] https://www.drupal.org/node/2403057 [6] https://www.drupal.org/project/field_display_label [7] https://www.drupal.org/user/982724 [8] https://www.drupal.org/user/982724 [9] https://www.drupal.org/user/36762 [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-012 - Jammer - Cross Site Request Forgery (CSRF)
by security-news＠drupal.org 07 Jan '15

07 Jan '15

View online: https://www.drupal.org/node/2403487 * Advisory ID: DRUPAL-SA-CONTRIB-2015-012 * Project: Jammer [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-January-07 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:None/CI:None/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- This module enables you to hide or remove items from displaying including the node and comment preview buttons, node delete button, revision log textarea, workflow form on the workflow tab, and feed icon. The report administration links are not properly protected from CSRF. A malicious user could cause an administrator to delete settings for hidden form elements or status messages by getting the administrator's browser to make a request to a specially-crafted URL while the administrator was logged in. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Jammer 6.x-1.x versions prior to 6.x-1.8. * Jammer 7.x-1.x versions prior to 7.x-1.4. Drupal core is not affected. If you do not use the contributed Jammer [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Jammer module for Drupal 6.x, upgrade to Jammer 6.x-1.8 [5] * If you use the Jammer module for Drupal 7.x, upgrade to Jammer 7.x-1.4 [6] Also see the Jammer [7] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [8] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * David Norman [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Owen Barton [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/jammer [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/jammer [5] https://www.drupal.org/node/2402749 [6] https://www.drupal.org/node/2402745 [7] https://www.drupal.org/project/jammer [8] https://www.drupal.org/user/2301194 [9] https://www.drupal.org/user/972 [10] https://www.drupal.org/user/19668 [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-011 - Todo Filter - Cross Site Request Forgery (CSRF)
by security-news＠drupal.org 07 Jan '15

07 Jan '15

View online: https://www.drupal.org/node/2403465 * Advisory ID: DRUPAL-SA-CONTRIB-2015-011 * Project: Todo Filter [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-January-07 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:None/CI:None/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- Todo Filter module provides an input filter to display check-boxes that can be used as a task list. Some paths were not protected against CSRF, meaning that an attacker could cause users to toggle tasks they did not intend to toggle by getting the user's browser to make a request to a specially-crafted URL while the user was logged in. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Todo Filter 6.x-1.x versions prior to 6.x-1.1. * Todo Filter 7.x-1.x versions prior to 7.x-1.1. Drupal core is not affected. If you do not use the contributed Todo Filter [4] module, there is nothing you need to do. Drupal core is not affected. If you do not use the contributed Todo Filter [5] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Todo Filter module for Drupal 6.x, upgrade to Todo Filter 6.x-1.1 [6] * If you use the Todo Filter module for Drupal 7.x, upgrade to Todo Filter 7.x-1.1 [7] Also see the Todo Filter [8] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [9] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Joshua Clark [10] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [11] 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 [12]. Learn more about the Drupal Security team and their policies [13], writing secure code for Drupal [14], and securing your site [15]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [16] [1] https://www.drupal.org/project/todo_filter [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/todo_filter [5] https://www.drupal.org/project/todo_filter [6] https://www.drupal.org/node/2403015 [7] https://www.drupal.org/node/2403013 [8] https://www.drupal.org/project/todo_filter [9] https://www.drupal.org/user/2301194 [10] https://www.drupal.org/user/1132616 [11] https://www.drupal.org/user/2301194 [12] https://www.drupal.org/contact [13] https://www.drupal.org/security-team [14] https://www.drupal.org/writing-secure-code [15] https://www.drupal.org/security/secure-configuration [16] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-010 - Log Watcher - Cross Site Request Forgery (CSRF)
by security-news＠drupal.org 07 Jan '15

07 Jan '15

View online: https://www.drupal.org/node/2403463 * Advisory ID: DRUPAL-SA-CONTRIB-2015-010 * Project: Log Watcher [1] (third-party module) * Version: 6.x * Date: 2015-January-07 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:None/CI:None/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- Log Watcher allows you to monitor your site logs in a systematic way by setting up scheduled aggregations for specific log types. The report administration links are not properly protected from CSRF. A malicious user could cause a log administrator to enable, disable, or delete a Log Watcher report by getting the administrator's browser to make a request to a specially-crafted URL while the administrator was logged in. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Log Watcher 6.x-1.x versions prior to 6.x-1.2. Drupal core is not affected. If you do not use the contributed Log Watcher [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Log Watcher module for Drupal 6.x, upgrade to Log Watcher 6.x-1.2 [5] Also see the Log Watcher [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * David Norman [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Owen Barton [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/logwatcher [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/logwatcher [5] https://www.drupal.org/node/2402767 [6] https://www.drupal.org/project/logwatcher [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/972 [9] https://www.drupal.org/user/19668 [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-009 - Linkit - Cross Site Scripting (XSS)
by security-news＠drupal.org 07 Jan '15

07 Jan '15

View online: https://www.drupal.org/node/2403459 * Advisory ID: DRUPAL-SA-CONTRIB-2015-009 * Project: Linkit [1] (third-party module) * Version: 7.x * Date: 2015-January-07 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Linkit provides an easy interface for internal and external linking with wysiwyg editors and fields by using an autocomplete field. The module doesn't sufficiently sanitize node titles in the result list if the node search plugin is enabled. This vulnerability is mitigated by the fact that an attacker must have a role with the permission to add or edit any type of node and that the linkit node search plugin is enabled. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Linkit 7.x-2.x versions prior to 7.x-2.7. * Linkit 7.x-3.x versions prior to 7.x-3.3. Drupal core is not affected. If you do not use the contributed Linkit [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Linkit module for Drupal 7.x and Linkit 7.x-2.x, upgrade to Linkit 7.x-2.7 [5] * If you use the Linkit module for Drupal 7.x and Linkit 7.x-3.x, upgrade to Linkit 7.x-3.3 [6] Also see the Linkit [7] project page. -------- REPORTED BY --------------------------------------------------------- * Martijn Vermeulen [8] -------- FIXED BY ------------------------------------------------------------ * Emil Stjerneman [9] the module maintainer * Martijn Vermeulen [10] -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [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 https://www.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]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [16] [1] https://www.drupal.org/project/linkit [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/linkit [5] https://www.drupal.org/node/2402855 [6] https://www.drupal.org/node/2402859 [7] https://www.drupal.org/project/linkit [8] https://www.drupal.org/user/960720 [9] https://www.drupal.org/user/464598 [10] https://www.drupal.org/user/960720 [11] https://www.drupal.org/user/36762 [12] https://www.drupal.org/contact [13] https://www.drupal.org/security-team [14] https://www.drupal.org/writing-secure-code [15] https://www.drupal.org/security/secure-configuration [16] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-008 - Batch Jobs - Cross Site Request Forgery (CSRF)
by security-news＠drupal.org 07 Jan '15

07 Jan '15

View online: https://www.drupal.org/node/2403451 * Advisory ID: DRUPAL-SA-CONTRIB-2015-008 * Project: Batch Jobs [1] (third-party module) * Version: 7.x * Date: 2015-January-07 * Security risk: 15/25 ( Critical) AC:None/A:None/CI:None/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- The Batch Jobs project is a scalable way to execute a list of tasks. Links that take actions on batch jobs are not protected from Cross Site Request Forgery (CSRF). A malicious individual could cause a user that has permission to access a particular batch job (or an administrator) to dele the record of that batch job or possibly execute a task by getting the user's browser to make a request to a specially-crafted URL while the user is logged in. This vulnerability only exists when batch job data exists - i.e. during the short period it is running or if it is retained (not deleted after completion of the batch job). -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Batch Jobs 7.x-1.x versions prior to 7.x-1.2. Drupal core is not affected. If you do not use the contributed Batch Jobs [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Make sure that all batch jobs are deleted or install the latest version: * If you use the Batch Jobs project for Drupal 7.x, upgrade to Batch Jobs 7.x-1.2 [5] Also see the Batch Jobs [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team * Thomas Robey [8] the module maintainer -------- FIXED BY ------------------------------------------------------------ * Thomas Robey [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [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/batch_jobs [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/batch_jobs [5] https://www.drupal.org/node/2402839 [6] https://www.drupal.org/project/batch_jobs [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/653476 [9] https://www.drupal.org/user/653476 [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-007 - Htaccess - Cross Site Request Forgery (CSRF)
by security-news＠drupal.org 07 Jan '15

07 Jan '15

View online: https://www.drupal.org/node/2403445 * Advisory ID: DRUPAL-SA-CONTRIB-2015-007 * Project: htaccess [1] (third-party module) * Version: 7.x * Date: 2015-January-07 * Security risk: 16/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- The Htaccess module allows the creation and deployment of .htaccess files based on custom settings. Some administration links were not properly protected from Cross Site Request Forgery (CSRF). A malicious user could cause an administrator to deploy or delete .htaccess files by getting the administrator's browser to request specially crafted URLS while the administrator was logged in. -------- 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 Htaccess 7.x-2.x versions prior to 7.x-2.3. Drupal core is not affected. If you do not use the contributed htaccess [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Htaccess module for Drupal 7.x, upgrade to Htaccess 7.x-2.3 [5] Also see the htaccess [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Jibus [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [9] 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 [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/htaccess [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/htaccess [5] https://www.drupal.org/node/2402825 [6] https://www.drupal.org/project/htaccess [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/1679812 [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-006 - Cloudwords for Multilingual Drupal - Multiple vulnerabilities
by security-news＠drupal.org 07 Jan '15

07 Jan '15

View online: https://www.drupal.org/node/2403447 * Advisory ID: DRUPAL-SA-CONTRIB-2015-006 * Project: Cloudwords for Multilingual Drupal [1] (third-party module) * Version: 7.x * Date: 2015-January-07 * Security risk: 16/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting, Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- This module provides integration with the Cloudwords third-party service. The module was not sanitizing node titles on certain conditions, thereby leading to a Cross Site Scripting (XSS) vulnerability. Also, a menu callback was not protected against CSRF. The XSS vulnerability is mitigated by the fact that an attacker must have a user with permissions to create nodes. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Cloudwords for Multilingual Drupal 7.x-2.x versions prior to 7.x-2.3. Drupal core is not affected. If you do not use the contributed Cloudwords for Multilingual Drupal [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Cloudwords for Multilingual Drupal module for Drupal 7.x, upgrade to Cloudwords for Multilingual Drupal 7.x-2.3 [5] Also see the Cloudwords for Multilingual Drupal [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Eric Hildebrand [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [9] 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 [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/cloudwords [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/cloudwords [5] https://www.drupal.org/node/2402643 [6] https://www.drupal.org/project/cloudwords [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/1751082 [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-005 - WikiWiki - SQL injection
by security-news＠drupal.org 07 Jan '15

07 Jan '15

View online: https://www.drupal.org/node/2403375 * Advisory ID: DRUPAL-SA-CONTRIB-2015-005 * Project: WikiWiki [1] (third-party module) * Version: 6.x * Date: 2015-January-07 * Security risk: 22/25 ( Highly Critical) AC:None/A:None/CI:All/II:All/E:Theoretical/TD:All [2] * Vulnerability: SQL Injection -------- DESCRIPTION --------------------------------------------------------- WikiWiki module gives you one place to create, share and find wiki pages in your site. The module did not sanitize user input inside a database query thereby leading to a SQL Injection vulnerability. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * WikiWiki 6.x-1.x versions prior to 6.x-1.2. Drupal core is not affected. If you do not use the contributed WikiWiki [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the WikiWiki module for Drupal 6.x, upgrade to WikiWiki 6.x-1.2 [5] Also see the WikiWiki [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Gabriele Manna [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [9] 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 [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/wikiwiki [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/wikiwiki [5] https://www.drupal.org/node/2402905 [6] https://www.drupal.org/project/wikiwiki [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/1183748 [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-004 - Context - Open Redirect
by security-news＠drupal.org 07 Jan '15

07 Jan '15

View online: https://www.drupal.org/node/2403351 * Advisory ID: DRUPAL-SA-CONTRIB-2015-004 * Project: Context [1] (third-party module) * Version: 7.x * Date: 2015-January-07 * Security risk: 9/25 ( Less Critical) AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Open Redirect -------- DESCRIPTION --------------------------------------------------------- Context allows you to manage contextual conditions and reactions for different portions of your site. Context UI module wasn't checking for external URLs in the HTTP GET destination parameter when redirecting users that are activating/deactivating the Context UI inline editor dialog, thereby leading to an Open Redirect vulnerability. This vulnerability is mitigated by the fact that the victim must have the permission "administer contexts" and that Context UI module must be enabled. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Context 7.x-3.x versions prior to 7.x-3.6 Drupal core is not affected. If you do not use the contributed Context [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Context module for Drupal 7, upgrade to Context 7.x-3.6 [5] Also see the Context [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Pere Orga [8] provisional member of the Drupal Security Team * Chris Johnson [9], module maintainer * Yonas Yanfa [10], module maintainer -------- COORDINATED BY ------------------------------------------------------ * Owen Barton [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 https://www.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]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [16] [1] https://www.drupal.org/project/context [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/context [5] https://www.drupal.org/node/2402779 [6] https://www.drupal.org/project/context [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/2301194 [9] https://www.drupal.org/user/8134 [10] https://www.drupal.org/user/7089 [11] https://www.drupal.org/user/19668 [12] https://www.drupal.org/contact [13] https://www.drupal.org/security-team [14] https://www.drupal.org/writing-secure-code [15] https://www.drupal.org/security/secure-configuration [16] https://twitter.com/drupalsecurity

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Security-news January 2015