- Security-news - lists.drupal.org

SA-CONTRIB-2010-084 - OpenID - Authentication bypass
by security-news＠drupal.org 11 Aug '10

11 Aug '10

* Advisory ID: DRUPAL-SA-CONTRIB-2010-084 * Project: OpenID (third-party module) * Version: 5.x * Date: 2010-Aug-11 * Security risk: Critical * Exploitable from: Remote * Vulnerability: Authentication bypass -------- DESCRIPTION --------------------------------------------------------- The OpenID module provides users the ability to login to sites using an OpenID account. The OpenID module doesn't implement the all required verifications from the OpenID 2.0 protocol and is vulnerable to a number of attacks. Specifically: - OpenID should verify that a "openid.response_nonce" has not already been used for an assertion by the OpenID provider - OpenID should verify the value of openid.return_to as obtained from the OpenID provider - OpenID must verify that all fields that are required to be signed are signed These specification violations allow malicious sites to harvest positive assertions from OpenID providers and use them on sites using the OpenID module to obtain access to preexisting accounts bound to the harvested OpenIDs. Intercepted assertions from OpenID providers can also be replayed and used to obtain access to user accounts bound to the intercepted OpenIDs. -------- VERSIONS AFFECTED --------------------------------------------------- * OpenID module for Drupal 5.x versions prior to 5.x-1.4 This issue affects the OpenID module for Drupal 5.x only. A separate security announcement [1] and release is published for the OpenID core module in Drupal 6.x. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the OpenID module for Drupal 5.x upgrade to OpenID 5.x-1.4 [2] See also the OpenID project page [3]. -------- REPORTED BY --------------------------------------------------------- * Johnny Bufu [4] * Christian Schmidt [5] * Heine Deelstra [6] of the Drupal security team -------- FIXED BY ------------------------------------------------------------ * Christian Schmidt [7] * Heine Deelstra [8] of the Drupal security team * Damien Tournoud [9] of the Drupal security team -------- CONTACT ------------------------------------------------------------- The Drupal security team [10] can be reached at security at drupal.org or via the form at http://drupal.org/contact. [1] http://drupal.org/node/880476 [2] http://drupal.org/node/880496 [3] http://drupal.org/project/openid [4] http://drupal.org/user/226462 [5] http://drupal.org/user/216078 [6] http://drupal.org/user/17943 [7] http://drupal.org/user/216078 [8] http://drupal.org/user/17943 [9] http://drupal.org/user/22211 [10] http://drupal.org/security-team

1 0

SA-CORE-2010-002 - Drupal core - Multiple vulnerabilities
by security-news＠drupal.org 11 Aug '10

11 Aug '10

