- Security-news - lists.drupal.org

SA-CONTRIB-2009-012 - Printer, e-mail and PDF versions - Unrestricted e-mailing (spam)
by security-news＠drupal.org 18 Mar '09

18 Mar '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-012 * Project: Printer, e-mail and PDF versions (third-party module) * Versions: 5.x, 6.x * Date: 2009 March 18 * Security risk: Highly Critical * Exploitable from: Remote * Vulnerability: Unrestricted e-mailing (spam) The "Send by e-mail" module, part of the "Printer, e-mail and PDF versions" project, allows users to send e-mail messages while viewing content on the site. This module was found to have multiple vulnerabilities. -------- UNRESTRICTED E-MAILING (SPAM) --------------------------------------- Due to improper use of Drupal's flood control API, it is possible for spammers or spambots to send an unlimited numbers of e-mails using the "Send by e-mail" module. This vulnerability is very similar to the recent vulnerability found in the Forward module and reported in SA-CONTRIB-2009-009 [1]. The security team has received reports of this vulnerability being actively exploited on production sites using the Forward module. In addition, when sending out e-mails in HTML format, some content is not properly filtered, allowing malicious users to inject arbitrary HTML and script code into these e-mails. -------- VERSIONS AFFECTED --------------------------------------------------- * Versions of "Printer, e-mail and PDF versions" 5.x prior to 5.x-4.4 * Versions of "Printer, e-mail and PDF versions" 6.x prior to 6.x-1.4 Drupal core is not affected. If you do not use the contributed "Printer, e-mail and PDF versions" module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use "Printer, e-mail and PDF versions" 5.x upgrade to Printer, e-mail and PDF versions 5.x-4.4 [2] * If you use "Printer, e-mail and PDF versions" 6.x upgrade to Printer, e-mail and PDF versions 6.x-1.4 [3] -------- REPORTED BY --------------------------------------------------------- João Ventura, the "Printer, e-mail and PDF versions" project maintainer -------- FIXED BY ------------------------------------------------------------ João Ventura, with assistance from James Gilliand and David Rothstein of the Drupal security team -------- CONTACT ------------------------------------------------------------- The security contact for Drupal can be reached at security at drupal.org or via the form at http://drupal.org/contact [4]. [1] http://drupal.org/node/398564 [2] http://drupal.org/node/406512 [3] http://drupal.org/node/406522 [4] http://drupal.org/contact

1 0

SA-CONTRIB-2009-013 CCK - Cross site scripting
by security-news＠drupal.org 18 Mar '09

18 Mar '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-013 * Project: Content Construction Kit (third-party module) * Version: 6.x * Date: 2009 March 18 * Security risk: Moderately critical * Exploitable from: Remote * Vulnerability: Cross-site scripting (XSS) -------- DESCRIPTION --------------------------------------------------------- The Node reference and User reference sub-modules, which are part of the Content Construction Kit (CCK) project, lets administrators define node fields that are references to other nodes or to users. When displaying a node edit form, the titles of candidate referenced nodes or names of candidate referenced users are not properly filtered, allowing malicious users to inject arbitrary code on those pages. Such a cross site scripting [1] (XSS) attack may lead to a malicious user gaining full administrative access. -------- VERSIONS AFFECTED --------------------------------------------------- * Versions of CCK for Drupal 6.x prior to 6.x-2.2 Drupal core is not affected. If you do not use the Node reference or User reference sub-modules of the contributed Content Construction Kit (CCK) project, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use CCK for Drupal 6.x upgrade to CCK 6.x-2.2 [2] See also the Content Construction Kit (CCK) project page [3]. -------- REPORTED BY --------------------------------------------------------- Yves Chedemois (yched [4]). -------- FIXED BY ------------------------------------------------------------ Yves Chedemois (yched [5]). -------- 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/406534 [3] http://drupal.org/project/cck [4] http://drupal.org/user/39567 [5] http://drupal.org/user/39567

1 0

SA-CONTRIB-2009-011 Tasklist - SQL injection and Cross site scripting
by security-news＠drupal.org 18 Mar '09

