Security-news

security-news@drupal.org

1 participants
1782 discussions

SA-CONTRIB-2009-042 - Submitted By - Cross Site Scripting
by security-news＠drupal.org 15 Jul '09

15 Jul '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-042 * Project: Submitted By (third-party module) * Version: 6.x * Date: 2009-July-15 * Security risk: Less critical * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Submitted By is a module to let you control the format of the "Submitted by" information on your content per content type. This module does not properly escape user input used in building the string to display the "submitted by" text. Only administrators with the 'administer content types' permission can enter this text. A user with this administrative privileges could attempt a cross site scripting [1] (XSS) attack which may lead to the user gaining full administrative access. In general, the permission "administer content types" is comparable in scope to the "administer site configuration" permission. Only grant this permission to trusted site administrators. See: http://drupal.org/node/372836 -------- VERSIONS AFFECTED --------------------------------------------------- * Submitted By for Drupal 6.x prior to 6.x-1.3 Drupal core is not affected. If you do not use the contributed Submitted By module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Upgrade to the latest version: * If you use Submitted By for Drupal 6.x upgrade to Submitted By 6.x-1.3 [2] See also the Submitted By project page [3]. -------- REPORTED BY --------------------------------------------------------- Nancy Wichmann [4], the project maintainer. -------- FIXED BY ------------------------------------------------------------ Nancy Wichmann [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/519246 [3] http://drupal.org/project/submitted_by [4] http://drupal.org/user/101412 [5] http://drupal.org/user/101412

1 0

SA-CONTRIB-2009-041 - Nodequeue - Access bypass
by security-news＠drupal.org 08 Jul '09

08 Jul '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-041 * Project: Nodequeue (third-party module) * Version: 5.x, 6.x * Date: 2009-July-08 * Security risk: Not critical * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The Nodequeue module enables an administrator to arbitrarily put nodes in a group with an arbitrary order for any purpose, such as providing a listing of nodes or featuring a particular node. On the queue administration screen, users with permission to manipulate a queue are presented with an autocomplete textfield that allows them to type the title of a node and add it to a queue. This textfield fails to restrict unpublished node titles from being displayed to users who lack the 'administer content' permission, allowing unprivileged users to view the title of unpublished nodes. -------- VERSIONS AFFECTED --------------------------------------------------- * Nodequeue 6.x prior to 6.x-2.3 * Nodequeue 5.x prior to 5.x-2.8 Drupal core is not affected. If you do not use the contributed Nodequeue module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use Nodequeue 6.x upgrade to Nodequeue 6.x-2.3 [1] * If you use Nodequeue 5.x upgrade to Nodequeue 5.x-2.8 [2] See also the Nodequeue [3] project page. -------- REPORTED BY --------------------------------------------------------- Ezra Barnett Gildesgame (ezra-g [4]) -------- FIXED BY ------------------------------------------------------------ Ezra Barnett Gildesgame, the Nodequeue maintainer (ezra-g [5]) -------- 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/513726 [2] http://drupal.org/node/513732 [3] http://drupal.org/project/nodequeue [4] http://drupal.org/user/69959/ [5] http://drupal.org/user/69959/

1 0

SA-CONTRIB-2009-040 - Advanced Forum - Multiple vulnerabilities
by security-news＠drupal.org 01 Jul '09

