Security-news

security-news@drupal.org

1 participants
1782 discussions

SA-CONTRIB-2014-038 - SimpleCorp theme - Cross Site Scripting
by security-news＠drupal.org 09 Apr '14

09 Apr '14

View online: https://drupal.org/node/2236811 * Advisory ID: DRUPAL-SA-CONTRIB-2014-038 * Project: SimpleCorp [1] (third-party theme) * Version: 7.x * Date: 2014-April-09 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- SimpleCorp theme is a free responsive Drupal theme. The SimpleCorp theme does not properly sanitize theme settings before they are used in the output of a page. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer themes". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Simplecorp-7.x-1.0 Drupal core is not affected. If you do not use the contributed SimpleCorp [4] theme, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the SimpleCorp theme 7.x-1.0 for Drupal 7.x, upgrade to SimpleCorp theme 7.x-1.1. [5] Also see the SimpleCorp [6] project page. -------- REPORTED BY --------------------------------------------------------- * Dennis Walgaard [7] -------- FIXED BY ------------------------------------------------------------ * George Tsopouridis [8] the theme maintainer -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [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 http://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] http://drupal.org/project/simplecorp [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/simplecorp [5] https://drupal.org/node/2236255 [6] http://drupal.org/project/simplecorp [7] https://drupal.org/user/883702 [8] http://drupal.org/user/829430 [9] https://drupal.org/user/262198 [10] http://drupal.org/contact [11] http://drupal.org/security-team [12] http://drupal.org/writing-secure-code [13] http://drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-037 - BlueMasters - Cross Site Scripting
by security-news＠drupal.org 09 Apr '14

09 Apr '14

View online: https://drupal.org/node/2236797 * Advisory ID: DRUPAL-SA-CONTRIB-2014-037 * Project: BlueMasters [1] (third-party module) * Version: 7.x * Date: 2014-April-09 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Bluemasters is a responsive layout theme for Drupal 7. The Bluemasters theme does not properly sanitize theme settings before they are used in the output of a page. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer themes". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Bluemasters 7.x-2.x versions prior to 7.x-2.1. Drupal core is not affected. If you do not use the contributed BlueMasters [4] theme, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Bluemasters theme 7.x-2.0 for Drupal 7.x, upgrade to Bluemasters 7.x-2.1 [5]. Also see the BlueMasters [6] project page. -------- REPORTED BY --------------------------------------------------------- * Dennis Walgaard [7] -------- FIXED BY ------------------------------------------------------------ * George Tsopouridis [8] the theme maintainer -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [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 http://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] http://drupal.org/project/bluemasters [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/bluemasters [5] https://drupal.org/node/2236251 [6] http://drupal.org/project/bluemasters [7] https://drupal.org/user/883702 [8] http://drupal.org/user/829430 [9] https://drupal.org/user/262198 [10] http://drupal.org/contact [11] http://drupal.org/security-team [12] http://drupal.org/writing-secure-code [13] http://drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-035 - CAS Server - Access Bypass
by security-news＠drupal.org 02 Apr '14

02 Apr '14

View online: https://drupal.org/node/2231663 * Advisory ID: DRUPAL-SA-CONTRIB-2014-035 * Project: CAS [1] (third-party module) * Version: 6.x, 7.x * Date: 2014-April-02 * Security risk: Critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The cas_server module of the CAS project implements the CAS 1.0 and 2.0 specifications for providing a single sign-on to relying party web application (the "service" in CAS specs). The CAS server creates single-use tickets when serving a user's login request, which is subsequently deleted when the relying party validates the ticket. However, this successful validation will be cached if the Drupal page cache is enabled, and subsequent identical validations can be processed even though the single-use ticket has been deleted. A user's session on a relying party can be therefore be re-initialized via a session replay attack involving the cas_server module, even when the user deletes cookies and server-side sessions for both sites. This would require an attacker to sniff the service URL containing the ticket ID, such as with a non-SSL relying party, by protocol downgrade, or by accessing an earlier user's web activity on a public computer. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * CAS Server 6.x-2.x versions prior to 6.x-3.3. * CAS Server 7.x-2.x versions prior to 7.x-1.3. Drupal core is not affected. If you do not use the contributed CAS [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the CAS Server module for Drupal 6.x, upgrade to CAS Server 6.x-3.3 [5] * If you use the CAS Server module for Drupal 7.x, upgrade to CAS Server 7.x-1.3 [6] Also see the CAS [7] project page. -------- REPORTED BY --------------------------------------------------------- * Eric Searcy [8] * Greg Knaddison [9] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Eric Searcy [10] * Tim Yale [11], the module maintainer * Greg Knaddison [12] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [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 http://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] http://drupal.org/project/cas [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/cas [5] https://drupal.org/node/2231659 [6] https://drupal.org/node/2231657 [7] http://drupal.org/project/cas [8] http://drupal.org/user/137284 [9] http://drupal.org/user/36762 [10] http://drupal.org/user/137284 [11] http://drupal.org/user/2413764 [12] http://drupal.org/user/36762 [13] http://drupal.org/user/36762 [14] http://drupal.org/contact [15] http://drupal.org/security-team [16] http://drupal.org/writing-secure-code [17] http://drupal.org/security/secure-configuration [18] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-034 - Custom Search - Cross Site Scripting
by security-news＠drupal.org 02 Apr '14

