June 2012 - Security-news - lists.drupal.org

SA-CONTRIB-2012-105 - Hashcash - Cross Site Scripting (XSS)
by security-news＠drupal.org 27 Jun '12

27 Jun '12

View online: http://drupal.org/node/1663306 * Advisory ID: DRUPAL-SA-CONTRIB-2012-105 * Project: Hashcash [1] (third-party module) * Version: 6.x, 7.x * Date: 2012-June-27 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Hashcash project is an implementation of a Proof Of Work (POW) or Puzzle scheme where users of a service have to do computational work to have their request granted. In the case of the Drupal Hashcash project, the service is 'form submission' and the Proof Of Work is a token that causes a partial hash collision when concatenated with a given string. This is intended to stop spam submissions to a site. .... Cross Site Scripting When an invalid token is received and the setting "Log failed hashcash" is enabled, the invalid token is written to watchdog with incorrect placeholders. This enables an attacker to insert arbitrary scripts into certain pages displayed to administrators via the core module Database logging. Mitigation: The setting "Log failed hashcash" is disabled by default. .... Insufficient proof of work The Hashcash project also fails as a proper proof of work scheme: * 1 in 256 random answers will be accepted as the correct answer. * The discrepancy in resources between a legitimate user using the Javascript hash implementation and an optimal attacker using a GPGPU implementation makes the cost of calculating a Hashcash token negligible for the attacker. The protection against spambots offered by the Drupal Hashcash project hinges on the lack of interest on behalf of an attacker. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Hashcash 6.x-2.x versions prior to 6.x-2.6 * Hashcash 7.x-2.x versions prior to 7.x-2.2 Drupal core is not affected. If you do not use the contributed Hashcash [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ To solve the cross site scripting issue, install the latest version: * If you use the Hashcash module for Drupal 6.x, upgrade to Hashcash 6.x-2.6 [4] * If you use the Hashcash module for Drupal 7.x, upgrade to Hashcash 7.x-2.2 [5] There is no solution for the insufficient proof of work. You need to consider the consequences of this for your sites. Also see the Hashcash [6] project page. -------- REPORTED BY --------------------------------------------------------- * Heine Deelstra [7] -------- FIXED BY ------------------------------------------------------------ * Simon Rycroft [8], the module maintainer -------- 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 [9]. Learn more about the Drupal Security team and their policies [10], writing secure code for Drupal [11], and securing your site [12]. [1] http://drupal.org/project/hashcash [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/hashcash [4] http://drupal.org/node/1650784 [5] http://drupal.org/node/1650790 [6] http://drupal.org/project/hashcash [7] http://drupal.org/user/17943 [8] http://drupal.org/user/151544 [9] http://drupal.org/contact [10] http://drupal.org/security-team [11] http://drupal.org/writing-secure-code [12] http://drupal.org/security/secure-configuration

1 0

SA-CONTRIB-2012-104 - Privatemsg - Cross Site Scripting (XSS)
by security-news＠drupal.org 20 Jun '12

20 Jun '12

View online: http://drupal.org/node/1649346 * Advisory ID: DRUPAL-SA-CONTRIB-2012-104 * Project: Privatemsg [1] (third-party module) * Version: 7.x * Date: 2012-June-20 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Privatemsg module allows users to send private messages between to each other. The module doesn't sufficiently sanitize user names when creating messages. This vulnerability is mitigated by the fact that it is not possible to create insecure user names through the default user interface. The exploit is only possible in combination with another module that allows this, such as Realname [3] which allows site-builders to choose fields to display an alternative username. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Privatemsg 7.x-1.x versions prior to 7.x-1.3 Drupal core is not affected. If you do not use the contributed Privatemsg [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Privatemsg module for Drupal 7, upgrade to Privatemsg 7.x-1.3 [5] Also see the Privatemsg [6] project page. -------- REPORTED BY --------------------------------------------------------- * Dave Reid [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Sascha Grossenbacher [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Dave Reid [9] of the Drupal Security Team * Greg Knaddison [10] of the Drupal Security Team * Michael Hess [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 http://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]. [1] http://drupal.org/project/privatemsg [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/realname [4] http://drupal.org/project/privatemsg [5] http://drupal.org/node/1649338 [6] http://drupal.org/project/privatemsg [7] http://drupal.org/user/53892 [8] http://drupal.org/user/214652 [9] http://drupal.org/user/53892 [10] http://drupal.org/user/36762 [11] http://drupal.org/user/102818 [12] http://drupal.org/contact [13] http://drupal.org/security-team [14] http://drupal.org/writing-secure-code [15] http://drupal.org/security/secure-configuration