* Advisory ID: DRUPAL-SA-CORE-2010-002 * Project: Drupal core * Version: 5.x, 6.x * Date: 2010-August-11 * Security risk: Critical * Exploitable from: Remote * Vulnerability: Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- Multiple vulnerabilities and weaknesses were discovered in Drupal. .... OpenID authentication bypass The OpenID module provides users the ability to login to sites using an OpenID account. The OpenID module doesn't implement all the required verifications from the OpenID 2.0 protocol and is vulnerable to a number of attacks. Specifically: - OpenID should verify that a "openid.response_nonce" has not already been used for an assertion by the OpenID provider - OpenID should verify the value of openid.return_to as obtained from the OpenID provider - OpenID must verify that all fields that are required to be signed are signed These specification violations allow malicious sites to harvest positive assertions from OpenID providers and use them on sites using the OpenID module to obtain access to preexisting accounts bound to the harvested OpenIDs. Intercepted assertions from OpenID providers can also be replayed and used to obtain access to user accounts bound to the intercepted OpenIDs. This issue affects Drupal 6.x only. A separate security announcement and release [1] is published for the contributed OpenID module for Drupal 5.x. .... File download access bypass The upload module allows users to upload files and provides access checking for file downloads. The module looks up files for download in the database and serves them for download after access checking. However, it does not account for the fact that certain database configurations will not consider case differences in file names. If a malicious user uploads a file which only differs in letter case, access will be granted for the earlier upload regardless of actual file access to that. This issue affects Drupal 5.x and 6.x. .... Comment unpublishing bypass The comment module allows users to leave comments on content on the site. The module supports unpublishing comments by privileged users. Users with the "post comments without approval" permission however could craft a URL which allows them to republish previously unpublished comments. This issue affects Drupal 5.x and 6.x. .... Actions cross site scripting The actions feature combined with Drupal's trigger module allows users to configure certain actions to happen when users register, content is submitted, and so on; through a web based interface. Users with "administer actions permission" can enter action descriptions and messages which are not properly filtered on output. Users with content and taxonomy tag submission permissions can create nodes and taxonomy terms which are not properly sanitized for inclusion in action messages and inject arbitrary HTML and script code into Drupal pages. Such a cross-site scripting attack may lead to the malicious user gaining administrative access. Wikipedia has more information about cross-site scripting [2] (XSS). This issue affects Drupal 6.x only. -------- VERSIONS AFFECTED --------------------------------------------------- * Drupal 6.x before version 6.18 or 6.19. * Drupal 5.x before version 5.23. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you are running Drupal 6.x then upgrade to Drupal 6.18 [3] or Drupal 6.19 [4]. * If you are running Drupal 5.x then upgrade to Drupal 5.23 [5]. Drupal 5 will no longer be maintained when Drupal 7 is released [6]. Upgrading to Drupal 6 [7] is recommended. The security team starts a new practice of releasing both a pure security update without other bugfixes and a security update combined with other bug fixes and improvements. You can choose to either only include the security update for an immediate fix (which might require less quality assurance and testing) or more fixes and improvements alongside the security fixes by choosing between Drupal 6.18 and Drupal 6.19. Read the announcement [8] for more information. -------- REPORTED BY --------------------------------------------------------- The OpenID authentication bypass issues were reported by Johnny Bufu [9], Christian Schmidt [10] and Heine Deelstra [11] (*). The file download access bypass was reported by Dylan Tack [12] (*). The comment unpublish bypass issue was reported by Heine Deelstra [13] (*). The actions module cross site scripting was reported by Justin Klein Keane [14] and Heine Deelstra [15] (*). (*) Member of the Drupal security team. -------- FIXED BY ------------------------------------------------------------ The OpenID authentication issues were fixed by Christian Schmidt [16], Heine Deelstra [17] (*) and Damien Tournoud [18] (*). The file download access bypass was fixed by Dave Reid [19] (*) and Neil Drumm [20] (*). The comment unpublish bypass issue was fixed by Heine Deelstra [21] (*). The actions module cross site scripting was fixed by Justin Klein Keane [22] and Heine Deelstra [23] (*). (*) Member of the Drupal security team. -------- CONTACT ------------------------------------------------------------- The security team for Drupal can be reached at security at drupal.org or via the form at http://drupal.org/contact. [1] http://drupal.org/node/880480 [2] http://en.wikipedia.org/wiki/Cross-site_scripting [3] http://ftp.drupal.org/files/projects/drupal-6.18.tar.gz [4] http://ftp.drupal.org/files/projects/drupal-6.19.tar.gz [5] http://ftp.drupal.org/files/projects/drupal-5.23.tar.gz [6] http://drupal.org/node/725382 [7] http://drupal.org/upgrade [8] http://drupal.org/drupal-6.19 [9] http://drupal.org/user/226462 [10] http://drupal.org/user/216078 [11] http://drupal.org/user/17943 [12] http://drupal.org/user/96647 [13] http://drupal.org/user/17943 [14] http://drupal.org/user/302225 [15] http://drupal.org/user/17943 [16] http://drupal.org/user/216078 [17] http://drupal.org/user/17943 [18] http://drupal.org/user/22211 [19] http://drupal.org/user/53892 [20] http://drupal.org/user/3064 [21] http://drupal.org/user/17943 [22] http://drupal.org/user/302225 [23] http://drupal.org/user/17943

1 0

SA-CONTRIB-2010-083 - Ubercart sub-modules - Multiple Vulnerabilities
by security-news＠drupal.org 11 Aug '10

11 Aug '10