02 Apr '14

View online: https://drupal.org/node/2231665 * Advisory ID: DRUPAL-SA-CONTRIB-2014-034 * Project: Custom Search [1] (third-party module) * Version: 6.x, 7.x * Date: 2014-April-02 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Custom Search module alters the default search box to provide additional search filtering options and control. Custom Search contains a persistent cross-site scripting (XSS) vulnerability due to the fact that it fails to sanitize filter labels before display. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer custom search." -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Custom Search 6.x-1.x versions prior to 6.x-1.12. * Custom Search 7.x-1.x versions prior to 7.x-1.14. Drupal core is not affected. If you do not use the contributed Custom Search [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Custom Search module for Drupal 6.x, upgrade to Custom Search 6.x-1.12 [5] * If you use the Custom Search module for Drupal 7.x, upgrade to Custom Search 7.x-1.14 [6] Also see the Custom Search [7] project page. -------- REPORTED BY --------------------------------------------------------- * Justin C. Klein Keane [8] -------- FIXED BY ------------------------------------------------------------ * Justin C. Klein Keane [9] * Jérôme Danthinne [10], module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [11] of the Drupal Security Team * Ben Jeavons [12] 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 http://drupal.org/contact [13]. Learn more about the Drupal Security team and their policies [14], writing secure code for Drupal [15], and securing your site [16]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [17] [1] http://drupal.org/project/custom_search [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/custom_search [5] https://drupal.org/node/2231533 [6] https://drupal.org/node/2231531 [7] http://drupal.org/project/custom_search [8] http://drupal.org/user/302225 [9] http://drupal.org/user/302225 [10] https://drupal.org/user/313766 [11] https://drupal.org/user/36762 [12] http://drupal.org/user/91990 [13] http://drupal.org/contact [14] http://drupal.org/security-team [15] http://drupal.org/writing-secure-code [16] http://drupal.org/security/secure-configuration [17] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-036 - Print - Cross Site Scripting
by security-news＠drupal.org 02 Apr '14

02 Apr '14

View online: https://drupal.org/node/2231671 * Advisory ID: DRUPAL-SA-CONTRIB-2014-036 * Project: Printer, email and PDF versions [1] (third-party module) * Version: 6.x, 7.x * Date: 2014-April-02 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module provides printer-friendly versions of content, including send by e-mail and PDF versions. The module does not sufficiently sanitize user provided input when generating the printed version of a node. This is mitigated by the fact that an attacker must have permission to create a node which offers the print functionality. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Printer, email and PDF versions 6.x-1.x versions prior to 6.x-1.19. * Printer, email and PDF versions 7.x-1.x versions prior to 7.x-1.3. * Printer, email and PDF versions 7.x-2.x versions prior to 7.x-2.0. Drupal core is not affected. If you do not use the contributed Printer, email and PDF versions [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Printer, email and PDF versions module for Drupal 6.x, upgrade to print 6.x-1.19 [5] * If you use the Printer, email and PDF versions module for Drupal 7.x, upgrade to print 7.x-1.3 [6] or print 7.x-2.0 [7] Also see the Printer, email and PDF versions [8] project page. -------- REPORTED BY --------------------------------------------------------- * Dinesh Waghmare [9] -------- FIXED BY ------------------------------------------------------------ * Dinesh Waghmare [10] * Cash Williams [11] provisional member of the Drupal Security Team * João Ventura [12] the module maintainer * Heine Deelstra [13] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Heine Deelstra [14] 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 http://drupal.org/contact [15]. Learn more about the Drupal Security team and their policies [16], writing secure code for Drupal [17], and securing your site [18]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [19] [1] http://drupal.org/project/print [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/print [5] https://drupal.org/node/2231191 [6] https://drupal.org/node/2231197 [7] https://drupal.org/node/2231199 [8] http://drupal.org/project/print [9] http://drupal.org/user/2279292 [10] http://drupal.org/user/2279292 [11] http://drupal.org/user/421070 [12] http://drupal.org/user/122464 [13] http://drupal.org/user/17943 [14] http://drupal.org/user/17943 [15] http://drupal.org/contact [16] http://drupal.org/security-team [17] http://drupal.org/writing-secure-code [18] http://drupal.org/security/secure-configuration [19] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-033 - Nivo Slider - Cross Site Scripting
by security-news＠drupal.org 19 Mar '14

