- Security-news - lists.drupal.org

SA-CONTRIB-2012-143 PRH Search - Cross Site Scripting (XSS)
by security-news＠drupal.org 19 Sep '12

19 Sep '12

View online: http://drupal.org/node/1789252 * Advisory ID: DRUPAL-SA-CONTRIB-2012-143 * Project: PRH Search [1] (third-party module) * Version: 7.x * Date: 2012-September-19 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- PRH Search provides an interface to search for association information for Finnish association using the PRH (Patentti- ja Rekisterihallitus) database. The module fails to sanitize data retrieved from an untrusted third party source, thereby exposing an arbitrary script injection vulnerability (XSS). This vulnerability is mitigated by the fact that an attacker must have either gained access to that third party source or use techniques such as DNS spoofing in order to inject malicious data. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * PRH Search 7.x-1.x versions prior to 7.x-1.1 Drupal core is not affected. If you do not use the contributed PRH Search [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the PRH Search module for Drupal 7.x, upgrade to PRH Search 7.x-1.1 [4] Also see the PRH Search [5] project page. -------- REPORTED BY --------------------------------------------------------- * Klaus Purer [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Antti Alamäki [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/prh_search [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/prh_search [4] http://drupal.org/node/1778778 [5] http://drupal.org/project/prh_search [6] http://drupal.org/user/262198 [7] http://drupal.org/user/155131 [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-142 - Spambot - Cross Site Scripting (XSS)
by security-news＠drupal.org 19 Sep '12

19 Sep '12

View online: http://drupal.org/node/1789242 * Advisory ID: DRUPAL-SA-CONTRIB-2012-142 * Project: Spambot [1] (third-party module) * Version: 6.x, 7.x * Date: 2012-September-19 * Security risk: Less critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Spambot module enables you to protect new user registrations from spammers using the database at stopforumspam.com. Spambot doesn't sufficiently sanitize API responses from stopforumspam.com when they are logged to the watchdog, allowing a potential XSS attack. This vulnerability is mitigated by the fact that only stopforumspam.com (or someone pretending to be stopforumspam.com) can exploit it. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Spambot 6.x-3.x versions prior to 6.x-3.2. * Spambot 7.x-1.x versions prior to 7.x-1.1. Drupal core is not affected. If you do not use the contributed Spambot [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Spambot module for Drupal 6.x, upgrade to Spambot 6.x-3.2 [4] * If you use the Spambot module for Drupal 7.x, upgrade to Spambot 7.x-1.1 [5] Also see the Spambot [6] project page. -------- REPORTED BY --------------------------------------------------------- * Jimmy Axenhus [7] -------- FIXED BY ------------------------------------------------------------ * Beng Tan [8], the module maintainer * Jimmy Axenhus [9] -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [10] of the Drupal Security Team * Ben Jeavons [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/spambot [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/spambot [4] http://drupal.org/node/1789084 [5] http://drupal.org/node/1789086 [6] http://drupal.org/project/spambot [7] http://drupal.org/user/565562 [8] http://drupal.org/user/132729 [9] http://drupal.org/user/565562 [10] http://drupal.org/user/36762 [11] http://drupal.org/user/91990 [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-139 - PDFThumb OS Injection
by security-news＠drupal.org 13 Sep '12

13 Sep '12

