- Security-news - lists.drupal.org

SA-CONTRIB-2015-027 - Quizzler - Cross Site Scripting (XSS)
by security-news＠drupal.org 22 Jan '15

22 Jan '15

View online: https://www.drupal.org/node/2411579 * Advisory ID: DRUPAL-SA-CONTRIB-2015-027 * Project: Quizzler [1] (third-party module) * Version: 7.x * Date: 2015-January-21 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Quizzler module allows you to create online quizzes and tests. Quizzes are nodes with questions attached. The module does not sanitize user input in the node title when displaying it on the page, allowing a malicious user to inject code, a Cross Site Scripting (XSS) attack. This vulnerability is mitigated by the fact that an attacker must have a role that allows them to create nodes or edit nodes that are assigned as quizzes. -------- 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 prior to 7.x-1.16. Drupal core is not affected. If you do not use the contributed Quizzler [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Quizzler module, upgrade to Quizzler 7-x.1.16 [5] Also see the Quizzler [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Aaron Craig [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/quizzler [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/quizzler [5] https://www.drupal.org/node/2410399 [6] https://www.drupal.org/project/quizzler [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/118575 [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-026 - Taxonews - Cross Site Scripting (XSS)
by security-news＠drupal.org 22 Jan '15

22 Jan '15

View online: https://www.drupal.org/node/2411573 * Advisory ID: DRUPAL-SA-CONTRIB-2015-026 * Project: Taxonews [1] (third-party module) * Version: 5.x, 6.x, 7.x * Date: 2015-January-21 * 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 create blocks of nodes carrying a given taxonomy term. The module doesn't sufficiently escape term names in the blocks it builds 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 "administer taxonomy" or the ability to create terms in some other way. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Taxonews 7.x-1.x versions prior to 7.x-1.1. * Taxonews 6.x-1.x versions prior to 6.x-1.2. Drupal core is not affected. If you do not use the contributed Taxonews [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version of Taxonews module: * For Drupal 7.x, upgrade to Taxonews 7.x-1.1 [5] * For Drupal 6.x, upgrade to Taxonews 6.x-1.2 [6] Also see the Taxonews [7] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [8] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * FGM [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/taxonews [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/taxonews [5] https://www.drupal.org/node/2409769 [6] https://www.drupal.org/node/2409767 [7] https://www.drupal.org/project/taxonews [8] https://www.drupal.org/user/2301194 [9] https://www.drupal.org/user/27985 [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-025 - Patterns - Cross Site Request Forgery (CSRF)
by security-news＠drupal.org 22 Jan '15

22 Jan '15

View online: https://www.drupal.org/node/2411539 * Advisory ID: DRUPAL-SA-CONTRIB-2015-025 * Project: Patterns [1] (third-party module) * Version: 7.x * Date: 2015-January-21 * 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 --------------------------------------------------------- Patterns module manages and automates site configuration. Site configurations stored in XML or YAML are called Patterns, and these are easy to read, modify, manage & share and can be executed manually or as a part of an automated web site deployment. Some links were not protected against CSRF. A malicious user could cause an administrator to restore, publish and unpublish patterns by getting the administrator's 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 --------------------------------------------------- * Patterns 7.x-2.x versions prior to 7.x-2.2. Drupal core is not affected. If you do not use the contributed Patterns [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Patterns module for Drupal 7.x, upgrade to Patterns 7.x-2.2 [5] Also see the Patterns [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * David Rozas [8], one of the module maintainers -------- 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/patterns [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/patterns [5] https://www.drupal.org/node/2411507 [6] https://www.drupal.org/project/patterns [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/740628 [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-024 - Alfresco - Cross Site Request Forgery (CSRF)
by security-news＠drupal.org 22 Jan '15

22 Jan '15

View online: https://www.drupal.org/node/2411523 * Advisory ID: DRUPAL-SA-CONTRIB-2015-0XX * Project: Alfresco [1] (third-party module) * Version: 6.x * Date: 2015-January-21 * 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 --------------------------------------------------------- The Alfresco module provides integration between Drupal and Alfresco via Content Management Web Services (SOAP) and Repository RESTful API. The Alfresco Browser submodule provides an AJAX-based repository browser that allows users to visualize, upload, search and retrieve nodes from the Alfresco repository. Some links from Alfresco Browser were not properly protected from CSRF. A malicious user could cause a user to delete alfresco nodes 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 --------------------------------------------------- * Alfresco 6.x-1.x versions prior to 6.x-1.3. Drupal core is not affected. If you do not use the contributed Alfresco [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Alfresco module for Drupal 6.x, upgrade to Alfresco 6.x-1.3 [5] Also see the Alfresco [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Sergio Martín Morillas [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/alfresco [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/alfresco [5] https://www.drupal.org/node/2411501 [6] https://www.drupal.org/project/alfresco [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/191570 [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-023 - Classified Ads - Cross Site Scripting (XSS)
by security-news＠drupal.org 22 Jan '15

22 Jan '15

View online: https://www.drupal.org/node/2411527 * Advisory ID: DRUPAL-SA-CONTRIB-2015-023 * Project: Classified Ads [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-January-21 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Classified Ads module enables administrators to create classified ads in various categories. The module doesn't correctly escape the category names in its administration user interface. 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 --------------------------------------------------- * Classified Ads 6.x-3.x versions prior to 6.x-3.1. * Classified Ads 7.x-3.x versions prior to 7.x-3.1. Drupal core is not affected. If you do not use the contributed Classified Ads [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Classified Ads module for Drupal 6.x, upgrade to Classified Ads 6.x-3.1 [5] * If you use the Classified Ads module for Drupal 7.x, upgrade to Classified Ads 7.x-3.1 [6] Also see the Classified Ads [7] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [8] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Frédéric Marand [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [10] provisional member of the Drupal Security Team * Klaus Purer [11] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at 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/ed_classified [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/ed_classified [5] https://www.drupal.org/node/2407783 [6] https://www.drupal.org/node/2407785 [7] https://www.drupal.org/project/ed_classified [8] https://www.drupal.org/user/2301194 [9] https://www.drupal.org/user/27985 [10] https://www.drupal.org/user/2301194 [11] https://www.drupal.org/u/klausi [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-022 - nodeauthor - Cross Site Scripting (XSS) - Unsupported
by security-news＠drupal.org 14 Jan '15

