- Security-news - lists.drupal.org

SA-CONTRIB-2012-133 - Taxonomy Image - Cross Site Scripting (XSS) & Arbitrary PHP code execution
by security-news＠drupal.org 29 Aug '12

29 Aug '12

View online: http://drupal.org/node/1762482 * Advisory ID: DRUPAL-SA-CONTRIB-2012-133 * Project: Taxonomy Image [1] (third-party module) * Version: 6.x * Date: 2012-August-29 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting, Arbitrary PHP code execution -------- DESCRIPTION --------------------------------------------------------- The taxonomy_image module allows site administrators to associate images with taxonomy terms. The module did not sufficiently filter retrieval of taxonomy images, allowing users to bypass Drupal's normal file upload protections to install malicious HTML or executable code to the server. This vulnerability is mitigated by the fact that an attacker must have the permissions "administer taxonomy" and "administer taxonomy images", and that the fix for SA-2006-006 - Drupal Core - Execution of arbitrary files in certain Apache configurations [3] should prevent code execution in typical Apache configurations. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Taxonomy Image 6.x-1.x versions prior to 6.x-1.7. Drupal core is not affected. If you do not use the contributed Taxonomy Image [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Taxonomy Image module for Drupal 6.x, upgrade to Taxonomy Image 6.x-1.7 [5] Also see the Taxonomy Image [6] project page. -------- REPORTED BY --------------------------------------------------------- * Chris Burgess [7] -------- FIXED BY ------------------------------------------------------------ * Nancy Wichmann [8], the module maintainer * Niklas Fiekas [9], the module maintainer * Chris Burgess [10] -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [11] of the Drupal Security Team * Ivo Van Geertruyen [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/taxonomy_image [2] http://drupal.org/security-team/risk-levels [3] https://drupal.org/node/65409 [4] http://drupal.org/project/taxonomy_image [5] http://drupal.org/node/1760678 [6] http://drupal.org/project/taxonomy_image [7] http://drupal.org/user/76026 [8] http://drupal.org/user/101412 [9] http://drupal.org/user/1089248 [10] http://drupal.org/user/76026 [11] http://drupal.org/user/36762 [12] http://drupal.org/user/383424 [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-132 - Announcements - Access Bypass
by security-news＠drupal.org 29 Aug '12

29 Aug '12

View online: http://drupal.org/node/1762480 * Advisory ID: DRUPAL-SA-CONTRIB-2012-132 * Project: Announcements [1] (third-party module) * Version: 6.x * Date: 2012-August-29 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The Announcements module creates an "announcement" content type and provides both node views and block lists. The module doesn't sufficiently check node access under certain conditions. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "access announcements". CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Announcements 6.x-1.x versions prior to 6.x-1.5. Drupal core is not affected. If you do not use the contributed Announcements [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Announcements module for Drupal 6.x, upgrade to Announcements 6.x-1.5 [4] Also see the Announcements [5] project page. -------- REPORTED BY --------------------------------------------------------- * Michael Hess [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Nancy Wichmann [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/announcements [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/announcements [4] http://drupal.org/node/1761038 [5] http://drupal.org/project/announcements [6] http://drupal.org/user/102818 [7] http://drupal.org/user/101412 [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-131 - Email Field - Access Bypass
by security-news＠drupal.org 29 Aug '12

29 Aug '12