1 0

SA-CONTRIB-2012-103 - Global Redirect - Open Redirect
by security-news＠drupal.org 13 Jun '12

13 Jun '12

View online: http://drupal.org/node/1633054 * Advisory ID: DRUPAL-SA-CONTRIB-2012-103 * Project: Global Redirect [1] (third-party module) * Version: 6.x, 7.x * Date: 2012-June-13 * Security risk: Less critical [2] * Exploitable from: Remote * Vulnerability: Open Redirect -------- DESCRIPTION --------------------------------------------------------- This module improves SEO and usability of a site by redirecting visitors to user-friendly and search-engine-friendly URLs. The module does not sufficiently validate that a destination URL is internal to the site, allowing an attacker to disguise a malicious destination address as a query parameter passed to a legitimate site URL. This vulnerability is mitigated by the fact that a site must have the "non-clean to clean" redirect enabled; however, this is the default configuration. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Global Redirect 6.x-1.x versions prior to 6.x-1.4. * Global Redirect 7.x-1.x versions prior to 7.x-1.4. Drupal core is not affected. If you do not use the contributed Global Redirect [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Global Redirect module for Drupal 6.x, upgrade to Global Redirect 6.x-1.4 [4] * If you use the Global Redirect module for Drupal 7.x, upgrade to Global Redirect 7.x-1.4 [5] Also see the Global Redirect [6] project page. -------- REPORTED BY --------------------------------------------------------- * Ben Johnson [7] (benpjohnson) * Justin Klein-Keane [8] (Justin_KleinKeane) * Joe Chambers [9] (myrapunzeled) -------- FIXED BY ------------------------------------------------------------ * Nicholas Thompson [10] the module maintainer * Dave Reid [11] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [12] of the Drupal Security Team * Dave Reid [13] of the Drupal Security Team * Michael Hess [14] of the Drupal Security Team * Dylan Tack [15] of the Drupal Security Team * David Rothstein [16] 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 [17]. Learn more about the Drupal Security team and their policies [18], writing secure code for Drupal [19], and securing your site [20]. [1] http://drupal.org/project/globalredirect [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/globalredirect [4] https://drupal.org/node/1378116 [5] https://drupal.org/node/1378118 [6] http://drupal.org/project/globalredirect [7] http://drupal.org/user/268889 [8] http://drupal.org/user/302225 [9] http://drupal.org/user/1228542 [10] http://drupal.org/user/59351 [11] http://drupal.org/user/53892 [12] http://drupal.org/user/36762 [13] http://drupal.org/user/53892 [14] http://drupal.org/user/102818 [15] http://drupal.org/user/96647 [16] http://drupal.org/user/124982 [17] http://drupal.org/contact [18] http://drupal.org/security-team [19] http://drupal.org/writing-secure-code [20] http://drupal.org/security/secure-configuration

1 0

SA-CONTRIB-2012-102 - Ubercart AJAX Cart - Potential Disclosure of user Session ID
by security-news＠drupal.org 13 Jun '12

13 Jun '12