View online: http://drupal.org/node/1782580 * Advisory ID: DRUPAL-SA-CONTRIB-2012-139 * Project: PDFThumb [1] (third-party module) * Version: 7.x * Date: 2012-September-12 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: OS Injection -------- DESCRIPTION --------------------------------------------------------- PDFThumb module creates thumbnail images of PDF files. The module doesn't sufficiently escape user-entered values when executing commands on the server allowing an attacker to execute whatever commands are available to the web server user (e.g. www-data). This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Administer PDFThumb". CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * PDFThumb 7.x-1.x versions prior to 7.x-1.1 Drupal core is not affected. If you do not use the contributed PDFThumb [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the PDFThumb module for Drupal 7.x, upgrade to PDFThumb 7.x-1.1 [4] Also see the PDFThumb [5] project page. -------- REPORTED BY --------------------------------------------------------- * Matt Kleve [6] of the Drupal Security Team * mdespeuilles [7], the module maintainer -------- FIXED BY ------------------------------------------------------------ * Matt Kleve [8] of the Drupal Security Team * mdespeuilles [9], the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [10] of the Drupal Security Team * Matt Kleve [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/pdfthumb [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/pdfthumb [4] http://drupal.org/node/1776248 [5] http://drupal.org/project/pdfthumb [6] http://drupal.org/user/150473 [7] http://drupal.org/user/939504 [8] http://drupal.org/user/150473 [9] http://drupal.org/user/939504 [10] http://drupal.org/user/36762 [11] http://drupal.org/user/150473 [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-140 - Inf08 - Cross Site Scripting (XSS)
by security-news＠drupal.org 13 Sep '12

13 Sep '12

View online: http://drupal.org/node/1782686 * Advisory ID: DRUPAL-SA-CONTRIB-2012-140 * Project: Inf08 [1] (third-party module) * Version: 6.x * Date: 2012-September-12 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Inf08 is a valid XHTML 1.0 Strict / CSS 2.1 theme ported from the free CSS template. The theme contains an arbitrary script injection vulnerability (XSS) due to the fact that it fails to sanitize user supplied taxonomy vocabulary names before display. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer taxonomy". CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Inf08 6.x-1.x versions prior to 6.x-1.10. Drupal core is not affected. If you do not use the contributed Inf08 [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Inf08 theme for Drupal 6.x, upgrade to Inf08 6.x-1.10 [4] Also see the Inf08 [5] project page. -------- REPORTED BY --------------------------------------------------------- * Justin C. Klein Keane [6] -------- FIXED BY ------------------------------------------------------------ * kong [7], the theme 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/inf08 [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/inf08 [4] http://drupal.org/node/1782286 [5] http://drupal.org/project/inf08 [6] http://drupal.org/user/15344 [7] http://drupal.org/user/46601 [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-141 - Mass Contact - Access bypass
by security-news＠drupal.org 13 Sep '12

13 Sep '12

View online: http://drupal.org/node/1782832 * Advisory ID: DRUPAL-SA-CONTRIB-2012-141 * Project: Mass Contact [1] (third-party module) * Version: 6.x * Date: 2012-September-12 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module allows anyone with permission to send a single message to multiple users of a site, using its roles functionality. The module doesn't sufficiently check permissions after the form has been submitted. This vulnerability is mitigated by the fact that an attacker must use a tool of some kind (like the Tamper Data Firefox add-on) to intercept the form submission request in order to modify the settings. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Mass Contact 6.x-1.x versions prior to 6.x-1.2. Drupal core is not affected. If you do not use the contributed Mass Contact [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Mass Contact module for Drupal 6.x, upgrade to Mass Contact 6.x-1.2 [4] Also see the Mass Contact [5] project page. -------- REPORTED BY --------------------------------------------------------- * Michael Orlitzky [6] -------- FIXED BY ------------------------------------------------------------ * Michael Orlitzky [7] * Jason Flatt [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/mass_contact [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/mass_contact [4] http://drupal.org/node/1782766 [5] http://drupal.org/project/mass_contact [6] http://drupal.org/user/1731656 [7] http://drupal.org/user/1731656 [8] http://drupal.org/user/4649 [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-138 - Exposed Filter Data - Cross Site Scripting (XSS)
by security-news＠drupal.org 05 Sep '12

05 Sep '12

