- Security-news - lists.drupal.org

SA-CONTRIB-2009-063 - XML sitemap - Cross Site Scripting
by security-news＠drupal.org 30 Sep '09

30 Sep '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-063 * Project: XML sitemap (third-party module) * Version: 5.x * Date: 2009-September-30 * Security risk: Less critical * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The XML sitemap module creates a sitemap that conforms to the sitemaps.org specification. It also allows users with the 'administer site configuration' permission to add additional custom links to be included in the sitemap. In the additional links interface, the module does not properly sanitize the output of the link paths before display, leading to a cross-site scripting (XSS [1]) vulnerability. Such an attack may lead to a malicious user gaining full administrative access. -------- VERSIONS AFFECTED --------------------------------------------------- * XML sitemap versions 5.x prior to 5.x-1.7 Drupal core is not affected. If you do not use the contributed XML sitemap module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the XML sitemap for Drupal 5.x upgrade to XML sitemap 5.x-1.7 [2] See also the XML sitemap module project page [3]. -------- IMPORTANT NOTES ----------------------------------------------------- This vulnerability was publicly disclosed. If you find a security vulnerability, please contact the Security team rather than posting a public issue. If you are a module maintainer, do not commit any security-related code fixes unless you have coordinated with the Security team. -------- REPORTED BY --------------------------------------------------------- This vulnerability was publicly disclosed. -------- FIXED BY ------------------------------------------------------------ Dave Reid [4] of the Drupal Security Team and module co-maintainer. -------- 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://en.wikipedia.org/wiki/Cross-site_scripting [2] http://drupal.org/node/591732 [3] http://drupal.org/project/xmlsitemap [4] http://drupal.org/user/53892

1 0

SA-CONTRIB-2009-062 - Devel - Cross Site Scripting
by security-news＠drupal.org 23 Sep '09

23 Sep '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-062 * Project: Devel (third-party module) * Version: 5.x, 6.x * Date: 2009-September-23 * Security risk: Less critical * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Devel module contains many useful developer functions, such as a query log and the display of variables. When using the variable editor, the module does not properly sanitize the output of the variable name before display, leading to a cross-site scripting (XSS [1]) vulnerability. Such an attack may lead to a malicious user gaining full administrative access. -------- VERSIONS AFFECTED --------------------------------------------------- * Devel versions 6.x prior to 6.x-1.18 * Devel versions 5.x prior to 5.x-1.2 Drupal core is not affected. If you do not use the contributed Devel module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Devel for Drupal 6.x upgrade to Devel 6.x-1.18 [2] * If you use the Devel for Drupal 5.x upgrade to Devel 5.x-1.2 [3] See also the Devel module project page [4]. -------- REPORTED BY --------------------------------------------------------- Stéphane Corlosquet [5] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ dmitrig01 [6] 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://en.wikipedia.org/wiki/Cross-site_scripting [2] http://drupal.org/node/585982 [3] http://drupal.org/node/585988 [4] http://drupal.org/project/devel [5] http://drupal.org/user/52142 [6] http://drupal.org/user/47566

1 0

SA-CONTRIB-2009-061 - Markdown Preview - Cross Site Scripting
by security-news＠drupal.org 23 Sep '09

23 Sep '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-061 * Project: Markdown Preview (third-party module) * Version: 6.x * Date: 2009 September 23 * Security risk: Less critical * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Markdown Preview module provides a live preview pane that displays the rendered HTML output of your Markdown input. When displaying the live preview, the module does not properly escape user entered data, leading to a cross-site scripting (XSS [1]) vulnerability. Such an attack may lead to a malicious user gaining full administrative access. -------- VERSIONS AFFECTED --------------------------------------------------- * Markdown Preview for Drupal 6.x Drupal core is not affected. If you do not use the contributed Markdown Preview module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ The Markdown Preview module has been abandoned and its releases have been unpublished. It is recommended that it be disabled and removed from your server if in use. For Markdown live preview functionality for nodes and comments, use the Live module [2], which properly escapes the user entered data using the content's current input format. See the Markdown Preview project page [3] for instructions how to enable Markdown preview functionality with the Live module [4]. -------- REPORTED BY --------------------------------------------------------- Reported by David Needham [5]. -------- HANDLED BY ---------------------------------------------------------- On behalf of Drupal security team, this module has been handled by Stéphane Corlosquet [6], Oleg Terenchuk [7], and Dave Reid [8]. -------- CONTACT ------------------------------------------------------------- The security contact for Drupal 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/live [3] http://drupal.org/project/markdownpreview [4] http://drupal.org/project/live [5] http://drupal.org/user/191261 [6] http://drupal.org/user/52142 [7] http://drupal.org/user/78134 [8] http://drupal.org/user/53892

