- Security-news - lists.drupal.org

Display Suite - Moderately Critical - Cross Site Scripting (XSS) - SA-CONTRIB-2015-095
by security-news＠drupal.org 15 Apr '15

15 Apr '15

View online: https://www.drupal.org/node/2471733 * Advisory ID: DRUPAL-SA-CONTRIB-2015-05 * Project: Display Suite [1] (third-party module) * Version: 7.x * Date: 2015-April-15 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Display Suite allows you to take full control over how your content is displayed using a drag and drop interface. In certain situations, Display Suite does not properly sanitize some of the output, allowing a malicious user to embed scripts within a page, resulting in a Cross-site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker has to be able to configure field display settings, which usually needs a higher level permission such as administer taxonomy. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Display Suite version 7.x-2.7. Versions prior to Display Suite 7.x-2.7 are not vulnerable. Drupal core is not affected. If you do not use the contributed Display Suite [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Display Suite module for Drupal 7.x-2.7, upgrade to Display Suite 7.x-2.8 [5] Also see the Display Suite [6] project page. -------- REPORTED BY --------------------------------------------------------- * Ward Van Hooreweghe [7] * Bram Goffings [8] -------- FIXED BY ------------------------------------------------------------ * Bram Goffings [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Ivo Van Geertruyen [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/ds [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/ds [5] https://drupal.org/node/2471721 [6] https://www.drupal.org/project/ds [7] https://www.drupal.org/u/hjarnmastara [8] https://www.drupal.org/u/aspilicious [9] https://www.drupal.org/u/aspilicious [10] https://www.drupal.org/u/mr.baileys [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

Services - Critical - Multiple Vulnerabilites - SA-CONTRIB-2014-096
by security-news＠drupal.org 15 Apr '15

15 Apr '15

View online: https://www.drupal.org/node/2471879 * Advisory ID: DRUPAL-SA-CONTRIB-2015-096 * Project: Services [1] (third-party module) * Version: 7.x * Date: 2015-April-15 * Security risk: 16/25 ( Critical) AC:None/A:None/CI:Some/II:Some/E:Theoretical/TD:Uncommon [2] * Vulnerability: Access bypass, Arbitrary PHP code execution -------- DESCRIPTION --------------------------------------------------------- Services module enables you to expose an API to third party systems. .... Access bypass (file upload and execution) The resource/endpoint for uploading files does not properly sanitize the filename of uploaded files. This vulnerability is mitigated by the fact that the "File > Create" resource must be enabled and an attacker must have a role with the Services "Save file information" permission. .... Private fields information displayed Services does not check field_access when displaying entities so some private field information may be displayed. This vulnerability is only affecting sites using the field_permissions module configured to hide fields from anonymous users. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- Services 7.x-3.x versions prior to 7.x-3.12. Drupal core is not affected. If you do not use the contributed Services [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version of Services: Services 7.x-3.12 [5]. As a reminder, Services for Drupal 6 is no longer maintained. Also see the Services [6] project page. -------- REPORTED BY --------------------------------------------------------- .... Access Bypass/file upload * Fabian Franz [7] * Bevan Rudge [8] .... Private fields information displayed * giorgio79 [9] -------- FIXED BY ------------------------------------------------------------ .... Access Bypass/file upload * Bevan Rudge [10] .... Private fields information displayed * Kyle Browning [11] module maintainer -------- COORDINATED BY ------------------------------------------------------ * Ben Dougherty [12] of the Drupal Security Team * Stéphane Corlosquet [13] 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 [14]. Learn more about the Drupal Security team and their policies [15], writing secure code for Drupal [16], and securing your site [17]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [18] [1] https://www.drupal.org/project/services [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/services [5] https://www.drupal.org/node/2471847 [6] https://www.drupal.org/project/services [7] https://www.drupal.org/u/fabianx [8] https://www.drupal.org/u/bevan [9] https://www.drupal.org/user/235790 [10] https://www.drupal.org/u/bevan [11] https://www.drupal.org/u/kylebrowning [12] https://www.drupal.org/u/benjy [13] https://www.drupal.org/u/scor [14] https://www.drupal.org/contact [15] https://www.drupal.org/security-team [16] https://www.drupal.org/writing-secure-code [17] https://www.drupal.org/security/secure-configuration [18] https://twitter.com/drupalsecurity