* Advisory ID: DRUPAL-SA-CONTRIB-2010-083 * Project: UC2Checkout, UCPaypal, UC Cart LInks (third-party modules in the Ubercart Project) * Version: 5.x, 6.x * Date: 2010-Aug-11 * Security risk: Critical * Exploitable from: Remote * Vulnerability: Access Bypass, Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- The Ubercart module for Drupal provides e-commerce features. Several modules within Ubercart were vulnerable to various security issues. 1) The 2Checkout gateway module did not properly verify the payment notification information. A malicious user could use a specially crafted HTTP request to simulate payment and order completion on arbitrary orders. If the 2Checkout gateway module is not installed then your site is not at risk to this vulnerability. 2) The Paypal module's WPS payment method did not properly verify the payment notification information. A malicious user could alter HTML form data to send payment to a different Paypal account and still check out on the site. If you do not use the Paypal WPS payment method then your site is not at risk to this vulnerability. 3) The Ubercart Cart Links module is vulnerable to both an Access Bypass and Cross Site Request Forgery where a malicious user could both trick other users into adding or removing items from their cart and add items to a cart which are not published on the site. If you do not use Ubercart Cart Links module your site is not at risk to this vulnerability. -------- VERSIONS AFFECTED --------------------------------------------------- * Ubercart module for Drupal 5.x versions prior to 5.x-1.10 * Ubercart module for Drupal 6.x versions prior to 6.x-2.4 Drupal core is not affected. If you do not use the contributed Ubercart [1] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Ubercart module for Drupal 5.x upgrade to Ubercart 5.x-1.10 [2] * If you use the Ubercart module for Drupal 6.x upgrade to Ubercart 6.x-2.4 [3] See also the Ubercart project page [4]. -------- REPORTED BY --------------------------------------------------------- * Greg Knaddison [5] of the Drupal Security Team * Guy Paddock [6] * Nathan Phillip Brink [7] -------- FIXED BY ------------------------------------------------------------ * Lyle Mantooth [8], the module maintainer * Greg Knaddison [9] of the Drupal Security Team -------- CONTACT ------------------------------------------------------------- The Drupal security team [10] can be reached at security at drupal.org or via the form at http://drupal.org/contact. [1] http://drupal.org/project/ubercart [2] http://drupal.org/node/880378 [3] http://drupal.org/node/880390 [4] http://drupal.org/project/ubercart [5] http://drupal.org/user/UID [6] http://drupal.org/user/156932 [7] http://drupal.org/user/829476 [8] http://drupal.org/user/86683 [9] http://drupal.org/user/UID [10] http://drupal.org/security-team

1 0

SA-CONTRIB-2010-082 - Print - Local file read access
by security-news＠drupal.org 11 Aug '10

11 Aug '10

* Advisory ID: DRUPAL-SA-CONTRIB-2010-082 * Project: Printer, e-mail and PDF versions (third-party module) * Version: 5.x, 6.x * Date: 2010-August-11 * Security risk: Critical * Exploitable from: Remote * Vulnerability: Local file read access -------- DESCRIPTION --------------------------------------------------------- The Printer, e-mail and PDF versions ("print") module provides printer-friendly versions of content, including a PDF version that is generated by one of three supported generation tools (dompdf, TCPDF and wkhtmltopdf). When using the wkhtmltopdf PDF generation tool, that tool is able to access local files in the Drupal server environment. Users with the ability to create unfiltered HTML in the node content could trick the tool to access any file accessible by the Web server user and to display its contents inside the generated PDF. Sites should not grant the ability to post unfiltered HTML to untrusted roles. -------- VERSIONS AFFECTED --------------------------------------------------- * Printer, e-mail and PDF versions 6.x prior to 6.x-1.11 * Printer, e-mail and PDF versions 5.x prior to 5.x-4.10 Drupal core is not affected. If you do not use the contributed Printer, e-mail and PDF versions module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use Printer, e-mail and PDF versions for Drupal 6.x upgrade to Printer, e-mail and PDF versions 6.x-1.11 [1] * If you use Printer, e-mail and PDF versions for Drupal 5.x upgrade to Printer, e-mail and PDF versions 5.x-4.10 [2] If you use the wkhtmltopdf PDF generation tool, and it's version is older than 0.9.6, please upgrade [3] to a more recent version, as the module now supports only versions 0.9.6 or higher. See also the Printer, e-mail and PDF versions project page [4]. -------- REPORTED BY --------------------------------------------------------- * Douglas Bagnall [5] -------- FIXED BY ------------------------------------------------------------ * João Ventura [6], module maintainer * James Gilliland [7], module maintainer -------- CONTACT ------------------------------------------------------------- The Drupal security team [8] can be reached at security at drupal.org or via the form at http://drupal.org/contact. [1] http://drupal.org/node/880280 [2] http://drupal.org/node/880276 [3] http://code.google.com/p/wkhtmltopdf [4] http://drupal.org/project/print [5] http://drupal.org/user/758786 [6] http://drupal.org/user/122464 [7] http://drupal.org/user/48673 [8] http://drupal.org/security-team