1 0

SA-CONTRIB-2009-060 - Meta tags (Nodewords) - Access bypass
by security-news＠drupal.org 23 Sep '09

23 Sep '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-060 * Project: Meta tags / Nodewords (third-party module) * Version: 6.x * Date: 2009-September-23 * Security risk: Less critical * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The Meta tags (also known as Nodewords) module provides meta tags based on node titles. In certain conditions, the node meta tags were not respecting access permissions, potentially exposing content not available otherwise. -------- VERSIONS AFFECTED --------------------------------------------------- * Meta tags for Drupal 6.x before Meta tags 6.x-1.1 Drupal core is not affected. If you do not use the contributed Meta tags module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use Drupal 6.x upgrade to Meta tags 6.x-1.1 [1]. Also see the Meta tags [2] project page. -------- REPORTED BY --------------------------------------------------------- Barry Jaspan [3] and Ben Jeavons [4], both of the Drupal Security Team [5] -------- FIXED BY ------------------------------------------------------------ Alberto Paderno [6], the module co-maintainer -------- CONTACT ------------------------------------------------------------- The security contact for Drupal can be reached at security at drupal.org or via the form at http://drupal.org/contact. [1] http://drupal.org/node/585706 [2] http://drupal.org/project/nodewords [3] http://drupal.org/user/46413 [4] http://drupal.org/user/91990 [5] http://drupal.org/security-team [6] http://drupal.org/user/55077

1 0

SA-CONTRIB-2009-059 - OpenID - Multiple vulnerabilities
by security-news＠drupal.org 16 Sep '09

16 Sep '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-059 * Project: OpenID (third-party module) * Version: 5.x * Date: 2009-September-16 * Security risk: Critical * Exploitable from: Remote * Vulnerability: Impersonation, cross site request forgery -------- DESCRIPTION --------------------------------------------------------- The contributed OpenID module for Drupal 5 allows users to create an account or log into a Drupal site using one or more OpenID identities. The module does not correctly implement Form API for the form that allows one to link user accounts with OpenID identifiers. A malicious user is therefore able to use cross site request forgeries [1] to add attacker controlled OpenID identities to existing accounts. These OpenID identities can then be used to gain access to the affected accounts. .... OpenID impersonation The OpenID module is not a compliant implementation of the OpenID Authentication 2.0 specification. An implementation error allows a user to access the account of another user when they share the same OpenID 2.0 provider. -------- VERSIONS AFFECTED --------------------------------------------------- * OpenID for Drupal 5.x prior to 5.x-1.3 Drupal 6.x core has a similar issue, see SA-CORE-2009-008 [2] for details. -------- SOLUTION ------------------------------------------------------------ Upgrade to the latest version: * If you use OpenID for Drupal 5.x upgrade to OpenID 5.x-1.3 [3] *Important note*: Some users using OpenID might not be able to use the existing OpenID associations to login after the upgrade. These users should use the one time login via password recovery to get access to their user account and re-add desired associations. These users likely had issues with OpenID logins prior to the upgrade. See also the OpenID project page [4]. -------- REPORTED BY --------------------------------------------------------- The OpenID impersonation was reported by Robert Metcalf [5]. The OpenID association CSRF was reported by Heine Deelstra [6] (*). (*) Member of the Drupal security team. -------- FIXED BY ------------------------------------------------------------ The issues were fixed by Heine Deelstra [7]. -------- CONTACT ------------------------------------------------------------- The security contact for Drupal 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_request_forgery [2] http://drupal.org/node/579482 [3] http://drupal.org/node/579470 [4] http://drupal.org/project/openid [5] http://drupal.org/user/581142 [6] http://drupal.org/user/17943 [7] http://drupal.org/user/17943

1 0

SA-CORE-2009-008 - Drupal core - Multiple vulnerabilities
by security-news＠drupal.org 16 Sep '09

16 Sep '09