1 0

CiviCRM private report - Moderately Critical - Cross Site Request Forgery (CSRF) - SA-CONTRIB-2015-094
by security-news＠drupal.org 08 Apr '15

08 Apr '15

View online: https://www.drupal.org/node/2467697 * Advisory ID: DRUPAL-SA-CONTRIB-2015-094 * Project: CiviCRM private report [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-April-08 * 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 --------------------------------------------------------- CiviCRM private report module enables users to create their own private copies of CiviCRM reports, which they can modify and save to meet their needs without requiring the "Administer reports" permission. The module doesn't sufficiently protect some links against CSRF. A malicious user can cause another user to delete reports by getting their browser to make a request to a specially-crafted URL. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * CiviCRM private report 6.x-1.x versions prior to 6.x-1.2. * CiviCRM private report 7.x-1.x versions prior to 7.x-1.3. Drupal core is not affected. If you do not use the contributed CiviCRM private report [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the CiviCRM private report module for Drupal 6.x, upgrade to CiviCRM private report 6.x-1.2 [5] * If you use the CiviCRM private report module for Drupal 7.x, upgrade to CiviCRM private report 7.x-1.3 [6] Also see the CiviCRM private report [7] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [8] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * TwoMice [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [10] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact [11]. Learn more about the Drupal Security team and their policies [12], writing secure code for Drupal [13], and securing your site [14]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/civicrm_private_report [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/civicrm_private_report [5] https://www.drupal.org/node/2467635 [6] https://www.drupal.org/node/2467631 [7] https://www.drupal.org/project/civicrm_private_report [8] https://www.drupal.org/user/2301194 [9] https://www.drupal.org/user/600924 [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

User Import - Moderately Critical - Cross Site Request Forgery (CSRF) - SA-CONTRIB-2015-093
by security-news＠drupal.org 01 Apr '15

01 Apr '15

View online: https://www.drupal.org/node/2463949 * Advisory ID: DRUPAL-SA-CONTRIB-2015-093 * Project: User Import [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-April-01 * 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 the import of users into Drupal, or the update of existing users, with data from a CSV file (comma separated file). Some management URLs were not properly protected. A malicious user could trick an administrator into continuing or deleting an ongoing import by getting them to request certain URLs, thereby leading to a Cross Site Request Forgery (CSRF) 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 --------------------------------------------------- * User Import 6.x-2.x versions prior to 6.x-4.4 * User Import 7.x-2.x versions prior to 7.x-2.3 Drupal core is not affected. If you do not use the contributed User Import [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the User Import module for Drupal 6.x, upgrade to User Import 6.x-4.4 [5] * If you use the User Import module for Drupal 7.x, upgrade to User Import 7.x-2.3 [6] Also see the User Import [7] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [8] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Robert Castelo [9] module maintainer and member of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [10] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact [11]. Learn more about the Drupal Security team and their policies [12], writing secure code for Drupal [13], and securing your site [14]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/user_import [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/user_import [5] https://www.drupal.org/node/2463943 [6] https://www.drupal.org/node/2463941 [7] https://www.drupal.org/project/user_import [8] https://www.drupal.org/user/2301194 [9] https://www.drupal.org/user/3555 [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

Open Graph Importer - Moderately Critical - Access bypass - Unsupported - SA-CONTRIB-2015-092
by security-news＠drupal.org 01 Apr '15

01 Apr '15

View online: https://www.drupal.org/node/2463891 * Advisory ID: DRUPAL-SA-CONTRIB-2015-092 * Project: Open Graph Importer [1] (third-party module) * Version: 7.x * Date: 2015-April-01 * Security risk: 10/25 ( Moderately Critical) AC:Basic/A:User/CI:None/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to import content from a web page by scraping its Open Graph data. The module doesn't sufficiently check for "create" permission to the content type that is configured as the destination for imported content, thus allowing a user with the "import og_tag_importer" permission to create content regardless of other permissions. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * og_tag_importer 7.x-1.x versions. Drupal core is not affected. If you do not use the contributed Open Graph Importer [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Disable the module. There is no safe version of the module to use. Also see the Open Graph Importer [5] project page. -------- REPORTED BY --------------------------------------------------------- * Chang Xiao [6] the module maintainer * Cameron Eagans [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * David Stoline [8] of the Drupal Security Team * Damien McKenna [9] of the Drupal Security Team (provisional) -------- 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/og_tag_importer [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/og_tag_importer [5] https://www.drupal.org/project/og_tag_importer [6] https://www.drupal.org/u/xcf33 [7] https://www.drupal.org/user/404732 [8] https://www.drupal.org/user/329570 [9] https://www.drupal.org/user/108450 [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

