Security-news

security-news@drupal.org

1 participants
1782 discussions

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

SA-CONTRIB-2012-095 - Simplenews - Information Disclosure
by security-news＠drupal.org 06 Jun '12

06 Jun '12

View online: http://drupal.org/node/1619848 * Advisory ID: DRUPAL-SA-CONTRIB-2012-095 * Project: Simplenews [1] (third-party module) * Version: 6.x, 7.x * Date: 2012-June-06 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Information Disclosure -------- DESCRIPTION --------------------------------------------------------- Simplenews publishes and sends newsletters. When subscribing to a Simplenews mailing list, confirmation may be required, and Simplenews may disclose the user's e-mail address on the confirmation page. Further, due to the absence of a noindex tag, the list of e-mail addresses can subsequently be indexed by search engines. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Simplenews 6.x-1.x versions prior to 6.x-1.4 * Simplenews 6.x-2.x versions prior to 6.x-2.0-alpha4 * Simplenews 7.x-1.x versions prior to 7.x-1.0-rc1 Drupal core is not affected. If you do not use the contributed Simplenews [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Simplenews module for Drupal 6.x, upgrade to Simplenews 6.x-1.4 [4] or Simplenews 6.x-2.0-alpha4 [5] * If you use the Simplenews module for Drupal 7.x, upgrade to Simplenews 7.x-1.0-rc1 [6] Also see the Simplenews [7] project page. -------- REPORTED BY --------------------------------------------------------- * Laza [8] * Sascha Grossenbacher [9] the module maintainer -------- FIXED BY ------------------------------------------------------------ * Sascha Grossenbacher [10] the module maintainer * Dave Reid [11] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Dave Reid [12] of the Drupal Security Team * Greg Knaddison [13] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at http://drupal.org/contact [14]. Learn more about the Drupal Security team and their policies [15], writing secure code for Drupal [16], and securing your site [17]. [1] http://drupal.org/project/simplenews [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/simplenews [4] http://drupal.org/node/1619812 [5] http://drupal.org/node/1619818 [6] http://drupal.org/node/1619820 [7] http://drupal.org/project/simplenews [8] http://drupal.org/user/145993 [9] http://drupal.org/user/214652 [10] http://drupal.org/user/214652 [11] http://drupal.org/user/53892 [12] http://drupal.org/user/53892 [13] http://drupal.org/user/36762 [14] http://drupal.org/contact [15] http://drupal.org/security-team [16] http://drupal.org/writing-secure-code [17] http://drupal.org/security/secure-configuration

1 0

SA-CONTRIB-2012-094 - Maestro module - Cross Site Request Forgery (CSRF), Cross Site Scripting (XSS)
by security-news＠drupal.org 06 Jun '12

06 Jun '12

View online: http://drupal.org/node/1619830 * Advisory ID: DRUPAL-SA-CONTRIB-2012-094 * Project: Maestro [1] (third-party module) * Version: 7.x * Date: 2012-June-06 * Security risk: Critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting, Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- The Maestro module is a workflow engine/solution that facilitates simple and complex business process automation. The module doesn't sufficiently filter user-supplied data in its admin screens leading to a Cross Site Scripting (XSS) vulnerability. A Cross Site Request Forgery vulnerability in the control of the module could allow a user to change workflows including injecting malicious scripts to exploit the XSS. This vulnerability is mitigated by the fact that an attacker must have a role with the maestro admin permissions or use CSRF against a user with that permission. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * maestro 7.x-1.x versions prior to 7.x-1.2. Drupal core is not affected. If you do not use the contributed Maestro [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the maestro module for Drupal 7.x, upgrade to Maestro 7.x-1.2 [4] Also see the Maestro [5] project page. -------- REPORTED BY --------------------------------------------------------- * Steve Persch [6] -------- FIXED BY ------------------------------------------------------------ * Blaine Lang [7] module maintainer * Randy Kolenko [8] module maintainer * Greg Knaddison [9] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [10] of the Drupal Security Team * Stella Power [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/maestro [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/maestro [4] http://drupal.org/node/1617952 [5] http://drupal.org/project/maestro [6] http://drupal.org/user/179805 [7] http://drupal.org/user/726382 [8] http://drupal.org/user/704970 [9] http://drupal.org/user/36762 [10] http://drupal.org/user/36762 [11] http://drupal.org/user/66894 [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-093 - Node Embed - Access Bypass
by security-news＠drupal.org 06 Jun '12

06 Jun '12