01 Jul '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-040 * Project: Advanced Forum (third-party module) * Version: 5.x, 6.x * Date: 2009-July-1 * Security risk: Moderately critical * Exploitable from: Remote * Vulnerability: Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- .... Cross-site scripting The Advanced Forum module does not correctly handle certain arguments obtained from the URL. By enticing a suitably privileged user to visit a specially crafted URL, a malicious user is able to insert arbitrary HTML and script code into forum pages. Such a cross-site scripting attack may lead to the malicious user gaining administrative access. Wikipedia has more information about cross-site scripting (XSS). This issue affects both Advanced Forum for Drupal 5.x and Advanced Forum for Drupal 6.x. .... Input format access bypass User signatures have no separate input format, they use the format of the comment with which they are displayed. A user will no longer be able to edit a comment when an administrator changes the comment's input format to a format that is not accessible to the user. However they will still be able to modify their signature, which will then be processed by the new input format. If the new format is very permissive, via their signature, the user may be able to insert arbitrary HTML and script code into pages or, when the PHP filter is enabled for the new format, execute PHP code. This issue affects Advanced Forum for Drupal 6.x only. -------- VERSIONS AFFECTED --------------------------------------------------- * Advanced Forum for Drupal 5.x prior to Advanced Forum 5.x-1.2 * Advanced Forum for Drupal 6.x prior to Advanced Forum 6.x-1.2 -------- SOLUTION ------------------------------------------------------------ Upgrade to the latest version: * If you use Advanced Forum for Drupal 5.x upgrade to Advanced Forum 5.x-1.1 [1] * If you use Advanced Forum for Drupal 6.x upgrade to Advanced Forum 6.x-1.1 [2] See also the Advanced Forum project page [3]. -------- FIXED BY ------------------------------------------------------------ Michelle Cox [4], 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://drupal.org/node/507550 [2] http://drupal.org/node/507526 [3] http://drupal.org/project/advanced_forum [4] http://drupal.org/user/23570

1 0

SA-CORE-2009-007 - Drupal core - Multiple vulnerabilities
by security-news＠drupal.org 01 Jul '09

01 Jul '09

* Advisory ID: DRUPAL-SA-CORE-2009-007 * Project: Drupal core * Version: 5.x, 6.x * Date: 2009-July-1 * Security risk: Moderately critical * Exploitable from: Remote * Vulnerability: Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- Multiple vulnerabilities and weaknesses were discovered in Drupal. .... Cross-site scripting The Forum module does not correctly handle certain arguments obtained from the URL. By enticing a suitably privileged user to visit a specially crafted URL, a malicious user is able to insert arbitrary HTML and script code into forum pages. Such a cross-site scripting attack may lead to the malicious user gaining administrative access. Wikipedia has more information about cross-site scripting [1] (XSS). This issue affects Drupal 6.x only. .... Input format access bypass User signatures have no separate input format, they use the format of the comment with which they are displayed. A user will no longer be able to edit a comment when an administrator changes the comment's input format to a format that is not accessible to the user. However they will still be able to modify their signature, which will then be processed by the new input format. If the new format is very permissive, via their signature, the user may be able to insert arbitrary HTML and script code into pages or, when the PHP filter is enabled for the new format, execute PHP code. This issue affects Drupal 6.x only. .... Password leaked in URL When an anonymous user fails to login due to mistyping his username or password, and the page he is on contains a sortable table, the (incorrect) username and password are included in links on the table. If the user visits these links the password may then be leaked to external sites via the HTTP referer. In addition, if the anonymous user is enticed to visit the site via a specially crafted URL while the Drupal page cache is enabled, a malicious user might be able to retrieve the (incorrect) username and password from the page cache. This issue affects both Drupal 5.x and Drupal 6.x -------- VERSIONS AFFECTED --------------------------------------------------- * Drupal 5.x before version 5.19. * Drupal 6.x before version 6.13. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you are running Drupal 6.x then upgrade to Drupal 6.13 [2]. * If you are running Drupal 5.x then upgrade to Drupal 5.19 [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 vulnerability, but do not contain other fixes which were released in Drupal 5.19 or Drupal 6.13. * To patch Drupal 6.12 use SA-CORE-2009-007-6.12.patch [4]. * To patch Drupal 5.18 use SA-CORE-2009-007-5.18.patch [5]. -------- REPORTED BY --------------------------------------------------------- The forum XSS issue was independently reported by Mark Piper of Catalyst IT Ltd, Sven Herrmann and Brandon Knight. The user signature issue was reported by Gerhard Killesreiter [6] of the Drupal security team. The password in URL issue was reported by Sumit Datta [7]. -------- FIXED BY ------------------------------------------------------------ The forum XSS issue was fixed by Heine Deelstra [8], Peter Wolanin [9] and Charlie Gordon [10]. The user signature issue was fixed by David Rothstein [11], Charlie Gordon [12], Heine Deelstra [13] and Gábor Hojtsy [14]. The password in URL issue was fixed by Damien Tournoud [15] and Bart Jansens [16]. -------- 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://ftp.drupal.org/files/projects/drupal-6.13.tar.gz [3] http://ftp.drupal.org/files/projects/drupal-5.19.tar.gz [4] http://drupal.org/files/sa-core-2009-007/SA-CORE-2009-007-6.12.patch [5] http://drupal.org/files/sa-core-2009-007/SA-CORE-2009-007-5.18.patch [6] http://drupal.org/user/227 [7] http://drupal.org/user/59022 [8] http://drupal.org/user/17943 [9] http://drupal.org/user/49851 [10] http://drupal.org/user/157412 [11] http://drupal.org/user/124982 [12] http://drupal.org/user/157412 [13] http://drupal.org/user/17943 [14] http://drupal.org/user/4166 [15] http://drupal.org/user/22211 [16] http://drupal.org/user/5330