View online: http://drupal.org/node/1633048 * Advisory ID: DRUPAL-SA-CONTRIB-2012-102 * Project: Ubercart AJAX Cart [1] (third-party module) * Version: 6.x * Date: 2012-June-13 * Security risk: Less critical [2] * Exploitable from: Remote * Vulnerability: Information Disclosure -------- DESCRIPTION --------------------------------------------------------- This module enables you to replace the default Ubercart shopping cart block with an AJAX-enabled one. The module includes the user's current session ID in one of its JavaScript settings keys on every page load which could be intercepted if the user's connection is not over SSL. This vulnerability is mitigated by the fact that an attacker must gain read access to the HTML output of a page with the uc_ajax_cart block enabled in order to potentially hijack the user's session. The issue is only known to affect sites that use some additional form of caching for authenticated users that shares Javascript settings values which is not a common case. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * uc_ajax_cart 6.x-2.x versions prior to 6.x-2.1. Drupal core is not affected. If you do not use the contributed Ubercart AJAX Cart [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the uc_ajax_cart module for Drupal 6.x, upgrade to uc_ajax_cart 6.x-2.1 [4] Also see the Ubercart AJAX Cart [5] project page. -------- REPORTED BY --------------------------------------------------------- * Neil Bertram [6] -------- FIXED BY ------------------------------------------------------------ * Stewart Adam [7], the module maintainer * Gerhard Killesreiter [8] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [9] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at 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]. [1] http://drupal.org/project/uc_ajax_cart [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/uc_ajax_cart [4] http://drupal.org/node/1619586 [5] http://drupal.org/project/uc_ajax_cart [6] http://drupal.org/user/154713 [7] http://drupal.org/user/586244 [8] http://drupal.org/user/83 [9] http://drupal.org/user/36762 [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

1 0

SA-CONTRIB-2012-101 - Protected Node - Access Bypass
by security-news＠drupal.org 13 Jun '12

13 Jun '12

View online: http://drupal.org/node/1632918 * Advisory ID: DRUPAL-SA-CONTRIB-2012-101 * Project: Protected node [1] (third-party module) * Version: 6.x * Date: 2012-June-13 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The Protected Node module enables users to use a password to restrict access to an individual node or all nodes of a node type. The module doesn't sufficiently protect node access when nodes are accessed outside of the standard node view (i.e. node/1 is protected but other lists are not). CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Protected node 6.x-1.x versions prior to 6.x-1.6. Drupal core is not affected. If you do not use the contributed Protected node [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Protected node module for Drupal 6.x, upgrade to Protected node 6.x-1.6 [4] Also see the Protected node [5] project page. -------- REPORTED BY --------------------------------------------------------- * Martin Barbella [6] -------- FIXED BY ------------------------------------------------------------ * Alexis Wilke [7] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [8] of the Drupal Security Team * Michael Hess [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]. [1] http://drupal.org/project/protected_node [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/protected_node [4] http://drupal.org/node/1258034 [5] http://drupal.org/project/protected_node [6] http://drupal.org/user/633600 [7] http://drupal.org/user/356197 [8] http://drupal.org/user/36762 [9] http://drupal.org/user/102818 [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

1 0

SA-CONTRIB-2012-100 - SimpleMeta - Cross Site Request Forgery (CSRF)
by security-news＠drupal.org 13 Jun '12

13 Jun '12