18 Mar '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-011 * Project: Tasklist (third-party module) * Version: 5.x * Date: 2009 March 18 * Security risk: Highly critical * Exploitable from: Remote * Vulnerability: SQL injection and Cross-site scripting (XSS) -------- DESCRIPTION --------------------------------------------------------- Tasklist does not properly use the Drupal database API and inserts values from the URL directly into queries. This can be exploited to perform SQL Injection attacks [1]. These attacks may lead to a malicious user gaining full administrator access. In addition, Tasklist allows users to add CSS to pages. This CSS was not restricted or filtered, allowing malicious users to insert arbitrary HTML and script code into these pages. Such a cross site scripting [2] (XSS) attack may also lead to a malicious user gaining full administrative access. -------- VERSIONS AFFECTED --------------------------------------------------- * Tasklist 5.x-1.x prior to 5.x-1.3 * Tasklist 5.x-2.x prior to 5.x-2.0-alpha1 Drupal core is not affected. If you do not use the contributed Tasklist module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use Tasklist 5.x-1.x upgrade to Tasklist 5.x-1.3 [3] * If you use Tasklist 5.x-2.x (development snapshots) upgrade to Tasklist 5.x-2.0-alpha1 [4] Tasklist for Drupal 4.7.x is no longer supported. See also the Tasklist project page [5]. -------- REPORTED BY --------------------------------------------------------- John Morahan of the Drupal Security Team [6]. -------- FIXED BY ------------------------------------------------------------ Stéphane Corlosquet of the Drupal Security Team [7]. -------- CONTACT ------------------------------------------------------------- The security contact for Drupal can be reached at security at drupal.org or via the form at http://drupal.org/contact [8]. [1] http://en.wikipedia.org/wiki/Sql_injection [2] http://en.wikipedia.org/wiki/Cross-site_scripting [3] http://drupal.org/node/406482 [4] http://drupal.org/node/406488 [5] http://drupal.org/project/tasks [6] http://drupal.org/security-team [7] http://drupal.org/security-team [8] http://drupal.org/contact

1 0

SA-CONTRIB-2009-010 Plus 1 - Cross-site request forgery
by security-news＠drupal.org 18 Mar '09

18 Mar '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-010 * Project: Plus 1 (third-party module) * Version: 6.x * Date: 2009 March 18 * Security risk: Not critical * Exploitable from: Remote * Vulnerability: Cross-site request forgery (CSRF) -------- DESCRIPTION --------------------------------------------------------- The Plus 1 module provides a voting widget for content that records votes using Ajax. The URL for voting is vulnerable to cross-site request forgeries (CSRF [1]) making it possible for users to unknowingly vote for content. -------- VERSIONS AFFECTED --------------------------------------------------- * Versions of Plus 1 prior to 6.x-2.6 Drupal core is not affected. If you do not use the contributed Plus 1 module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use Plus 1 for Drupal 6.x upgrade to Plus 1 6.x-2.6 [2] See also the Plus 1 project page [3]. -------- REPORTED BY --------------------------------------------------------- Greg Knaddison of the Drupal security team. -------- FIXED BY ------------------------------------------------------------ Greg Knaddison, Ben Jeavons, Neil Drumm, and Caroline Schnapp. -------- CONTACT ------------------------------------------------------------- The security contact for Drupal can be reached at security at drupal.org or via the form at http://drupal.org/contact [4]. [1] http://en.wikipedia.org/wiki/Csrf [2] http://drupal.org/node/405672 [3] http://drupal.org/project/plus1 [4] http://drupal.org/contact

1 0

New pages and RSS feeds for security announcements
by security-news＠drupal.org 18 Mar '09

18 Mar '09