1 0

SA-CONTRIB-2010-081 - FileField Sources - Arbitrary Code Execution
by security-news＠drupal.org 11 Aug '10

11 Aug '10

* Advisory ID: DRUPAL-SA-CONTRIB-2010-081 * Project: FileField Sources (third-party module) * Version: 6.x * Date: 2010-May-19 * Security risk: Critical * Exploitable from: Remote * Vulnerability: Arbitrary Code Execution -------- DESCRIPTION --------------------------------------------------------- The FileField Sources module expands on the abilities of FileField, allowing users to select new or existing files through additional means, including: Reuse of existing files through an autocomplete textfield or IMCE, or transfering files directly from remote servers. The module does not sanitize the file extemsions of files that have been transfered from remote servers, allowing for the transfering of files that match allowed extensions but actually contain malicious code. This could potentially allow an attacker to transfer scripts to the server and execute them. This vulerability is usually mitigated by Drupal core's built-in security mechanisms which prevent code execution of uploads that are within the Drupal files directory. This exploit should not affect the majority of Drupal sites. Users would also need the ability to use the FileField Sources module which requires permission to create or edit a node that has a FileField with FileField Sources configured for it. -------- VERSIONS AFFECTED --------------------------------------------------- * FileField Sources module for Drupal 6.x versions prior to 6.x-1.2 Drupal core is not affected. If you do not use the contributed FileField Sources [1] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the FileField Sources module for Drupal 6.x upgrade to FileField Sources 6.x-1.2 [2] See also the FileField Sources project page [3]. -------- REPORTED BY --------------------------------------------------------- * Apa Sajja -------- FIXED BY ------------------------------------------------------------ * Nathan Haug [4], module maintainer * Greg Knaddison [5] of the Drupal security team -------- CONTACT ------------------------------------------------------------- The Drupal security team [6] can be reached at security at drupal.org or via the form at http://drupal.org/contact. [1] http://drupal.org/project/filefield_sources [2] http://drupal.org/node/880248 [3] http://drupal.org/project/filefield_sources [4] http://drupal.org/user/35821 [5] http://drupal.org/user/36762 [6] http://drupal.org/security-team

1 0

SA-CONTRIB-2010-080 - Privatemsg - Cross Site Scripting
by security-news＠drupal.org 11 Aug '10

11 Aug '10

* Advisory ID: DRUPAL-SA-CONTRIB-2010-080 * Project: Privatemsg (third-party module) * Version: 6.x * Date: 2010-August-11 * Security risk: Moderately critical * Exploitable from: Remote * Vulnerability: Cross-Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Privatemsg module allows to send private messages between users. The module does not properly escape user-supplied data before displaying it, leading to a Cross Site Scripting (XSS [1]) vulnerability. Any user with permission to write private messages is vulnerable to attack. -------- VERSIONS AFFECTED --------------------------------------------------- * Privatemsg module for Drupal 6.x versions prior to 6.x-1.3 Drupal core is not affected. If you do not use the contributed Privatemsg [2] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Privatemsg module for Drupal 6.x upgrade to Privatemsg 6.x-1.3 [3] See also the Privatemsg project page [4]. -------- REPORTED BY --------------------------------------------------------- * Ben Durbin (bdurbin) [5] -------- FIXED BY ------------------------------------------------------------ * Ben Durbin (bdurbin) [6] * Sascha Grossenbacher (Berdir) [7], module maintainer -------- CONTACT ------------------------------------------------------------- The Drupal security team [8] can be reached at security at drupal.org or via the form at http://drupal.org/contact. [1] http://en.wikipedia.org/wiki/Cross-site_scripting [2] http://drupal.org/project/privatemsg [3] http://drupal.org/node/880036 [4] http://drupal.org/project/privatemsg [5] http://drupal.org/user/165644 [6] http://drupal.org/user/165644 [7] http://drupal.org/user/214652 [8] http://drupal.org/security-team

1 0

SA-CONTRIB-2010-079 - Devel (Performance logging) - Cross Site Scripting
by security-news＠drupal.org 05 Aug '10

05 Aug '10