View online: http://drupal.org/node/1632908 * Advisory ID: DRUPAL-SA-CONTRIB-2012-100 * Project: SimpleMeta [1] (third-party module) * Version: 6.x * Date: 2012-June-13 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- The Simple Meta module provides a method to set meta tags, such as page title, description and keywords for nodes, views and other pages. The module doesn't sufficiently confirm user intent when adding and deleting meta tag entries allowing a malicious user to trick a site admin into deleting entries or adding inappropriate entries. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Simple meta 6.x-1.x all versions prior to 6.x-2.0. Drupal core is not affected. If you do not use the contributed SimpleMeta [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Simple meta module for Drupal 6.x, upgrade to Simple meta 6.x-2.0 [4] The 6.x-1.x branch is no longer supported and all users of that branch should upgrade to the 6.x-2.x code. Also see the SimpleMeta [5] project page. -------- REPORTED BY --------------------------------------------------------- * Nicholas Thompson [6] -------- FIXED BY ------------------------------------------------------------ * Alexander [7] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [8] of the Drupal Security Team * Michael Hess [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]. [1] http://drupal.org/project/simplemeta [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/simplemeta [4] http://drupal.org/node/1534874 [5] http://drupal.org/project/simplemeta [6] http://drupal.org/user/59351 [7] http://drupal.org/user/366450 [8] http://drupal.org/user/36762 [9] http://drupal.org/user/102818 [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

1 0

SA-CONTRIB-2012-099 - Node Hierarchy - Cross Site Request Forgery (CSRF)
by security-news＠drupal.org 13 Jun '12

13 Jun '12

View online: http://drupal.org/node/1632900 * Advisory ID: DRUPAL-SA-CONTRIB-2012-099 * Project: Node Hierarchy [1] (third-party module) * Version: 6.x * Date: 2012-June-13 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- Node Hierarchy module allows for the creation of parent child relationships among nodes that can create a tree-like hierarchy of content. The module doesn't sufficiently confirm user intent when reordering children nodes allowing a malicious user to trick a site admin to changing the desired hierarchy. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Node Hierarchy 6.x-1.x versions prior to 6.x-1.5. Drupal core is not affected. If you do not use the contributed Node Hierarchy [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Node Hierarchy module for Drupal 6.x, upgrade to Node Hierarchy 6.x-1.5 [4] Also see the Node Hierarchy [5] project page. -------- REPORTED BY --------------------------------------------------------- * Dylan Tack [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Ronan Dowling [7] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [8] 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 [9]. Learn more about the Drupal Security team and their policies [10], writing secure code for Drupal [11], and securing your site [12]. [1] http://drupal.org/project/nodehierarchy [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/nodehierarchy [4] http://drupal.org/node/1632432 [5] http://drupal.org/project/nodehierarchy [6] http://drupal.org/user/96647 [7] http://drupal.org/user/72815 [8] http://drupal.org/user/36762 [9] http://drupal.org/contact [10] http://drupal.org/security-team [11] http://drupal.org/writing-secure-code [12] http://drupal.org/security/secure-configuration

1 0

SA-CONTRIB-2012-098 - Janrain Capture - Open Redirect
by security-news＠drupal.org 13 Jun '12

13 Jun '12

View online: http://drupal.org/node/1632734 * Advisory ID: DRUPAL-SA-CONTRIB-2012-098 * Project: Janrain Capture [1] (third-party module) * Version: 6.x, 7.x * Date: 2012-June-13 * Security risk: Less critical [2] * Exploitable from: Remote * Vulnerability: Open Redirect -------- DESCRIPTION --------------------------------------------------------- This module allows for authentication through the cloud user-management platform Janrain Capture. Part of the module exposes an endpoint to re-synchronize user data between Drupal and Capture and allows for passing an optional parameter to redirect the user back to an original location. This parameter was not checked to verify that it's an internal path, possibly leading to an open redirect vulnerability if the user was tricked into accessing the authentication workflow via a specially crafted URL. An additional security weakness occurs when the module creates a new local user account. The input to the generated password should be unguessable, but could be partially discovered. For sites that allow both local and Capture logins, this could lead to easy brute-force guessing of the local password. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Janrain Capture 6.x-1.0 * Janrain Capture 7.x-1.0 Drupal core is not affected. If you do not use the contributed Janrain Capture [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Janrain Capture module for Drupal 6.x, upgrade to Janrain Capture 6.x-1.1 [4] or later * If you use the Janrain Capture module for Drupal 7.x, upgrade to Janrain Capture 7.x-1.1 [5] or later If you are using this module and allow local logins, you may wish to regenerate the "random" local user passwords. Also see the Janrain Capture [6] project page. -------- REPORTED BY --------------------------------------------------------- * Peter Wolanin [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Bryce Hamrick [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Peter Wolanin [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]. [1] http://drupal.org/project/janrain_capture [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/janrain_capture [4] http://drupal.org/node/1632704 [5] http://drupal.org/node/1632702 [6] http://drupal.org/project/janrain_capture [7] http://drupal.org/user/49851 [8] http://drupal.org/user/1350078 [9] http://drupal.org/user/49851 [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