View online: http://drupal.org/node/1775582 * Advisory ID: DRUPAL-SA-CONTRIB-2012-138 * Project: Exposed Filter Data [1] (third-party module) * Version: 6.x * Date: 2012-September-05 * Security risk: Critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Exposed Filter Data facilitates displaying data posted to Views via an exposed filter. The module does not properly sanitize user-supplied data prior to output, leading to a Cross-Site Scripting (XSS) vulnerability. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Exposed Filter Data 6.x-1.x versions prior to 6.x-1.2. Drupal core is not affected. If you do not use the contributed Exposed Filter Data [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Exposed Filter Data module for Drupal 6.x, upgrade to Exposed Filter Data 6.x-1.2 [4]. * The 7.x-1.x branch is not vulnerable. If you use Exposed Filter Data for Drupal 7.x, there is nothing you need to do. Also see the Exposed Filter Data [5] project page. -------- REPORTED BY --------------------------------------------------------- * Joe Tsui [6] * ekes [7] -------- FIXED BY ------------------------------------------------------------ * Shushu Inbar [8], the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Michael Hess (mlhess [9]) of the Drupal Security Team * Ivo Van Geertruyen (mr.baileys [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/exposed_filter_data [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/exposed_filter_data [4] http://drupal.org/node/1774636 [5] http://drupal.org/project/exposed_filter_data [6] https://drupal.org/user/125025 [7] http://drupal.org/user/10083 [8] https://drupal.org/user/99513 [9] http://drupal.org/user/102818 [10] http://drupal.org/user/383424 [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-137 - Heartbeat - Cross Site Request Forgery (CSRF) in heartbeat_comments
by security-news＠drupal.org 05 Sep '12

05 Sep '12

View online: http://drupal.org/node/1775470 * Advisory ID: DRUPAL-SA-CONTRIB-2012-137 * Project: Heartbeat [1] (third-party module) * Version: 6.x, 7.x * Date: 2012-September-5 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- This module enables you to display activity for events on a site. The module doesn't sufficiently check the heartbeat comment post values making it possible for an attacker to cause a user to unknowingly make comments. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * heartbeat_comments 6.x-4.x versions prior to 6.x-4.11. * heartbeat_comments 7.x-1.x versions prior to 7.x-1.0. Drupal core is not affected. If you do not use the contributed Heartbeat [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the heartbeat_comments or shouts module for Drupal 6.x, upgrade to heartbeat 6.x-4.12 [4] * If you use the heartbeat_comments module for Drupal 7.x, upgrade to heartbeat 7.x-1.1 [5] Also see the Heartbeat [6] project page. -------- REPORTED BY --------------------------------------------------------- * Greg Knaddison [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Stalski [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [9] of the Drupal Security Team * Matt Chapman [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/heartbeat [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/heartbeat [4] http://drupal.org/node/1774140 [5] http://drupal.org/node/1774160 [6] http://drupal.org/project/heartbeat [7] http://drupal.org/user/36762 [8] http://drupal.org/user/322618 [9] http://drupal.org/user/36762 [10] http://drupal.org/user/143172 [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-136 - Apache Solr Search Autocomplete - Cross Site Scripting (XSS)
by security-news＠drupal.org 29 Aug '12

29 Aug '12

View online: http://drupal.org/node/1762734 * Advisory ID: DRUPAL-SA-CONTRIB-2012-136 * Project: Apache Solr Autocomplete [1] (third-party module) * Version: 6.x, 7.x * Date: 2012-August-29 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Apache Solr Search Autocomplete module enables you to add autocomplete capabilities to the search text field for the Apache Solr Search Integration module. The module doesn't sufficiently filter the autocomplete results sent back from the Drupal site, so under the scenario where someone provided a URL with a specially-crafted search string embedded in it, the attacker could have a user execute arbitrary Javascript when clicking or focusing on the autocomplete text field. This vulnerability is mitigated by the fact that the attacked user must click or otherwise give focus to the text widget to have the Javascript activate. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Apache Solr Autocomplete 6.x-1.x versions prior to 6.x-1.4. * Apache Solr Autocomplete 7.x-1.x versions prior to 7.x-1.3. Drupal core is not affected. If you do not use the contributed Apache Solr Autocomplete [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version. * If you use the Apache Solr Autocomplete module for Drupal 6.x, upgrade to Apache Solr Autocomplete 6.x-1.4 [4] * If you use the Apache Solr Autocomplete module for Drupal 7.x, upgrade to Apache Solr Autocomplete 7.x-1.3 [5] Also see the Apache Solr Autocomplete [6] project page. -------- REPORTED BY --------------------------------------------------------- * drupaledmonk [7] -------- FIXED BY ------------------------------------------------------------ * Alejandro Garza [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/apachesolr_autocomplete [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/apachesolr_autocomplete [4] http://drupal.org/node/1762684 [5] http://drupal.org/node/1762686 [6] http://drupal.org/project/apachesolr_autocomplete [7] http://drupal.org/user/263391 [8] http://drupal.org/user/153120 [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-135 - CAPTCHA - Insufficient anti-automation prevention
by security-news＠drupal.org 29 Aug '12