View online: http://drupal.org/node/1762470 * Advisory ID: DRUPAL-SA-CONTRIB-2012-131 * Project: Email Field [1] (third-party module) * Version: 6.x, 7.x * Date: 2012-August-29 * Security risk: Less critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The email module provides a field type (CCK / FieldAPI) for storing email addresses. Furthermore, it provides a formatter to output the email address as a link to a contact form. The contact form formatter allows a site visitor to email the stored address without letting them see what that e-mail address is. The module didn't sufficiently check access for the contact form page, allowing a site visitor to email the stored address on the entity without having access to the entity itself. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Email Field 6.x-1.x versions prior to 6.x-1.2. * Email Field 7.x-1.x versions prior to 7.x-1.1. Drupal core is not affected. If you do not use the contributed Email Field [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Email Field module for Drupal 6.x, upgrade to Email Field 6.x-1.3 [4] * If you use the Email Field module for Drupal 7.x, upgrade to Email Field 7.x-1.2 [5] Also see the Email Field [6] project page. -------- REPORTED BY --------------------------------------------------------- * Joachim Noreiko [7] -------- FIXED BY ------------------------------------------------------------ * Joachim Noreiko [8] * Matthias Hutterer [9] the module maintainer * Greg Knaddison [10] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [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/email [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/email [4] http://drupal.org/node/1761968 [5] http://drupal.org/node/1761948 [6] http://drupal.org/project/email [7] http://drupal.org/user/107701 [8] http://drupal.org/user/107701 [9] http://drupal.org/user/59747 [10] http://drupal.org/user/36762 [11] http://drupal.org/user/36762 [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-130 - Jstool - Multiple Vulnerabilities
by security-news＠drupal.org 29 Aug '12

29 Aug '12

View online: http://drupal.org/node/1762220 * Advisory ID: DRUPAL-SA-CONTRIB-2012-130 * Project: Javascript Tool [1] (third-party module) * Version: 7.x * Date: 2012-August-29 * Security risk: Highly critical [2] * Exploitable from: Remote * Vulnerability: Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- Javascript Tool enables administrators to edit any javascript file online from an admin panel. The module does not protect its menu paths, which contain sensitive information about all javascript files on the site and their contents. The module does not validate filenames which can lead to potential read/write access to arbitrary files on the server. Write access to files is mitigated by the fact that an attacker must have the permission to use the full_html text format. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Javascript Tool 7.x-1.x versions prior to 7.x-1.7. Drupal core is not affected. If you do not use the contributed Javascript Tool [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Javascript Tool module for Drupal 7.x, upgrade to Javascript Tool 7.x-1.7 [4] Also see the Javascript Tool [5] project page. -------- REPORTED BY --------------------------------------------------------- * Klaus Purer [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * drupwash [7] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [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/jstool [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/jstool [4] http://drupal.org/node/1759538 [5] http://drupal.org/project/jstool [6] http://drupal.org/user/262198 [7] http://drupal.org/user/1652472 [8] http://drupal.org/user/262198 [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-129 - Activism - Access Bypass
by security-news＠drupal.org 29 Aug '12

29 Aug '12

View online: http://drupal.org/node/1762160 * Advisory ID: DRUPAL-SA-CONTRIB-2012-129 * Project: Activism [1] (third-party module) * Version: 6.x * Date: 2012-08-29 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access Bypass -------- DESCRIPTION --------------------------------------------------------- The Activism module is an attempt to standardize the way online advocacy tools are built in Drupal 6. It ships with and creates a "Campaign" content type which is always viewable, even when an administrator unpublishes it or otherwise restricts viewing access. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Activism 6.x-2.0. Drupal core is not affected. If you do not use the contributed Activism [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Activism module for Drupal 6.x, upgrade to Activism 6.x-2.1 [4] Also see the Activism [5] project page. -------- REPORTED BY --------------------------------------------------------- * Sheldon Rampton [6] -------- FIXED BY ------------------------------------------------------------ * Sheldon Rampton [7], the issue reporter * Stella Power [8] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Stella Power [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/activism [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/activism [4] http://drupal.org/node/1762152 [5] http://drupal.org/project/activism [6] http://drupal.org/user/13085 [7] http://drupal.org/user/13085 [8] http://drupal.org/user/66894 [9] http://drupal.org/user/66894 [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-128 - Elegant Theme - Cross Site Scripting (XSS)
by security-news＠drupal.org 15 Aug '12

15 Aug '12