1 0

SA-CONTRIB-2012-097 - Protest - Cross Site Scripting (XSS)
by security-news＠drupal.org 06 Jun '12

06 Jun '12

View online: http://drupal.org/node/1619856 * Advisory ID: DRUPAL-SA-CONTRIB-2012-097 * Project: Protest [1] (third-party module) * Version: 6.x, 7.x * Date: 2012-June-06 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Protest allows websites to display a complete page blackout (website protest). The module contains a cross site scripting (XSS) vulnerability as it fails to sanitize user input before display. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer protest". CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Protest 6.x-1.x versions prior to 6.x-1.2. * Protest 7.x-1.x versions prior to 7.x-1.2. Drupal core is not affected. If you do not use the contributed Protest [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Protest module for Drupal 6.x, upgrade to Protest 6.x-1.2 [4] * If you use the Protest module for Drupal 7.x, upgrade to Protest 7.x-1.2 [5] Also see the Protest [6] project page. -------- REPORTED BY --------------------------------------------------------- * Shawn Price [7] -------- FIXED BY ------------------------------------------------------------ * Shawn Price [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [9] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at 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]. [1] http://drupal.org/project/protest [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/protest [4] http://drupal.org/node/1618090 [5] http://drupal.org/node/1618092 [6] http://drupal.org/project/protest [7] http://drupal.org/user/25556 [8] http://drupal.org/user/25556 [9] http://drupal.org/user/36762 [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

1 0

SA-CONTRIB-2012-096 - Authoring HTML - Cross Site Scripting (XSS)
by security-news＠drupal.org 06 Jun '12

06 Jun '12

View online: http://drupal.org/node/1619852 * Advisory ID: DRUPAL-SA-CONTRIB-2012-096 * Project: Authoring HTML [1] (third-party module) * Version: 6.x * Date: 2012-June-06 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module creates an input format suitable for use within a WYSIWYG editor. It adds support for the iframe HTML tag, making it friendly with the popular iframe embeds available in popular video sites like YouTube and Vimeo. It supports the script tag too. Both tags will only be allowed if the referred URL is whitelisted. By default, you can refer some well known video sites in the iframe tag and any site with the tag. The module doesn't sufficiently verify the whitelisted hosts. This allows an attacker to register and use a malicious host, bypassing verification. This vulnerability is mitigated by the fact that an attacker must have a role authorized to use the "Authoring HTML" input format. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Authoring HTML 6.x-1.x versions prior to 6.x-1.1. Drupal core is not affected. If you do not use the contributed Authoring HTML [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Authoring HTML module for Drupal 6.x, upgrade to Authoring HTML 6.x-1.1 [4] Also see the Authoring HTML [5] project page. -------- REPORTED BY --------------------------------------------------------- * Eriksen Costa [6] the module maintainer -------- FIXED BY ------------------------------------------------------------ * Eriksen Costa [7] the module maintainer * Matt Chapman [8] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Matt Chapman [9] of the Drupal Security Team * 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]. [1] http://drupal.org/project/authoring_html [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/authoring_html [4] http://drupal.org/node/1619086 [5] http://drupal.org/project/authoring_html [6] http://drupal.org/user/215266 [7] http://drupal.org/user/215266 [8] http://drupal.org/user/143172 [9] http://drupal.org/user/143172 [10] http://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

1 0