View online: http://drupal.org/node/1619824 * Advisory ID: DRUPAL-SA-CONTRIB-2012-093 * Project: Node Embed [1] (third-party module) * Version: 6.x, 7.x * Date: 2012-June-06 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- Node Embed gives content editors an interface for selecting and embedding nodes using a WYSIWYG editor. The interface for selecting nodes is a page that had no access check, allowing users to view node titles they might not have access to. This issue only affects your site if you have unpublished nodes or use a node access module to restrict content access from some users. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Node Embed 6.x-1.x versions prior to 6.x-1.5. * Node Embed 7.x-1.x versions prior to 7.x-1.0. Drupal core is not affected. If you do not use the contributed Node Embed [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Node Embed module for Drupal 6.x, upgrade to Node Embed 6.x-1.5 [4] * If you use the Node Embed module for Drupal 7.x, upgrade to Node Embed 7.x-1.0 [5] Also see the Node Embed [6] project page. -------- REPORTED BY --------------------------------------------------------- * Paul Aumer-Ryan [7] -------- FIXED BY ------------------------------------------------------------ * Scott Reynen [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/node_embed [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/node_embed [4] http://drupal.org/node/1618430 [5] http://drupal.org/node/1618428 [6] http://drupal.org/project/node_embed [7] http://drupal.org/user/422353 [8] http://drupal.org/user/109890 [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-092 - Organic Groups - Cross Site Scripting (XSS) and Access Bypass
by security-news＠drupal.org 06 Jun '12

06 Jun '12

View online: http://drupal.org/node/1619810 * Advisory ID: DRUPAL-SA-CONTRIB-2012-092 * Project: Organic groups [1] (third-party module) * Version: 6.x * Date: 2012-June-06 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting, Access bypass -------- DESCRIPTION --------------------------------------------------------- The Organic Groups module enables users to create and manage their own 'groups'. Each group can have subscribers, and maintains a group home page where subscribers communicate amongst themselves. .... Cross Site Scripting The module doesn't sufficiently filter user supplied text when used in connection with the Vertical Tabs module. This vulnerability is mitigated by the fact that an attacker must have a role with the permission to create or edit a group title and the site must have the contributed Vertical Tabs module installed and the Vertical Tabs configuration must include the Organic Group select area (this is the default configuration when Vertical Tabs is enabled). .... Access bypass The module's default views do not sufficiently check the Drupal core permission to /access content/. This vulnerability is mitigated by the fact that a site must have removed the "access content" permission to all users. This is not a common configuration. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Organic groups 6.x-2.x versions prior to 6.x-2.4. Drupal core is not affected. If you do not use the contributed Organic groups [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Organic groups module for Drupal 6.x, upgrade to Organic Groups 6.x-2.4 [4] Also see the Organic groups [5] project page. -------- REPORTED BY --------------------------------------------------------- * Ezra Barnett Gildesgame [6] identified the Cross Site Scripting issue * Fox [7] identified the Access Bypass issue -------- FIXED BY ------------------------------------------------------------ * Adam Ross [8] the module maintainer * Fox [9] * Greg Knaddison [10] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [11] of the Drupal Security Team * Forest Monsen [12] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at http://drupal.org/contact [13]. Learn more about the Drupal Security team and their policies [14], writing secure code for Drupal [15], and securing your site [16]. [1] http://drupal.org/project/og [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/og [4] http://drupal.org/node/1619736 [5] http://drupal.org/project/og [6] http://drupal.org/user/69959 [7] http://drupal.org/user/426416 [8] http://drupal.org/user/346868 [9] http://drupal.org/user/426416 [10] http://drupal.org/user/36762 [11] http://drupal.org/user/36762 [12] http://drupal.org/user/181798 [13] http://drupal.org/contact [14] http://drupal.org/security-team [15] http://drupal.org/writing-secure-code [16] http://drupal.org/security/secure-configuration

1 0

SA-CONTRIB-2012-091 - Token Authentication - Access bypass
by security-news＠drupal.org 06 Jun '12

06 Jun '12

View online: http://drupal.org/node/1619808 * Advisory ID: DRUPAL-SA-CONTRIB-2012-091 * Project: Tokenauth [1] (third-party module) * Version: 6.x * Date: 2012-June-06 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The Token Authentication module provides a token for use in the URL to authenticate users to a site. Under certain uncommon situations, the module may not revert a user's session properly. Depending on how tokenauth is used, this could result in subsequent requests being performed as a user with additional privileges when they shouldn't. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Tokenauth 6.x-1.x versions prior to 6.x-1.7. Drupal core is not affected. If you do not use the contributed Token Authentication [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Tokenauth module for Drupal 6.x, upgrade to Tokenauth 6.x-1.7 [4] Also see the Tokenauth [5] project page. -------- REPORTED BY --------------------------------------------------------- * John Morahan [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Adam Ross [7] 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 [8]. Learn more about the Drupal Security team and their policies [9], writing secure code for Drupal [10], and securing your site [11]. [1] http://drupal.org/project/tokenauth [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/tokenauth [4] http://drupal.org/node/1618476 [5] http://drupal.org/project/tokenauth [6] http://drupal.org/user/58170 [7] http://drupal.org/user/346868 [8] http://drupal.org/contact [9] http://drupal.org/security-team [10] http://drupal.org/writing-secure-code [11] http://drupal.org/security/secure-configuration

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