14 Jan '15

View online: https://www.drupal.org/node/2407401 * Advisory ID: DRUPAL-SA-CONTRIB-2015-022 * Project: nodeauthor [1] (third-party module) * Version: 7.x * Date: 2015-January-14 * Security risk: 12/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module displays node author information in a jQuery slider. The module doesn't sufficiently sanitize Profile2 fields in a provided block. This vulnerability is mitigated by the fact that an attacker must have a user account allowed to edit profile fields. -------- 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 nodeauthor module. Drupal core is not affected. If you do not use the contributed nodeauthor [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the nodeauthor module you should uninstall it. Also see the nodeauthor [5] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [6] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [7] 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 [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/node_author [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/node_author [5] https://www.drupal.org/project/node_author [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

SA-CONTRIB-2015-021 - Content Analysis - Cross Site Scripting (XSS)
by security-news＠drupal.org 14 Jan '15

14 Jan '15

View online: https://www.drupal.org/node/2407395 * Advisory ID: DRUPAL-SA-CONTRIB-2015-021 * Project: Content Analysis [1] (third-party module) * Version: 6.x * Date: 2014-January-14 * Security risk: 16/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Content Analysis module is an API designed to help modules that need to analyze content. 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 only sites with dblog module enabled are affected. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Content Analysis 6.x-1.x versions prior to 6.x-1.7. Drupal core is not affected. If you do not use the contributed Content Analysis [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Content Analysis module for Drupal 6.x, upgrade to Content Analysis 6.x-1.7 [5] Also see the Content Analysis [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Tom McCracken [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/contentanalysis [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/contentanalysis [5] https://www.drupal.org/node/2407261 [6] https://www.drupal.org/project/contentanalysis [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/258411 [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-020 - Contact Form Fields - Cross Site Request Forgery (CSRF)
by security-news＠drupal.org 14 Jan '15

14 Jan '15

View online: https://www.drupal.org/node/2407357 * Advisory ID: DRUPAL-SA-CONTRIB-2015-020 * Project: Contact form fields [1] (third-party module) * Version: 6.x * Date: 2014-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 -------- DESCRIPTION --------------------------------------------------------- The Contact Form Fields module enables you to create additional fields to site-wide contact form. Some links were not properly protected from CSRF. A malicious user could cause an administrator to delete fields 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 --------------------------------------------------- * All Contact Form Fields versions prior to 6.x-2.3. Drupal core is not affected. If you do not use the contributed Contact form fields [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Contact Form Fields module for Drupal 6.x, upgrade to Contact Form Fields 6.x-2.3 [5] Also see the Contact form fields [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Timofey Denisov [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/contact_field [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/contact_field [5] https://www.drupal.org/node/2407147 [6] https://www.drupal.org/project/contact_field [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/2740599 [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-019 - Ubercart Currency Conversion - Open Redirect
by security-news＠drupal.org 14 Jan '15

14 Jan '15

View online: https://www.drupal.org/node/2407347 * Advisory ID: DRUPAL-SA-CONTRIB-2015-019 * Project: Ubercart Currency Conversion [1] (third-party module) * Version: 6.x * Date: 2015-January-14 * Security risk: 10/25 ( Moderately Critical) AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:All [2] * Vulnerability: Open Redirect -------- DESCRIPTION --------------------------------------------------------- This module enables users to change the currency of Ubercart products. When switching the currency, the user is redirected to a page specified in the destination query parameter. The module was not checking that the passed argument was an internal URL, thereby leading to an open redirect 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 --------------------------------------------------- * Ubercart Currency Conversion 6.x-1.x versions prior to 6.x-1.2 Drupal core is not affected. If you do not use the contributed Ubercart Currency Conversion [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ * If you use the Ubercart Currency Conversion module for Drupal 6.x, upgrade to Ubercart Currency Conversion 6.x-1.2 [5] Also see the Ubercart Currency Conversion [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Sudhir Krishna S [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/uc_currency_convert [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/uc_currency_convert [5] https://www.drupal.org/node/2407145 [6] https://www.drupal.org/project/uc_currency_convert [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/554988 [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-018 - Video - Cross Site Scripting (XSS)
by security-news＠drupal.org 14 Jan '15

14 Jan '15

View online: https://www.drupal.org/node/2407341 * Advisory ID: DRUPAL-SA-CONTRIB-2015-018 * Project: Video [1] (third-party module) * Version: 7.x * Date: 2015-January-14 * 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 you to upload, convert and playback videos. The module doesn't sufficiently sanitize node titles when using the video WYSIWYG plugin, thereby opening a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "create video nodes" and that WYSIWYG video plugin 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 --------------------------------------------------- * Video 7.x-2.x versions from 7.x-2.2-beta1 to 7.x-2.10. Drupal core is not affected. If you do not use the contributed Video [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the video module for Drupal 7.x-2.x, upgrade to Video 7.x-2.11 [5] Also see the Video [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Heshan Wanigasooriya [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/video [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/video [5] https://www.drupal.org/node/2407047 [6] https://www.drupal.org/project/video [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/u/heshan.lk [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