* Advisory ID: DRUPAL-SA-CORE-2009-008 * Project: Drupal core * Version: 5.x, 6.x * Date: 2009-September-16 * Security risk: Critical * Exploitable from: Remote * Vulnerability: Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- Multiple vulnerabilities and weaknesses were discovered in Drupal. .... OpenID association cross site request forgeries The OpenID module in Drupal 6 allows users to create an account or log into a Drupal site using one or more OpenID identities. The core OpenID module does not correctly implement Form API for the form that allows one to link user accounts with OpenID identifiers. A malicious user is therefore able to use cross site request forgeries [1] to add attacker controlled OpenID identities to existing accounts. These OpenID identities can then be used to gain access to the affected accounts. This issue affects Drupal 6.x only. .... OpenID impersonation The OpenID module is not a compliant implementation of the OpenID Authentication 2.0 specification. An implementation error allows a user to access the account of another user when they share the same OpenID 2.0 provider. This issue affects Drupal 6.x only. .... File upload File uploads with certain extensions are not correctly processed by the File API. This may lead to the creation of files that are executable by Apache. The .htaccess that is saved into the files directory by Drupal should normally prevent execution. The files are only executable when the server is configured to ignore the directives in the .htaccess file. This issue affects Drupal 6.x only. .... Session fixation Drupal doesn't regenerate the session ID when an anonymous user follows the one time login link used to confirm email addresses and reset forgotten passwords. This enables a malicious user to fix and reuse the session id of a victim under certain circumstances. This issue affects Drupal 5.x only. -------- VERSIONS AFFECTED --------------------------------------------------- * Drupal 6.x before version 6.14. * Drupal 5.x before version 5.20. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you are running Drupal 6.x then upgrade to Drupal 6.14 [2]. * If you are running Drupal 5.x then upgrade to Drupal 5.20 [3]. If you are unable to upgrade immediately, you can apply a patch to secure your installation until you are able to do a proper upgrade. Theses patches fix the security vulnerabilities, but do not contain other fixes which were released in Drupal 6.14 or Drupal 5.20. * To patch Drupal 6.13 use SA-CORE-2009-008-6.13.patch [4]. * To patch Drupal 5.19 use SA-CORE-2009-008-5.19.patch [5]. *Important note*: Some users using OpenID might not be able to use the existing OpenID associations to login after the upgrade. These users should use the one time login via password recovery to get access to their user account and re-add desired associations. These users likely had issues with OpenID logins prior to the upgrade. -------- REPORTED BY --------------------------------------------------------- The session fixation issue was reported by Noel Sharpe [6]. OpenID impersonation was reported by Robert Metcalf [7]. OpenID association CSRF was reported by Heine Deelstra [8] (*). The file upload issue was reported by Heine Deelstra [9] (*). (*) Member of the Drupal security team -------- FIXED BY ------------------------------------------------------------ The session fixation issue was fixed by Jakub Suchy [10]. The OpenID and file upload issues were fixed by Heine Deelstra [11]. -------- 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://en.wikipedia.org/wiki/Cross-site_request_forgery [2] http://ftp.drupal.org/files/projects/drupal-6.14.tar.gz [3] http://ftp.drupal.org/files/projects/drupal-5.20.tar.gz [4] http://drupal.org/files/sa-core-2009-008/SA-CORE-2009-008-6.13.patch [5] http://drupal.org/files/sa-core-2009-008/SA-CORE-2009-008-5.19.patch [6] http://drupal.org/user/551958 [7] http://drupal.org/user/581142 [8] http://drupal.org/user/17943 [9] http://drupal.org/user/17943 [10] http://drupal.org/user/31977 [11] http://drupal.org/user/17943

1 0

SA-CONTRIB-2009-058 - Comment RSS - Access bypass
by security-news＠drupal.org 16 Sep '09

16 Sep '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-058 * Project: Comment RSS (third-party module) * Version: 5.x, 6.x * Date: 2009-September-16 * Security risk: Less critical * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The Comment RSS [1] module provides RSS feeds for comments on individual nodes. The link to this feed contains the node's title. Adding the link to the RSS feed was not respecting access permissions, potentially exposing content not available otherwise. -------- VERSIONS AFFECTED --------------------------------------------------- * Comment RSS for Drupal 5.x before Comment RSS 5.x-2.2 * Comment RSS for Drupal 6.x before Comment RSS 6.x-2.2 Drupal core is not affected. If you do not use the contributed Comment RSS module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use Drupal 5.x upgrade to Comment RSS 5.x-2.2 [2]. * If you use Drupal 6.x upgrade to Comment RSS 6.x-2.2 [3]. See also the Comment RSS [4] project page. -------- REPORTED BY --------------------------------------------------------- Dave Reid [5] of the Drupal Security Team [6] and co-maintainer of the Comment RSS module -------- FIXED BY ------------------------------------------------------------ Dave Reid [7] -------- CONTACT ------------------------------------------------------------- The security contact for Drupal can be reached at security at drupal.org or via the form at http://drupal.org/contact. [1] http://drupal.org/project/commentrss [2] http://drupal.org/node/579292 [3] http://drupal.org/node/579290 [4] http://drupal.org/project/commentrss [5] http://drupal.org/user/53892 [6] http://drupal.org/security-team [7] http://drupal.org/user/53892