View online: http://drupal.org/node/1733056 * Advisory ID: DRUPAL-SA-CONTRIB-2012-128 * Project: Elegant Theme [1] (third-party module) * Version: 7.x * Date: 2012-August-15 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Elegant Theme is a light weight Drupal 7 theme with a modern look and feel. The theme doesn't properly sanitize user-entered content in the 3 slide gallery on the homepage leading to a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker would have to have the 'administer themes' permission. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Elegant Theme 7.x-1.x versions prior to 7.x-1.0. Drupal core is not affected. If you do not use the contributed Elegant Theme [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Elegant Theme for Drupal 7.x, upgrade to Elegant Theme 7.x-1.1 [4] Also see the Elegant Theme [5] project page. -------- REPORTED BY --------------------------------------------------------- * Greg Knaddison [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * saran.quardz [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/elegant_theme [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/elegant_theme [4] http://drupal.org/node/1722880 [5] http://drupal.org/project/elegant_theme [6] http://drupal.org/user/36762 [7] http://drupal.org/user/1031208 [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-127 - Custom Publishing Options - Cross Site Scripting (XSS) Vulnerability
by security-news＠drupal.org 15 Aug '12

15 Aug '12

View online: http://drupal.org/node/1732980 * Advisory ID: DRUPAL-SA-CONTRIB-2012-127 * Project: Custom Publishing Options [1] (third-party module) * Version: 6.x * Date: 2012-August-15 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Custom Publishing Options module allows you to create custom publishing options for nodes. It allows you to add to the default options of Publish, Promote to Front Page, and Sticky. It also ingrates with views to allow you add as a field, sort and filter by, your custom options. The module doesn't sufficiently sanitize status labels containing HTML. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer nodes". CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Custom Publishing Options 6.x-1.x versions prior to 6.x-1.4. Drupal core is not affected. If you do not use the contributed Custom Publishing Options [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Custom Publishing Options module for Drupal 6.x, upgrade to Custom Publishing Options 6.x-1.5 [4] Also see the Custom Publishing Options [5] project page. -------- REPORTED BY --------------------------------------------------------- * Publicly disclosed. -------- FIXED BY ------------------------------------------------------------ * Kevin Quillen [6] -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [7] of the Drupal Security Team * Ivo Van Geertruyen [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/custom_pub [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/custom_pub [4] http://drupal.org/node/1730766 [5] http://drupal.org/project/custom_pub [6] http://drupal.org/user/317279 [7] http://drupal.org/user/36762 [8] http://drupal.org/user/383424 [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-126 - Hotblocks - Cross Site Scripting (XSS) and Denial of Service (DoS)
by security-news＠drupal.org 15 Aug '12

15 Aug '12

View online: http://drupal.org/node/1732946 * Advisory ID: DRUPAL-SA-CONTRIB-2012-126 * Project: HotBlocks [1] (third-party module) * Version: 6.x * Date: 2012-August-15 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting, Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- The Hotblocks module provides an enhanced GUI for administering blocks and block content that is intended to be simpler and more controllable for less privileged users than the default block administration tools. .... Cross Site Scripting (XSS) The module doesn't sufficiently sanitize the user input for "block names" on the module's settings page. A user could inject arbitrary scripts into pages affecting site users. This XSS vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer hotblocks". .... Denial of Service (DoS) The hotblocks user interface also allows a user to configure one hotblock to reference itself as content, thereby creating an infinite loop and potentially rendering a site unusable. The DoS vulnerability is mitigated by the fact that a user must have a role with the permission "administer hotblocks" or a user with said permission must have configured the site such that it allows hotblocks to be embedded in other hotblocks. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Hotblocks 6.x-1.x versions prior to 6.x-1.8. Drupal core is not affected. If you do not use the contributed HotBlocks [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Hotblocks module for Drupal 6.x, upgrade to Hotblocks 6.x-1.8 [4] Also see the HotBlocks [5] project page. -------- REPORTED BY --------------------------------------------------------- * Justin C. Klein Keane [6] -------- FIXED BY ------------------------------------------------------------ * Justin Dodge [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/hotblocks [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/hotblocks [4] http://drupal.org/node/1732828 [5] http://drupal.org/project/hotblocks [6] http://drupal.org/user/302225 [7] http://drupal.org/user/238638 [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-125 - Chaos tool suite (ctools) - Local File Inclusion and Cross Site Scripting (XSS)
by security-news＠drupal.org 09 Aug '12