1 0

SA-CONTRIB-2009-039 - Links Package - Cross Site Scripting
by security-news＠drupal.org 25 Jun '09

25 Jun '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-039 * Project: Links Package (third-party module) * Version: 5.x, 6.x * Date: 2009-June-25 * Security risk: Moderately critical * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Links Package is a multi-module set for managing URL links in a master directory, and attaching them in various ways to your content pages. The Links Related module of the Links Package does not properly escape user input used as the title on certain pages. A user with privileges to create content could attempt a cross site scripting [1] (XSS) attack which may lead to the user gaining full administrative access. -------- VERSIONS AFFECTED --------------------------------------------------- * Links Package for Drupal 5.x prior to Links Package 5.x-1.13 * Links Package for Drupal 6.x prior to Links Package 6.x-1.2 Drupal core is not affected. If you do not use the contributed Links Package, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Upgrade to the latest version: * If you use Links Package for Drupal 5.x upgrade to Links Package 5.x-1.13 [2] * If you use Links Packsge for Drupal 6.x upgrade to Links Package 6.x-1.2 [3] See also the Links Package project page [4]. -------- REPORTED BY --------------------------------------------------------- Stéphane Corlosquet [5] of the Drupal Security Team [6]. -------- FIXED BY ------------------------------------------------------------ Scott Courtney [7], 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/501356 [3] http://drupal.org/node/501360 [4] http://drupal.org/project/links [5] http://drupal.org/user/52142 [6] http://drupal.org/security-team [7] http://drupal.org/user/9184

1 0

SA-CONTRIB-2009-038 - Nodequeue - Multiple vulnerabilities
by security-news＠drupal.org 10 Jun '09

10 Jun '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-038 * Project: Nodequeue (third-party module) * Version: 5.x, 6.x * Date: 2009-June-10 * Security risk: Moderately critical * Exploitable from: Remote * Vulnerability: Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- The Nodequeue module enables an administrator to arbitrarily put nodes in a group for some purpose, such as providing a listing of nodes or featuring a particular node. It suffers from a cross-site scripting [1] (XSS) vulnerability due to not properly sanitizing vocabulary names before they are displayed. Additionally, the module does not respect node access restrictions when displaying node titles. -------- VERSIONS AFFECTED --------------------------------------------------- * Nodequeue for Drupal 5.x prior to Nodequeue 5.x-2.7 * Nodequeue for Drupal 6.x prior to Nodequeue 6.x-2.2 Drupal core is not affected. If you do not use the contributed Nodequeue module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Upgrade to the latest version: * If you use Nodequeue for Drupal 5.x upgrade to Nodequeue 5.x-2.7 [2] * If you use Nodequeue for Drupal 6.x upgrade to Nodequeue 6.x-2.2 [3] See also the Nodequeue project page [4]. -------- REPORTED BY --------------------------------------------------------- * The XSS issue was reported by Justin C. Klein Keane [5]. * The access bypass issue was reported by Ezra Barnett Gildesgame [6]. -------- FIXED BY ------------------------------------------------------------ * The XSS issue was fixed by Justin C. Klein Keane [7]. * The access bypass issue was fixed by Ezra Barnett Gildesgame [8] and Earl Miles [9]. -------- 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/488104 [3] http://drupal.org/node/488102 [4] http://drupal.org/project/nodequeue [5] http://drupal.org/user/302225 [6] http://drupal.org/user/69959 [7] http://drupal.org/user/302225 [8] http://drupal.org/user/69959 [9] http://drupal.org/user/26979