Current Search Links - Critical - Cross Site Scripting (XSS) - SA-CONTRIB-2015-091
by security-news＠drupal.org 01 Apr '15

01 Apr '15

View online: https://www.drupal.org/node/2463843 * Advisory ID: DRUPAL-SA-CONTRIB-2015-091 * Project: Current Search Links [1] (third-party module) * Version: 7.x * Date: 2015-April-01 * Security risk: 15/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Current Search Links module is an extension to the Facet API Current Search Blocks module. Instead of just showing the current search it turns the current search keywords into links that you can drop from the search. The module doesn't sufficiently sanitize the entered search query, thereby exposing a XSS vulnerability. An attacker could exploit this vulnerability by getting the victim to visit a specially-crafted URL. This is mitigated by the fact that only sites with the option "Append the keywords passed by the user to the list" disabled 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 --------------------------------------------------- * Current Search Links 7.x-1.x versions prior to 7.x-1.1. Drupal core is not affected. If you do not use the contributed Current Search Links [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Current Search Links module for Drupal 7.x, upgrade to Current Search Links 7.x-1.1 [5] Also see the Current Search Links [6] project page. -------- REPORTED BY --------------------------------------------------------- * Sogeti security team * Martijn de Wit [7] -------- FIXED BY ------------------------------------------------------------ * Johnny van de Laar [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [9] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [14] [1] https://www.drupal.org/project/current_search_links [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/current_search_links [5] https://www.drupal.org/node/2463493 [6] https://www.drupal.org/project/current_search_links [7] https://www.drupal.org/user/83953 [8] https://www.drupal.org/user/248932 [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

Password Policy - Critical - Cross Site Scripting (XSS) - SA-CONTRIB-2015-090
by security-news＠drupal.org 01 Apr '15

01 Apr '15

View online: https://www.drupal.org/node/2463835 * Advisory ID: DRUPAL-SA-CONTRIB-2015-090 * Project: Password policy [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-April-01 * Security risk: 15/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Password Policy module allows enforcing restrictions on user passwords by defining password policies. The module doesn't sufficiently sanitize usernames in some administration pages, thereby exposing a Cross Site Scripting vulnerability. This vulnerability is mitigated by the fact that only sites with a policy that uses the username constraint are affected. Also, only sites importing users from an external source (like distributed authentication) may allow non-standard usernames that might contain malicious characters, as Drupal core has validation when creating users via the user interface. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Password Policy 6.x-1.x versions prior to 6.x-1.11. * Password Policy 7.x-1.x versions prior to 7.x-1.11. Drupal core is not affected. If you do not use the contributed Password policy [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Password Policy 6.x-1.x module for Drupal 6.x, upgrade to Password Policy 6.x-1.11 [5] * If you use the Password Policy 7.x-1.x module for Drupal 7.x, upgrade to Password Policy 7.x-1.11 [6] Also see the Password policy [7] project page. -------- REPORTED BY --------------------------------------------------------- * AohRveTPV [8], the module maintainer -------- FIXED BY ------------------------------------------------------------ * AohRveTPV [9], the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [10] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact [11]. Learn more about the Drupal Security team and their policies [12], writing secure code for Drupal [13], and securing your site [14]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/password_policy [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/password_policy [5] https://www.drupal.org/node/2463329 [6] https://www.drupal.org/node/2463327 [7] https://www.drupal.org/project/password_policy [8] https://www.drupal.org/user/aohrveptv [9] https://www.drupal.org/user/aohrvetpv [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

EntityBulkDelete - Critical - Cross Site Scripting (XSS) - SA-CONTRIB-2015-089
by security-news＠drupal.org 01 Apr '15