19 Mar '14

View online: https://drupal.org/node/2221481 * Advisory ID: DRUPAL-SA-CONTRIB-2014-033 * Project: Nivo Slider [1] (third-party module) * Version: 7.x * Date: 2014-March-19 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Nivo Slider provides a way to showcase featured content. Nivo Slider gives administrators a simple method of adding slides to the slideshow, an administration interface to configure slideshow settings, and simple slider positioning using the Drupal block system. The module doesn't sufficiently sanitize the title of images in the slider. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer nivo slider". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Nivo Slider 7.x-2.x versions prior to 7.x-1.11. Drupal core is not affected. If you do not use the contributed Nivo Slider [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Nivo Slider module for Drupal 7.x, upgrade to Nivo Slider 7.x.1.11 [5] Also see the Nivo Slider [6] project page. -------- REPORTED BY --------------------------------------------------------- * James Davis [7] -------- FIXED BY ------------------------------------------------------------ * Devin Carlson (module maintainer) [8] * James Davis [9] -------- COORDINATED BY ------------------------------------------------------ * Domenic Santangelo [10] provisional member of the Drupal Security Team * Ben Jeavons [11] of the Drupal Security Team * Greg Knaddison [12] of the Drupal Security Team * Lee Rowlands [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 http://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] http://drupal.org/project/nivo_slider [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/nivo_slider [5] https://drupal.org/node/2220545 [6] http://drupal.org/project/nivo_slider [7] http://drupal.org/user/2766355 [8] https://drupal.org/user/290182 [9] http://drupal.org/user/2766355 [10] https://drupal.org/user/173461 [11] http://drupal.org/user/91990 [12] https://drupal.org/user/36762 [13] https://drupal.org/user/395439 [14] http://drupal.org/contact [15] http://drupal.org/security-team [16] http://drupal.org/writing-secure-code [17] http://drupal.org/security/secure-configuration [18] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-032 - Xapian integration - Access Bypass
by security-news＠drupal.org 19 Mar '14

19 Mar '14

View online: https://drupal.org/node/2221403 * Advisory ID: DRUPAL-SA-CONTRIB-2014-032 * Project: Xapian integration [1] (third-party module) * Version: 6.x, 7.x * Date: 2014-March-19 * Security risk: Not critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to use Xapian system to do searches of a Xapian index from within drupal. The module doesn't verify node access rights when a node is loaded for display after the search happened in Xapian. This vulnerability is mitigated by the fact that the system must be using a node access control module. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Xapian integration 6.x-2.x versions prior to 6.x-2.2. * Xapian integration 7.x-2.x versions prior to 7.x-1.2. Drupal core is not affected. If you do not use the contributed Xapian integration [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Xapian integration module for Drupal 6.x, upgrade to Xapian integration 6.x-2.2 [5] * If you use the Xapian integration module for Drupal 7.x, upgrade to Xapian integration 7.x-1.2 [6] Also see the Xapian integration [7] project page. -------- REPORTED BY --------------------------------------------------------- * Antonello Lobianco [8]. -------- FIXED BY ------------------------------------------------------------ * Marco Villegas [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [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 http://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] http://drupal.org/project/xapian [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/xapian [5] https://drupal.org/node/2220483 [6] https://drupal.org/node/2220487 [7] http://drupal.org/project/xapian [8] https://drupal.org/user/170459 [9] http://drupal.org/user/132175 [10] https://drupal.org/user/36762 [11] http://drupal.org/contact [12] http://drupal.org/security-team [13] http://drupal.org/writing-secure-code [14] http://drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-031 - Webform Template - Access Bypass
by security-news＠drupal.org 12 Mar '14

12 Mar '14