1 0

SA-CONTRIB-2009-037 - Views - Multiple vulnerabilities
by security-news＠drupal.org 10 Jun '09

10 Jun '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-037 * Project: Views * Versions: 6.x-2.x * Date: 2009-June-10 * Security risk: Moderately critical * Exploitable from: Remote * Vulnerability: Cross Site Scripting (XSS), Access Bypass -------- DESCRIPTION --------------------------------------------------------- The Views module provides a flexible method for Drupal site designers to control how lists of content are presented. In the Views UI administrative interface when configuring exposed filters, user input presented as possible exposed filters is not correctly filtered, potentially allowing malicious users to insert arbitrary HTML and script code into these pages. In addition, content entered by users with 'administer views' permission into the View name when defining custom views is subsequently displayed without being filtered. Such cross site scripting [1] (XSS) attacks may lead to a malicious user gaining full administrative access. An access bypass may exist where unpublished content owned by the anonymous user (e.g. content created by a user whose account was later deleted) is visible to any anonymous user there is a view already configured to show it incorrectly. An additional access bypass may occur because Views may generate queries which disrespect node access control. Users may be able to access private content if they have permission to see the resulting View. -------- VERSIONS AFFECTED --------------------------------------------------- * Versions of Views for Drupal 6.x prior to 6.x-2.6 Drupal core is not affected. If you do not use the Views module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version. * If you use Views for Drupal 6.x upgrade to 6.x-2.6 [2] In addition, preventing the node access bypass may require adding *node: access filters* to the View manually if using relationships to nodes that might be restricted. Also see the Views project page [3]. -------- REPORTED BY --------------------------------------------------------- * The exposed filters XSS was reported by Derek Wright (dww [4]) of the Drupal Security Team [5] * The XSS from the view name was reported by Justin Klein Keane (Justin_KleinKeane [6]) * The unpublished content access bypass was reported by Brandon Bergren (bdragon [7]) * The node access query bypass was reported by Moshe Weitzman (moshe weitzman [8]) of the Drupal Security Team [9] -------- FIXED BY ------------------------------------------------------------ Earl Miles (merlinofchaos [10]) Views 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 and by selecting the security issues category. [1] http://en.wikipedia.org/wiki/Cross-site_scripting [2] http://drupal.org/node/488082 [3] http://drupal.org/project/views [4] http://drupal.org/user/46549 [5] http://drupal.org/security-team [6] http://drupal.org/user/302225 [7] http://drupal.org/user/53081 [8] http://drupal.org/user/23 [9] http://drupal.org/security-team [10] http://drupal.org/user/26979

1 0

SA-CONTRIB-2009-036 - Services - Impersonation
by security-news＠drupal.org 10 Jun '09

10 Jun '09