29 Aug '12

View online: http://drupal.org/node/1762496 * Advisory ID: DRUPAL-SA-CONTRIB-2012-135 * Project: CAPTCHA [1] (third-party module) * Version: 6.x * Date: 2011-August-29 * Security risk: Less critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to protect website forms using a CAPTCHA. A CAPTCHA is a test which attempts to differentiate between a human and an automated bot or script. The module doesn't ensure that test submissions have a single-use unique token. This means that web robots could reuse a single successful submission multiple times, reducing the effectiveness of the protection. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * CAPTCHA 6.x-2.x versions prior to 6.x-2.3 Drupal core is not affected. If you do not use the contributed CAPTCHA [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the CAPTCHA module for Drupal 6.x, upgrade to CAPTCHA 6.x-2.3 [4] or greater Also see the CAPTCHA [5] project page. -------- REPORTED BY --------------------------------------------------------- * LeeSai [6] * MustLive -------- FIXED BY ------------------------------------------------------------ * Stefaan Lippens [7] a CAPTCHA module maintainer -------- COORDINATED BY ------------------------------------------------------ * Owen Barton [8] of the Drupal Security Team * 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/captcha [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/captcha [4] http://drupal.org/node/967244 [5] http://drupal.org/project/captcha [6] http://drupal.org/user/680166 [7] http://drupal.org/user/41478 [8] http://drupal.org/user/19668 [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-134 - Views - Privilege Escalation
by security-news＠drupal.org 29 Aug '12

29 Aug '12

View online: http://drupal.org/node/1762492 * Advisory ID: DRUPAL-SA-CONTRIB-2012-134 * Project: (third-party module) * Version: 6.x * Date: 2012-August-29 * Security risk: Critical [1] * Exploitable from: Remote * Vulnerability: Privilege escalation -------- DESCRIPTION --------------------------------------------------------- The Views module provides a flexible method for Drupal site designers to control how lists and tables of content, users, taxonomy terms and other data are presented. The module incorrectly modifies the global user object in some situations when a view has a uid argument and performs validation on that argument. This vulnerability is mitigated by the fact that it only affects sites with more roles than default where a role with a low role ID has more privileges than other roles on the site and where untrusted (i.e. potentially malicious) users are granted several of those roles. CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Views 6.x-2.x versions prior to 6.x-2.16. Drupal core is not affected. If you do not use the contributed module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Views module for Drupal 6.x, upgrade to Views 6.x-2.16 [2] Also see the project page. -------- REPORTED BY --------------------------------------------------------- * Derek Wright [3] of the Drupal Security Team * John Preto [4] -------- FIXED BY ------------------------------------------------------------ * Derek Wright [5] one of module maintainers, also of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [6] 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 [7]. Learn more about the Drupal Security team and their policies [8], writing secure code for Drupal [9], and securing your site [10]. [1] http://drupal.org/security-team/risk-levels [2] http://drupal.org/node/1341504 [3] http://drupal.org/user/46549 [4] http://drupal.org/user/356949 [5] http://drupal.org/user/46549 [6] http://drupal.org/user/36762 [7] http://drupal.org/contact [8] http://drupal.org/security-team [9] http://drupal.org/writing-secure-code [10] http://drupal.org/security/secure-configuration

1 0