09 Aug '12

View online: http://drupal.org/node/1719548 * Advisory ID: DRUPAL-SA-CONTRIB-2012-125 * Project: Chaos tool suite (ctools) [1] (third-party module) * Version: 6.x, 7.x * Date: 2012-August-8 * Security risk: Critical [2] * Exploitable from: Remote * Vulnerability: Local File Inclusion and Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Chaos tool suite is primarily a set of APIs and tools to improve the developer experience. The module doesn't sufficiently validate css import statements to confirm they only include css content appropriate to show to end users. This could allow a malicious user to add sensitive content from the site (e.g. settings.php) exposing that sensitive content to visitors of the page. It could also be used to execute a Cross Site Scripting attack. This vulnerability is party mitigated by the fact that an attacker must have a role with a permission to place custom CSS into a field. However, any user who can create or edit a node may have sufficient permissions to place the CSS depending on the site configuration. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Chaos tool suite (ctools) 6.x-1.x versions prior to 6.x-1.9. * Chaos tool suite (ctools) 7.x-1.x versions prior to 7.x-1.1. Drupal core is not affected. If you do not use the contributed Chaos tool suite (ctools) [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Ctools module for Drupal 6.x, upgrade to Ctools 6.x-1.9 [4] * If you use the Ctools module for Drupal 7.x, upgrade to Ctools 7.x-1.1 [5] Also see the Chaos tool suite (ctools) [6] project page. -------- REPORTED BY --------------------------------------------------------- * Casey [7] -------- FIXED BY ------------------------------------------------------------ * Tim Plunkett [8] a module maintainer * John Morahan [9] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * John Morahan [10] of the Drupal Security Team * Heine Deelstra [11] of the Drupal Security Team * Greg Knaddison [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/ctools [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/ctools [4] http://drupal.org/node/1719786 [5] http://drupal.org/node/1719782 [6] http://drupal.org/project/ctools [7] http://drupal.org/user/32403 [8] http://drupal.org/user/241634 [9] http://drupal.org/user/58170 [10] http://drupal.org/user/58170 [11] http://drupal.org/user/17943 [12] http://drupal.org/user/36762 [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-124 - Mime Mail - Access Bypass
by security-news＠drupal.org 08 Aug '12

08 Aug '12

View online: http://drupal.org/node/1719482 * Advisory ID: DRUPAL-SA-CONTRIB-2012-124 * Project: Mime Mail [1] (third-party module) * Version: 6.x * Date: 2012-August-8 * Security risk: Critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The MIME Mail module allows users to send MIME-encoded e-mail messages with embedded images and attachments. The module doesn't perform proper access checks, allowing a user to send arbitrary (e.g. the settings.php) files as attachments. In the latest version users must have the "send arbitrary files" permission to access files located outside the public files directory. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Mime Mail 6.x-1.x versions prior to 6.x-1.1. Drupal core is not affected. If you do not use the contributed Mime Mail [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Mime Mail module for Drupal 6.x, upgrade to Mime Mail 6.x-1.1 [4] Also see the Mime Mail [5] project page. -------- REPORTED BY --------------------------------------------------------- * joglin [6] -------- FIXED BY ------------------------------------------------------------ * Jeremiah Davis [7] the module maintainer * Gabor Seljan [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [9] of the Drupal Security Team * Dave Reid [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/mimemail [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/mimemail [4] http://drupal.org/node/1719446 [5] http://drupal.org/project/mimemail [6] http://drupal.org/user/86464 [7] http://drupal.org/user/228997 [8] http://drupal.org/user/232117 [9] http://drupal.org/user/36762 [10] http://drupal.org/user/53892 [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