- Security-news - lists.drupal.org

SA-CONTRIB-2015-017 - Room Reservations - Cross Site Scripting (XSS)
by security-news＠drupal.org 14 Jan '15

14 Jan '15

View online: https://www.drupal.org/node/2407329 * Advisory ID: DRUPAL-SA-CONTRIB-2015-017 * Project: Room Reservations [1] (third-party module) * Version: 7.x * Date: 2015-January-14 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Room Reservations module enables you to manage a room reservation system. The module doesn't sufficiently sanitize the node title of "Room Reservations Category" nodes and the body of "Room Reservations Room" nodes, thereby leading to a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a user with the permission "Administer the room reservations system". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Room Reservations 7.x-1.x versions prior to 7.x-1.1. Drupal core is not affected. If you do not use the contributed Room Reservations [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Room Reservations module for Drupal 7.x, upgrade to Room Reservations 7.x-1.1 [5] Also see the Room Reservations [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Peter Lindstrom [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/room_reservations [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/room_reservations [5] https://www.drupal.org/node/2406827 [6] https://www.drupal.org/project/room_reservations [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/44114 [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-016 - Tadaa! - Multiple vulnerabilities
by security-news＠drupal.org 14 Jan '15

14 Jan '15

View online: https://www.drupal.org/node/2407321 * Advisory ID: DRUPAL-SA-CONTRIB-2015-016 * Project: Tadaa! [1] (third-party module) * Version: 7.x * Date: 2015-January-14 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:None/CI:None/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Request Forgery, Open Redirect -------- DESCRIPTION --------------------------------------------------------- Tadaa! is a module aimed at simplifying the process of enabling/disabling modules and altering configuration when switching between different environments, e.g. Production/Staging/Development. The module exposes multiple paths that were not protected against Cross Site Request Forgeries (CSRF). A malicious user could cause a user with "Use Tadaa!" permission to enable and disable modules or change variables by getting his browser to make a request to a specially-crafted URL while logged in. Also, these callbacks had a destination query parameter that was not protected against open redirects. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Tadaa! 7.x-1.x versions prior to 7.x-1.4. Drupal core is not affected. If you do not use the contributed Tadaa! [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Tadaa! module for Drupal 7.x, upgrade to Tadaa! 7.x-1.4 [5] Also see the Tadaa! [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Olof Johansson [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/tadaa [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/tadaa [5] https://www.drupal.org/node/2406949 [6] https://www.drupal.org/project/tadaa [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/u/olofjohansson [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-015 - Term Merge - Cross Site Scripting (XSS)
by security-news＠drupal.org 14 Jan '15

14 Jan '15

View online: https://www.drupal.org/node/2407315 * Advisory ID: DRUPAL-SA-CONTRIB-2015-015 * Project: Term merge [1] (third-party module) * Version: 7.x * Date: 2015-January-14 * Security risk: 12/25 ( Moderately Critical) AC:Complex/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module enables you to merge (synonymous) taxonomy terms among themselves. The module doesn't sufficiently filter user input under certain conditions, thereby opening a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must be able to create 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 --------------------------------------------------- * Term Merge 7.x-1.x versions prior to 7.x-1.2. Drupal core is not affected. If you do not use the contributed Term merge [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Term Merge module for Drupal 7.x, upgrade to Term Merge 7.x-1.2 [5] Also see the Term merge [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Alexander Trotsenko [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/term_merge [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/term_merge [5] https://www.drupal.org/node/2406869 [6] https://www.drupal.org/project/term_merge [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/504128 [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-014 - Wishlist - Multiple vulnerabilities
by security-news＠drupal.org 14 Jan '15

14 Jan '15

View online: https://www.drupal.org/node/2407313 * Advisory ID: DRUPAL-SA-CONTRIB-2015-014 * Project: Wishlist Module [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-January-14 * 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 --------------------------------------------------------- The Wishlist module enables authorized users to create wishlist nodes which describe items they would like for a special occasion. Also, it allows users to indicate their intention to purchase items for other users. The module fails to sanitize user input in log messages, leading to a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "access wishlists", and that only sites with dblog module enabled are affected (dblog module is enabled by default). Also, the paths to manage wishlist purchase intentions do not confirm the intent of a user. A malicious user could cause another user to delete wishlist purchase intentions by getting their browser to make a request to a specially-crafted URL, a Cross-Site Request Forgery (CSRF). -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Wishlist 7.x-2.x versions prior to 7.x-2.7. * Wishlist 6.x-2.x versions prior to 6.x-2.7. Drupal core is not affected. If you do not use the contributed Wishlist Module [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Wishlist module for Drupal 7.x, upgrade to Wishlist 7.x-2.7 [5]. * If you use the Wishlist module for Drupal 6.x, upgrade to Wishlist 6.x-2.7 [6]. Also see the Wishlist Module [7] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [8] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Adrian Bateman [9] the module co-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/wishlist [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/wishlist [5] https://www.drupal.org/node/2406811 [6] https://www.drupal.org/node/2406803 [7] https://www.drupal.org/project/wishlist [8] https://www.drupal.org/user/2301194 [9] https://www.drupal.org/user/795122 [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-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