-------- SEPARATE SECURITY ANNOUNCEMENTS BY TYPE ----------------------------- To make the impact of different security advisories and announcements easier to see, they are now separated by type. Drupal core security advisories: http://drupal.org/security [1] RSS feed for Drupal core: http://drupal.org/security/rss.xml [2] Contributed project security advisories: http://drupal.org/security/contrib [3] RSS feed for contributed projects: http://drupal.org/security/contrib/rss.xml [4] Public service announcements: http://drupal.org/security/psa [5] RSS feed for announcements: http://drupal.org/security/psa/rss.xml [6] /We encourage those using RSS readers to track security-related developments to subscribe to all three of these feeds./ All posts to each of these three forums will still be sent to the one security announcements e-mail list. To subscribe to that e-mail list, once logged in, go to your user profile page and subscribe to the security newsletter on the Edit » My newsletters tab. All future public service announcements will only be posted to the /Public service announcements/ page and feed. -------- BACKGROUND ON THE CHANGES ------------------------------------------- At Drupalcon in Washington, D.C. earlier this month, members of the Security team held a "Birds of a Feather" session to discusses various topics including improvements to our process of communicating with the public. One outcome of this meeting was that we decided to more clearly differentiate among security advisories for Drupal core (which affect all users) as opposed to security advisories for contributed projects (which are often used by only tens of sites). In addition, the security team has on occasion issued announcements (such as this one), which were previously mixed in with actual security advisories. Since the Drupal 6.x upgrade of http://drupal.org [7], newsletter postings have been managed using forums. The security team has thus split security-related postings among three forums under http://drupal.org/forum/1188 [8]. All past and new advisories and announcements and their feeds can be viewed (via tabs) on http://drupal.org/security [9]. -------- CONTACT ------------------------------------------------------------- The security team for Drupal can be reached at security at drupal.org or via the form at http://drupal.org/contact [10]. [1] http://drupal.org/security [2] http://drupal.org/security/rss.xml [3] http://drupal.org/security/contrib [4] http://drupal.org/security/contrib/rss.xml [5] http://drupal.org/security/psa [6] http://drupal.org/security/psa/rss.xml [7] http://drupal.org [8] http://drupal.org/forum/1188 [9] http://drupal.org/security [10] http://drupal.org/contact

1 0

SA-CONTRIB-2009-009 Forward module can be used as a spam relay
by security-news＠drupal.org 11 Mar '09

11 Mar '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-009 * Project: Forward * Versions: 5.x, 6.x * Date: 2009-March-11 * Security risk: Highly Critical * Exploitable from: Remote * Vulnerability: Unrestricted e-mailing (spam) -------- DESCRIPTION --------------------------------------------------------- This vulnerability allows spammers or spambots to use sites with the forward module installed to send nearly unlimited e-mail. Due to improper use of Drupal's flood control API, it is possible for one user to send an unlimited numbers of mails using the forward module. *Important note*: the security team has received reports of this vulnerability being actively exploited on production sites, and this advisory should be considered urgent. -------- VERSIONS AFFECTED --------------------------------------------------- * Drupal 5.x before version 5.x-1.19 * Drupal 6.x development snapshots Drupal core is not affected. If you do not use the contributed Forward module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you are running Drupal 5.x then upgrade to Forward 5.x-1.19 [1]. * If you are running a Drupal 6.x development snapshot from prior to March 11, 2009 then upgrade to 6.x-1.0 [2] If you are unable to upgrade immediately, you should disable the Forward module as a work-around. -------- REPORTED BY --------------------------------------------------------- Helmut Debes Dylan Wilder-Tack Owen Barton -------- 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://ftp.drupal.org/files/projects/forward-5.x-1.19.tar.gz [2] http://ftp.drupal.org/files/projects/forward-6.x-1.0.tar.gz

1 0

SA-CONTRIB-2009-008 - Taxonomy Theme - Cross site scripting
by security-news＠drupal.org 28 Feb '09

28 Feb '09

* Advisory ID: DRUPAL-SA-CONTRIB-2009-008 * Project: Taxonomy Theme (third-party module) * Version: 5.x * Date: 2009 February 28 * Security risk: Less critical * Exploitable from: Remote * Vulnerability: Cross-site scripting (XSS) -------- DESCRIPTION --------------------------------------------------------- The Taxonomy Theme module allows a website adminstrator to change the theme of a given content item based on taxonomy, vocabulary or content type. It does not properly sanitize user-supplied data on a number of places. This allows users with the "administer taxonomy" permission, or, when tagging is enabled, the ability to submit content, to insert arbitrary HTML and scripts into certain pages. Such a cross site scripting [1] (XSS) attack against sufficiently privileged users may lead to adminstrator access to the site. -------- VERSIONS AFFECTED --------------------------------------------------- * Versions of Taxonomy Theme for Drupal 5.x prior to 5.x-1.2 Drupal core is not affected. If you do not use the contributed Taxonomy Theme module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use Taxonomy Theme for Drupal 5.x upgrade to Taxonomy Theme 5.x-1.2 [2] See also the Taxonomy Theme project page [3]. -------- REPORTED BY --------------------------------------------------------- This vulnerability was publicly disclosed. -------- 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/386942 [3] http://drupal.org/project/taxonomy_theme