1 0

SA-CONTRIB-2009-057 - Date - Cross Site Scripting
by security-news＠drupal.org 16 Sep '09

16 Sep '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-057 * Project: Date (third-party module) * Version: 5.x, 6.x * Date: 2009-September-16 * Security risk: Moderately critical * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Date module provides a date CCK field that can be added to any content type. The Date module does not properly escape user data correctly in some cases when setting the page title. A malicious user with permission to post date content could attempt a cross site scripting [1] (XSS) attack when creating or editing content, leading to the user gaining full administrative access. -------- VERSIONS AFFECTED --------------------------------------------------- * Date for Drupal 6.x prior to 6.x-2.4 * Date for Drupal 6.x prior to 5.x-2.8 Drupal core is not affected. If you do not use the contributed Date module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Upgrade to the latest version: * If you use Date for Drupal 6.x upgrade to Date 6.x-2.4 [2] * If you use Date for Drupal 5.x upgrade to Date 5.x-2.8 [3] See also the Date project page [4]. -------- REPORTED BY --------------------------------------------------------- The Acquia, Inc. support team -------- FIXED BY ------------------------------------------------------------ Karen Stevenson [5], the project maintainer. -------- CONTACT ------------------------------------------------------------- The security contact for Drupal 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/node/579000 [3] http://drupal.org/node/578998 [4] http://drupal.org/project/date [5] http://drupal.org/user/45874

1 0

SA-CONTRIB-2009-056 - Node2Node, Node Browser, Subdomain Manager, Quota by role, Rest API with vulnerabilities, now abandoned
by security-news＠drupal.org 09 Sep '09

09 Sep '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-056 * Project: Node2Node, Node Browser, Subdomain Manager, Quota by role, Rest API (third-party modules) * Version: 5.x, 6.x * Date: 2009 Sept 9 * Security risk: Critical * Exploitable from: Remote * Vulnerability: Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- Multiple vulnerabilities have been found in the following modules which have been abandoned. Their releases have been unpublished and it is recommended that they be disabled and un-installed if in use. -------- MODULES ------------------------------------------------------------- * Node2Node [1] * Node Browser [2] * Subdomain Manager [3] * Quota by role [4] * Rest API [5] Drupal core is not affected. If you do not use any of these contributed modules, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ There is no solution available. It is recommended that you disable any of the vulnerable modules if they are in use on your site. -------- CONTACT ------------------------------------------------------------- The security contact for Drupal can be reached at security at drupal.org or via the form at http://drupal.org/contact. [1] http://drupal.org/project/node2node [2] http://drupal.org/project/node_browser [3] http://drupal.org/project/subdomain_manager [4] http://drupal.org/project/quota_by_role [5] http://drupal.org/project/restapi

1 0

SA-CONTRIB-2009-055 - BUEditor - Cross Site Scripting
by security-news＠drupal.org 09 Sep '09

09 Sep '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-055 * Project: BUEditor (third-party module) * Version: 5.x, 6.x * Date: 2009 September 9 * Security risk: Less critical * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The BUEditor [1] module provides a plain textarea editor designed to facilitate code writing. The module suffers from a Cross Site Scripting (XSS [2]) vulnerability, which allows an attacker to hijack the account of a logged in user by tricking them into visiting a seemingly innocent page using the Live preview feature of BUEditor. -------- VERSIONS AFFECTED --------------------------------------------------- * BUEditor versions 6.x prior to 6.x-1.4 * BUEditor versions 5.x prior to 5.x-1.2 Drupal core is not affected. If you do not use the contributed BUEditor module there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ * Install BUEditor module version 6.x-1.4 [3] * Install BUEditor module version 5.x-1.2 [4] -------- REPORTED BY --------------------------------------------------------- * Reported by Derek Wright [5] of the Drupal security team, fixed by Ufuk Bayburt [6]. -------- CONTACT ------------------------------------------------------------- The security contact for Drupal can be reached at security at drupal.org or via the form at http://drupal.org/contact. [1] http://drupal.org/project/bueditor [2] http://en.wikipedia.org/wiki/Cross_Site_Scripting [3] http://drupal.org/node/572780 [4] http://drupal.org/node/572786 [5] http://drupal.org/user/46549 [6] http://drupal.org/user/9910

1 0