* Advisory ID: SA-CONTRIB-2010-079 * Project: Devel (third-party module) * Version: 5.x, 6.x * Date: 2010-Aug-04 * Security risk: Moderately critical * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION: -------------------------------------------------------- The devel project is a suite of modules for developers and themers. Within the devel project, there is the performance logging module. The module does not escape URLs comprised of node paths, leading to a Cross Site Scripting (XSS) vulnerability. Users with the permission to access the reports that the performance module produces are vulnerable to attack. A malicious user needs the ability to add url aliases to create and exploit the vulnerability. -------- VERSIONS AFFECTED: -------------------------------------------------- * Devel module for Drupal 5.x versions prior to 5.x-1.3 * Devel module for Drupal 6.x versions prior to 6.x-1.21 Drupal core is not affected. If you do not use the contributed performance logging module, there is nothing you need to do. -------- SOLUTION: ----------------------------------------------------------- Install the latest version: * For Drupal 5.x, upgrade to Devel 5.x-1.3 [1] * For Drupal 6.x, upgrade to Devel 6.x-1.21 [2] See also the Devel [3] project page. -------- REPORTED BY: -------------------------------------------------------- * Justin James Grevich -------- FIXED BY: ----------------------------------------------------------- * Khalid Baheyeldin (kbahey [4]), the performance logging module maintainer The Drupal security team can be reached at security at drupal.org or via the form at http://drupal.org/contact. [1] http://drupal.org/node/874130 [2] http://drupal.org/node/874116 [3] http://drupal.org/project/devel [4] http://drupal.org/user/4063

1 0

SA-CONTRIB-2010-078 - Kaltura - Information disclosure
by security-news＠drupal.org 29 Jul '10

29 Jul '10

* Advisory ID: DRUPAL-SA-CONTRIB-2010-078 * Project: Kaltura (third-party module) * Versions: 5.x, 6.x * Date: 2010-July-28 * Security risk: Less Critical * Exploitable from: Remote * Vulnerability: Information disclosure -------- DESCRIPTION --------------------------------------------------------- The Kaltura module integrates the Kaltura open source video platform with Drupal. When installing, uninstalling, or configuring the module, it would surreptitiously inject a hidden iframe into the messages displayed to the administrator with the source pointing to corp.kaltura.com/stats/drupal. These requests were made without prior knowledge or authorization of site administrators. The iframe also included information such as the site's Kaltura partner ID, registration ID, or registration error code. Because most browsers also include the referring site when dispalying an iframe, information such as the URL or IP address of the Drupal site could also have been obtained. -------- RESPONSIBLE COLLECTION OF USAGE STATISTICS FOR DRUPAL MODULES ------- The popularity of modules hosted on drupal.org is already tracked based on data in the request when a Drupal installation checks to see if any of its modules have new releases (see the Kaltura usage page [1] for example). This information is gathered with privacy in mind: an open discussion [2] occurred before including private information in the requests; the data is not shared outside of Drupal.org server administrators (approximately 10 people); site administrators are alerted to this system during installation of their site and they can opt in or out at any time. -------- VERSIONS AFFECTED --------------------------------------------------- * Kaltura module for Drupal 6.x prior to 6.x-1.5, and all 6.x-2.x versions * Kaltura module for Drupal 5.x prior to 5.x-1.4 Drupal core is not affected. If you do not use the Kaltura module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use Kaltura module for Drupal 5.x upgrade to Kaltura 5.x-1.4 [3] * If you use Kaltura module for Drupal 6.x upgrade to Kaltura 6.x-1.5 [4] * If you use Kaltura module for Drupal version 6.x-2.0 or 6.x-2.x-dev, downgrade to Kaltura 6.x-1.5 [5] Also see the Kaltura project page [6]. -------- REPORTED BY --------------------------------------------------------- * Denis Slepichev [7] * Chris Burgess [8] -------- FIXED BY ------------------------------------------------------------ * Chris Burgess [9], the new module maintainer -------- CONTACT ------------------------------------------------------------- The Drupal security team [10] can be reached at security at drupal.org or via the form at http://drupal.org/contact. [1] http://drupal.org/project/usage/kaltura [2] http://lists.drupal.org/pipermail/development/2007-December/027921.html [3] http://drupal.org/node/867754 [4] http://drupal.org/node/848996 [5] http://drupal.org/node/848996 [6] http://drupal.org/project/kaltura [7] http://drupal.org/user/399704 [8] http://drupal.org/user/76026 [9] http://drupal.org/user/76026 [10] http://drupal.org/security-team

1 0