1 0

SA-CORE-2009-004 - Local file inclusion on Windows
by security-news＠drupal.org 26 Feb '09

26 Feb '09

* Advisory ID: DRUPAL-SA-CORE-2009-004 * Project: Drupal core * Versions: 5.x * Date: 2009-February-25 * Security risk: Highly Critical * Exploitable from: Remote * Vulnerability: Local file inclusion on Windows * Reference: SA-CORE-2009-003 [1] (6.x) -------- DESCRIPTION --------------------------------------------------------- This vulnerability exists on Windows, regardless of the type of webserver (Apache, IIS) used. The Drupal theme system takes URL arguments into account when selecting a template file to use for page rendering. While doing so, it doesn't take into account how Windows arrives at a canonicalized path. This enables malicious users to include files, readable by the webserver and located on the same volume as Drupal, and to execute PHP contained within those files. For example: If a site has uploads enabled, an attacker may upload a file containing PHP code and cause it to be included on a subsequent request by manipulating the URL used to access the site. *Important note*: An attacker may also be able to inject PHP code into webserver logs and subsequently include the log file, leading to code execution even if no upload functionality is enabled on the site. -------- VERSIONS AFFECTED --------------------------------------------------- * Drupal 5.x before version 5.16 -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you are running Drupal 5.x then upgrade to Drupal 5.16 [2]. 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. The patch fixes the security vulnerability, but does not contain other fixes which were released in Drupal 5.16. * To patch Drupal 5.15 use SA-CORE-2009-004-5.15.patch [3]. -------- REPORTED BY --------------------------------------------------------- Bogdan Calin (www.acunetix.com) -------- 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/383724 [2] http://ftp.drupal.org/files/projects/drupal-5.16.tar.gz [3] http://drupal.org/files/sa-core-2009-004/SA-CORE-2009-004-5.15.patch

1 0

SA-CORE-2009-003 - Local file inclusion on Windows
by security-news＠drupal.org 25 Feb '09

25 Feb '09

* Advisory ID: DRUPAL-SA-CORE-2009-003 * Project: Drupal core * Versions: 6.x * Date: 2009-February-25 * Security risk: Highly Critical * Exploitable from: Remote * Vulnerability: Local file inclusion on Windows -------- DESCRIPTION --------------------------------------------------------- This vulnerability exists on Windows, regardless of the type of webserver (Apache, IIS) used. The Drupal theme system takes URL arguments into account when selecting a template file to use for page rendering. While doing so, it doesn't take into account how Windows arrives at a canonicalized path. This enables malicious users to include files, readable by the webserver and located on the same volume as Drupal, and to execute PHP contained within those files. For example: If a site has uploads enabled, an attacker may upload a file containing PHP code and cause it to be included on a subsequent request by manipulating the URL used to access the site. *Important note*: An attacker may also be able to inject PHP code into webserver logs and subsequently include the log file, leading to code execution even if no upload functionality is enabled on the site. -------- VERSIONS AFFECTED --------------------------------------------------- * Drupal 6.x before version 6.10 -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you are running Drupal 6.x then upgrade to Drupal 6.10 [1]. 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. The patch fixes the security vulnerability, but does not contain other fixes which were released in Drupal 6.10. * To patch Drupal 6.9 use SA-CORE-2009-003-6.9.patch [2]. -------- REPORTED BY --------------------------------------------------------- Bogdan Calin (www.acunetix.com) -------- 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://ftp.drupal.org/files/projects/drupal-6.10.tar.gz [2] http://drupal.org/files/sa-core-2009-003/SA-CORE-2009-003-6.9.patch

1 0

Notification of mailing list testing
by security-news＠drupal.org 25 Feb '09

25 Feb '09

Dear Security Newsletter subscribers, We have recently performed testing on the subscription infrastructure. As a result you might have received a message that you were unsubscribed from the security newsletter. There is no action required on your part, you are still subscribed. Many people tried to verify their subscription status which overloaded our mail servers. Therefore the newsletter subscriptions page is temporarily disabled. Receiving this mail is proof you are on the security mailing list, so no need to check. Sending these messages was unintentional. We apologize for the inconvenience. Regards, The Drupal.org infrastructure team

1 0