* Advisory ID: SA-CONTRIB-2009-036 * Project: Services (third-party module) * Version: 6.x * Date: 2009 June 10 * Security risk: Critical * Exploitable from: Remote * Vulnerability: Impersonation -------- DESCRIPTION --------------------------------------------------------- The Services module provides integration of external applications with Drupal. Service callbacks may be used with multiple interfaces like XMLRPC, SOAP, REST, AMF. When key based access is enabled any user may view or add keys, allowing a third party to access services they would not otherwise be able to access. The services that can be exploited depend on the access control checks that are in place on a given client site. -------- VERSIONS AFFECTED --------------------------------------------------- Services for 6.x before version 6.x-0.14. Drupal core is not affected. If you do not use the contributed Services module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Upgrade to the latest version: If you are running Services 6.x then upgrade to Services 6.x-0.14 [1]. If you are running a development version of Services module please upgrade to a version dated later than 9th June 2009. See also the Services [2] project page. -------- REPORTED BY --------------------------------------------------------- Gerhard Killesreiter [3] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ Marc Ingram [4]. -------- 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/487784 [2] http://drupal.org/project/services [3] http://drupal.org/user/227 [4] http://drupal.org/user/77320

1 0

SA-CONTRIB-2009-035 - Booktree - Cross site scripting
by security-news＠drupal.org 10 Jun '09

10 Jun '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-035 * Project: Booktree (third-party module) * Version: 5.x, 6.x * Date: 2009-June-10 * Security risk: Moderately critical * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Booktree takes as input a series of Book nodes and create a tree-like structure using Book node relationships.The Booktree module does not properly escape node title and node body on tree root pages. A user with privileges to create book pages could attempt a cross site scripting [1] (XSS) attack which may lead to the user gaining full administrative access. -------- VERSIONS AFFECTED --------------------------------------------------- * Booktree for Drupal 5.x prior to Booktree 5.x-7.3 * Booktree for Drupal 6.x prior to Booktree 6.x-1.1 Drupal core is not affected. If you do not use the contributed Booktree module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Upgrade to the latest version: * If you use Booktree for Drupal 5.x upgrade to Booktree 5.x-7.3 [2] * If you use Booktree for Drupal 6.x upgrade to Booktree 6.x-1.1 [3] See also the Booktree project page [4]. -------- REPORTED BY --------------------------------------------------------- Stéphane Corlosquet [5] of the Drupal Security Team [6]. -------- FIXED BY ------------------------------------------------------------ Uccio [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_scripting [2] http://drupal.org/node/487812 [3] http://drupal.org/node/487810 [4] http://drupal.org/project/booktree [5] http://drupal.org/user/52142 [6] http://drupal.org/security-team [7] http://drupal.org/user/32370

1 0

SA-CONTRIB-2009-034 - Taxonomy manager - Cross site scripting
by security-news＠drupal.org 10 Jun '09

10 Jun '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-034 * Project: Taxonomy manager (third-party module) * Version: 5.x, 6.x * Date: 2009-June-10 * Security risk: Moderately critical * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Taxonomy manager module provides additional tools for administering taxonomy through Drupal. A vocabulary gets displayed in a dynamic tree view, where parent terms can be expanded to list their nested child terms or can be collapsed. The module does not properly escape some user-supplied data, allowing malicious users to insert arbitrary HTML and script code into the administrative pages provided by this module. A user who has the 'administer taxonomy' permission, and (depending on configuration) a user able to add taxonomy terms via free tagging, could attempt a cross site scripting [1] (XSS) attack which may lead to the user gaining full administrative access. -------- VERSIONS AFFECTED --------------------------------------------------- * Taxonomy manager 6.x prior to 6.x-1.1 * Taxonomy manager 5.x prior to 5.x-1.2 Drupal core is not affected. If you do not use the contributed Taxonomy manager module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use Taxonomy manager 6.x upgrade to Taxonomy manager 6.x-1.1 [2] * If you use Taxonomy manager 5.x upgrade to Taxonomy manager 5.x-1.2 [3] See also the Taxonomy manager [4] project page. -------- REPORTED BY --------------------------------------------------------- Justin Klein Keane (Justin_KleinKeane [5]) -------- FIXED BY ------------------------------------------------------------ Matthias Hutterer (mh86 [6] the maintainer) and Justin Klein Keane (Justin_KleinKeane [7]) -------- 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/487602 [3] http://drupal.org/node/487620 [4] http://drupal.org/project/taxonomy_manager [5] http://drupal.org/user/302225 [6] http://drupal.org/user/59747 [7] http://drupal.org/user/302225

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