View online: https://drupal.org/node/2216607 * Advisory ID: DRUPAL-SA-CONTRIB-2014-031 * Project: Webform Template [1] (third-party module) * Version: 7.x * Date: 2014-March-12 * Security risk: Less critical [2] * Exploitable from: Remote * Vulnerability: Access Bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to copy webform config from one node to another. The module doesn't respect node access when providing possible nodes to copy from. As a result, a user may be disclosed the titles of nodes he does not have view access to and as such he may be able to copy the webform configuration from otherwise hidden nodes. This vulnerability is mitigated by the fact that the system must be using a node access control module and an attacker must have a role that has access to edit nodes of the "webform template destination" type. -------- 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 Webform Template 6.x-1.x versions. * Webform Template 7.x-1.x versions prior to 7.x-1.3. Drupal core is not affected. If you do not use the contributed Webform Template [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Webform Template module for Drupal 7.x, upgrade to a newer version. The issue is fixed as from 7.x-1.3 [5]. * If using an older version, be aware of the risks & consequences. *Note: *For some people, the previous behavior was actually exactly how they used this module. To restore the original functionality, go to the settings ( admin/config/content/webform_template ) and check the "Defeat node access" checkbox. Also see the Webform Template [6] project page. -------- REPORTED BY --------------------------------------------------------- * theunraveler [7] -------- FIXED BY ------------------------------------------------------------ * rv0 [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Rick Manelius [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 http://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] http://drupal.org/project/webform_template [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/webform_template [5] https://drupal.org//drupal.org/node/2216447 [6] http://drupal.org/project/webform_template [7] https://drupal.org/user/71548 [8] https://drupal.org/user/655596 [9] https://drupal.org/user/680072 [10] http://drupal.org/contact [11] http://drupal.org/security-team [12] http://drupal.org/writing-secure-code [13] http://drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-030 - SexyBookmarks - Information Disclosure
by security-news＠drupal.org 12 Mar '14

12 Mar '14

View online: https://drupal.org/node/2216269 * Advisory ID: DRUPAL-SA-CONTRIB-2014-030 * Project: SexyBookmarks [1] (third-party module) * Version: 6.x * Date: 2014-March-12 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Information Disclosure -------- DESCRIPTION --------------------------------------------------------- The SexyBookmarks module is a port of the WordPress SexyBookmarks plug-in. The module adds social bookmarking using the Shareaholic service. The module discloses the private files location when Drupal 6 is configured to use private files. This vulnerability is mitigated by the fact that only sites using private files 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 --------------------------------------------------- * All SexyBookmarks 6.x-2.x versions. Drupal core is not affected. If you do not use the contributed SexyBookmarks [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ * If you use the SexyBookmarks module for Drupal 6.x you should disable it. * Users can also consider using the Shareaholic [5] module which provides similar features. However, the Shareaholic module is currently only available for Drupal 7 so affected users would have to upgrade to Drupal 7 first. Also see the SexyBookmarks [6] project page. -------- REPORTED BY --------------------------------------------------------- * Don Morris [7] -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [8] of the Drupal Security Team * Cash Williams [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 http://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] http://drupal.org/project/sexybookmarks [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/sexybookmarks [5] http://drupal.org/project/shareaholic [6] http://drupal.org/project/sexybookmarks [7] http://drupal.org/user/79398 [8] http://drupal.org/user/36762 [9] http://drupal.org/user/421070 [10] http://drupal.org/contact [11] http://drupal.org/security-team [12] http://drupal.org/writing-secure-code [13] http://drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-027 - NewsFlash Theme - XSS
by security-news＠drupal.org 05 Mar '14

05 Mar '14

View online: https://drupal.org/node/2211381 * Advisory ID: DRUPAL-SA-CONTRIB-2014-027 * Project: NewsFlash [1] (third-party theme) * Version: 6.x, 7.x * Date: 2014-March-05 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Newsflash is a theme that features 7 color styles, 12 collapsible regions, suckerfish menus, fluid or fixed widths, built-in IE transparent PNG fix, and lots more. The theme does not sanitize the user provided theme setting for the font family CSS property, thereby exposing a cross-site scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer themes". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * NewsFlash 6.x-1.x versions prior to 6.x-1.7. * NewsFlash 7.x-1.x versions prior to 7.x-2.5. Drupal core is not affected. If you do not use the contributed NewsFlash [4] theme, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the theme NewsFlash for Drupal 7.x, upgrade to NewsFlash 7.x-2.5 [5] * If you use the theme NewsFlash for Drupal 6.x, upgrade to NewsFlash 6.x-1.7 [6] Also see the NewsFlash [7] project page. -------- REPORTED BY --------------------------------------------------------- * Dennis Walgaard [8] -------- FIXED BY ------------------------------------------------------------ * Alyx Vance [9] the theme maintainer -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [10] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at http://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] http://drupal.org/project/newsflash [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/newsflash [5] https://drupal.org/node/2210621 [6] https://drupal.org/node/2210619 [7] http://drupal.org/project/newsflash [8] https://drupal.org/user/883702 [9] https://drupal.org/user/1284976 [10] https://drupal.org/user/262198 [11] http://drupal.org/contact [12] http://drupal.org/security-team [13] http://drupal.org/writing-secure-code [14] http://drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Security-news