01 Apr '15

View online: https://www.drupal.org/node/2463831 * Advisory ID: DRUPAL-SA-CONTRIB-2015-089 * Project: EntityBulkDelete [1] (third-party module) * Version: 7.x * Date: 2015-April-01 * Security risk: 16/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- EntityBulkDelete module allows you to delete entities in bulk using the Batch API. The module doesn't sufficiently sanitize user supplied text in some administration pages, thereby exposing a Cross Site Scripting vulnerability. This vulnerability is mitigated by the fact that an attacker must be allowed to create/edit comments, create/edit taxonomy terms or create/edit 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 --------------------------------------------------- * EntityBulkDelete 7.x-1.0 Drupal core is not affected. If you do not use the contributed EntityBulkDelete [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the EntityBulkDelete module for Drupal 7.x, download EntityBulkDelete 7.x-1.1 [5] Also see the EntityBulkDelete [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Rahul Seth [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [9] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [14] [1] https://www.drupal.org/project/entitybulkdelete [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/entitybulkdelete [5] https://www.drupal.org/node/2463049 [6] https://www.drupal.org/project/entitybulkdelete [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/u/rahul-seth [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

Imagefield Info - Moderately Critical - Cross Site Scripting (XSS) - SA-CONTRIB-2015-088
by security-news＠drupal.org 01 Apr '15

01 Apr '15

View online: https://www.drupal.org/node/2463823 * Advisory ID: DRUPAL-SA-CONTRIB-2015-088 * Project: Imagefield Info [1] (third-party module) * Version: 7.x * Date: 2015-April-01 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Imagefield Info module enables you to view image field paths so you can easily use them with a WYSIWYG editor. The module doesn't sufficiently sanitize user supplied text in some administration pages, thereby exposing a Cross Site Scripting vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Administer image styles". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Imagefield Info 7.x-1.x versions prior to 7.x-1.2 Drupal core is not affected. If you do not use the contributed Imagefield Info [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Imagefield Info module for Drupal 7.x, upgrade to Imagefield Info 7.x-1.2 [5] Also see the Imagefield Info [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Peter Lachky [8] the module maintainer * Pere Orga [9] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [10] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact [11]. Learn more about the Drupal Security team and their policies [12], writing secure code for Drupal [13], and securing your site [14]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/imagefield_info [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/imagefield_info [5] https://www.drupal.org/node/2463237 [6] https://www.drupal.org/project/imagefield_info [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/1437 [9] https://www.drupal.org/user/2301194 [10] https://www.drupal.org/user/2301194 [11] https://www.drupal.org/contact [12] https://www.drupal.org/security-team [13] https://www.drupal.org/writing-secure-code [14] https://www.drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

Ubercart Webform Checkout Pane - Moderately Critical - Cross Site Scripting (XSS) - Unsupported - SA-CONTRIB-2015-087
by security-news＠drupal.org 25 Mar '15

25 Mar '15

View online: https://www.drupal.org/node/2459359 * Advisory ID: DRUPAL-SA-CONTRIB-2015-087 * Project: Ubercart Webform Checkout Pane [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-March-25 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Ubercart Webform Checkout Pane module allows you to define Webform nodes as checkout/order panes in Ubercart. The module doesn't sufficiently sanitize user supplied text in some pages, thereby exposing a Cross Site Scripting vulnerability. This vulnerability is mitigated by the fact that an attacker must have a user with permission to create/edit Ubercart products or webforms. -------- 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 Ubercart Webform Checkout Pane module Drupal core is not affected. If you do not use the contributed Ubercart Webform Checkout Pane [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Ubercart Webform Checkout Pane module you should uninstall it. Also see the Ubercart Webform Checkout Pane [5] project page. -------- REPORTED BY --------------------------------------------------------- * Joel Stein [6] * Dylan Tack [7] of the Drupal Security Team * Pere Orga [8] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [9] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [14] [1] https://www.drupal.org/project/uc_webform_pane [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/uc_webform_pane [5] https://www.drupal.org/project/uc_webform_pane [6] https://www.drupal.org/user/36598 [7] https://www.drupal.org/user/96647 [8] https://www.drupal.org/user/2301194 [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