SA-CONTRIB-2010-077 - Sage Pay (former Protx) Direct Payment Gateway for Ubercart - Information Disclosure
by security-news＠drupal.org 28 Jul '10

28 Jul '10

* Advisory ID: DRUPAL-SA-CONTRIB-2010-077 * Project: Sage Pay Direct Payment Gateway for Ubercart (third-party module) * Version: 5.x, 6.x * Date: 2010-July-28 * Security risk: Less Critical * Exploitable from: Remote * Vulnerability: Information Disclosure -------- DESCRIPTION --------------------------------------------------------- The Sage Pay Direct Payment Gateway for Ubercart (uc_protx_vsp_direct) processes credit card transactions in Ubercart stores using the Sage Pay Direct service. The module may show remote 3-D Secure pages to the user in an iframe when their bank supports the Verified by Visa or MasterCard SecureCode verification schemes. These pages can include sensitive information relating to the user's credit card. In some configurations, the page containing the iframe may be stored in the Drupal cache and incorrectly shown to a subsequent anonymous user. -------- VERSIONS AFFECTED --------------------------------------------------- * Sage Pay Direct Payment Gateway for Ubercart module for Drupal 5.x versions prior to 5.x-1.9 * Sage Pay Direct Payment Gateway for Ubercart for Drupal 6.x versions prior to 6.x-1.4 Drupal core is not affected. If you do not use the contributed Sage Pay Direct Payment Gateway for Ubercart there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Sage Pay Direct Payment Gateway for Ubercart module for Drupal 5.x upgrade to the 5.x-1.9 version [1] * If you use the Sage Pay Direct Payment Gateway for Ubercart module for Drupal 6.x upgrade to the 6.x-1.4 version [2] See also the Sage Pay Direct Payment Gateway for Ubercart project page [3]. -------- REPORTED BY --------------------------------------------------------- * David Long (longwave) [4], module co-maintainer -------- FIXED BY ------------------------------------------------------------ * David Long (longwave) [5], module co-maintainer -------- CONTACT ------------------------------------------------------------- The Drupal security team [6] can be reached at security at drupal.org or via the form at http://drupal.org/contact. [1] http://drupal.org/node/867454 [2] http://drupal.org/node/867456 [3] http://drupal.org/project/uc_protx_vsp_direct [4] http://drupal.org/user/246492 [5] http://drupal.org/user/246492 [6] http://drupal.org/security-team

1 0

SA-CONTRIB-2010-076 - Dashboard - Cross Site Scripting (CSS)
by security-news＠drupal.org 28 Jul '10

28 Jul '10

* Advisory ID: SA-CONTRIB-2010-076 * Project: Dashboard (third-party module) * Version: 6.x * Date: 2010-July-28 * Security risk: Moderately critical * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION: -------------------------------------------------------- The dashboard module allows users to create a personalized set of pages of widgets created from existing blocks and nodes (like iGoogle). The module does not escape user generated names for tags & titles associated with default widgets that are added to a user dashboard page, leading to a Cross Site Scripting (XSS [1]) vulnerability. Users with the permission to access or create default dashboard widgets is vulnerable to attack. A malicious user needs the permission "administer dashboard defaults" to exploit the vulnerability. -------- VERSIONS AFFECTED: -------------------------------------------------- * Dashboard module for Drupal 6.x versions prior to 6.x-2.1 [2] Drupal core is not affected. If you do not use the contributed Dashboard [3] module, there is nothing you need to do. -------- SOLUTION: ----------------------------------------------------------- Install the latest version: * Upgrade to Dashboard 6.x-2.1 [4] See also the Dashboard project page [5]. -------- REPORTED BY: -------------------------------------------------------- * Greg Knaddison (greggles) [6] a member of the Drupal Security Team -------- FIXED BY: ----------------------------------------------------------- * Chris Miller [7], module maintainer * Greg Knaddison (greggles) [8] a member of the Drupal Security Team The Drupal security team [9] can be reached at security at drupal.org [10] or via the form at http://drupal.org/contact [11]. [1] http://en.wikipedia.org/wiki/Cross-site_scripting [2] http://drupal.org/node/866628 [3] http://drupal.org/project/dashboard [4] http://drupal.org/node/866628 [5] http://drupal.org/project/dashboard [6] http://drupal.org/user/36762 [7] http://drupal.org/user/274027 [8] http://drupal.org/user/36762 [9] http://drupal.org/security-team [10] http://drupal.org [11] http://drupal.org/contact

1 0