Security advisories https://drupal.org/security en SA-CORE-2013-002 - Drupal core - Denial of service https://drupal.org/SA-CORE-2013-002 <ul><li>Advisory ID: DRUPAL-SA-CORE-2013-002</li> <li>Project: <a href="http://drupal.org/project/drupal" rel="nofollow">Drupal core</a></li> <li>Version: 7.x</li> <li>Date: 2013-February-20</li> <li>Security risk: <a href="http://drupal.org/security-team/risk-levels" rel="nofollow">Critical</a></li> <li>Exploitable from: Remote</li> <li>Vulnerability: Denial of service</li> </ul><h2>Description</h2> <p>Drupal core's Image module allows for the on-demand generation of image derivatives. This capability can be abused by requesting a large number of new derivatives which can fill up the server disk space, and which can cause a very high CPU load. Either of these effects may lead to the site becoming unavailable or unresponsive.</p> <p>Please see the <a href="http://drupal.org/drupal-7.20-release-notes" rel="nofollow">Drupal 7.20 release notes</a> for important notes about the changes which were made to fix this issue, since some sites will require extra testing and care when deploying this Drupal core release.</p> <p><a name="cve-identifiers-issued" id="cve-identifiers-issued" rel="nofollow"></a></p> <h2>CVE identifier(s) issued</h2> <ul><li>CVE-2013-0316</li> </ul><h2>Versions affected</h2> <ul><li>Drupal core 7.x versions prior to 7.20.</li> </ul><h2>Solution</h2> <p>Install the latest version:</p> <ul><li>If you use Drupal 7.x, upgrade to <a href="http://drupal.org/drupal-7.20-release-notes" rel="nofollow">Drupal core 7.20</a>.</li> </ul><p>Also see the <a href="http://drupal.org/project/drupal" rel="nofollow">Drupal core</a> project page.</p> <h2>Reported by</h2> <ul><li><a href="http://drupal.org/user/2663" rel="nofollow">Bèr Kessels</a></li> <li><a href="http://drupal.org/user/2274988" rel="nofollow">aBrookland</a></li> <li><a href="http://drupal.org/user/10297" rel="nofollow">Chad Fennell</a></li> </ul><h2>Fixed by</h2> <ul><li><a href="http://drupal.org/user/22211" rel="nofollow">Damien Tournoud</a> of the Drupal Security Team</li> <li><a href="http://drupal.org/user/49851" rel="nofollow">Peter Wolanin</a> of the Drupal Security Team</li> <li><a href="http://drupal.org/user/124982" rel="nofollow">David Rothstein</a> of the Drupal Security Team</li> <li><a href="http://drupal.org/user/17943" rel="nofollow">Heine Deelstra</a> of the Drupal Security Team</li> <li><a href="http://drupal.org/user/2663" rel="nofollow">Bèr Kessels</a></li> </ul><h2>Coordinated by</h2> <ul><li><a href="http://drupal.org/user/124982" rel="nofollow">David Rothstein</a> of the Drupal Security Team</li> <li><a href="http://drupal.org/user/52142" rel="nofollow">Stéphane Corlosquet</a> of the Drupal Security Team</li> <li><a href="http://drupal.org/user/49851" rel="nofollow">Peter Wolanin</a> of the Drupal Security Team</li> <li><a href="http://drupal.org/user/36762" rel="nofollow">Greg Knaddison</a> of the Drupal Security Team</li> </ul><h2>Contact and More Information</h2> <p>The Drupal security team can be reached at security at drupal.org or via the contact form at <a href="http://drupal.org/contact" rel="nofollow">http://drupal.org/contact</a>.</p> <p>Learn more about <a href="http://drupal.org/security-team" rel="nofollow">the Drupal Security team and their policies</a>, <a href="http://drupal.org/writing-secure-code" rel="nofollow">writing secure code for Drupal</a>, and <a href="http://drupal.org/security/secure-configuration" rel="nofollow">securing your site</a>.</p> Security advisories for Drupal core Drupal 7.x Wed, 20 Feb 2013 20:50:06 +0000 Drupal Security Team 1922770 at https://drupal.org SA-CORE-2013-001 - Drupal core - Multiple vulnerabilities https://drupal.org/SA-CORE-2013-001 <ul> <li>Advisory ID: DRUPAL-SA-CORE-2013-001</li> <li>Project: <a href="http://drupal.org/project/drupal">Drupal core</a></li> <li>Version: 6.x, 7.x</li> <li>Date: 2013-January-16</li> <li>Security risk: <a href="http://drupal.org/security-team/risk-levels">Highly critical</a></li> <li>Exploitable from: Remote</li> <li>Vulnerability: Cross Site Scripting, Access bypass</li> </ul> <!--break--><!--break--><h2>Description</h2> <p>Multiple vulnerabilities were fixed in the supported Drupal core versions 6 and 7.</p> <h3>Cross-site scripting (Various core and contributed modules - Drupal 6 and 7)</h3> <p>A reflected cross-site scripting vulnerability (XSS) was identified in certain Drupal JavaScript functions that pass unexpected user input into jQuery causing it to insert HTML into the page when the intended behavior is to select DOM elements. Multiple core and contributed modules are affected by this issue.</p> <p>jQuery versions 1.6.3 and higher provide protection against common forms of this problem; thus, the vulnerability is mitigated if your site has upgraded to a recent version of jQuery. However, the versions of jQuery that are shipped with Drupal 6 and Drupal 7 core do not contain this protection.</p> <p>Although the fix added to Drupal as part of this security release prevents the most common forms of this issue in the same way as newer versions of jQuery do, developers should be aware that passing untrusted user input directly to jQuery functions such as jQuery() and $() is unsafe and should be avoided.</p> <p>CVE: CVE-2013-0244 (a CVE was also <a href="http://www.openwall.com/lists/oss-security/2013/01/31/3">separately issued</a> for jQuery)</p> <h3>Access bypass (Book module printer friendly version - Drupal 6 and 7)</h3> <p>A vulnerability was identified that exposes the title or, in some cases, the content of nodes that the user should not have access to.</p> <p>This vulnerability is mitigated by the fact that the bypass is only accessible to users who already have the 'access printer-friendly version' permission (which is not granted to Anonymous or Authenticated users by default) and it only affects nodes that are part of a book outline.</p> <p>CVE: CVE-2013-0245</p> <h3>Access bypass (Image module - Drupal 7)</h3> <p>Drupal core provides the ability to have private files, including images. A vulnerability was identified in which derivative images (which Drupal automatically creates from these images based on "image styles" and which may differ, for example, in size or saturation) did not always receive the same protection. Under some circumstances, this would allow users to access image derivatives for images they should not be able to view.</p> <p>This vulnerability is mitigated by the fact that it only affects sites which use the Image module and which store images in a private file system.</p> <p>CVE: CVE-2013-0246</p> <p><a name="cve-identifiers-issued" id="cve-identifiers-issued" rel="nofollow"></a></p> <h2>CVE identifier(s) issued</h2> <ul> <li>CVE-2013-0244</li> <li>CVE-2013-0245</li> <li>CVE-2013-0246</li> </ul> <h2>Versions affected</h2> <ul> <li>Drupal core 6.x versions prior to 6.28.</li> <li>Drupal core 7.x versions prior to 7.19.</li> </ul> <h2>Solution</h2> <p>Install the latest version:</p> <ul> <li>If you use Drupal 6.x, upgrade to <a href="http://drupal.org/drupal-6.28-release-notes">Drupal core 6.28</a>.</li> <li>If you use Drupal 7.x, upgrade to <a href="http://drupal.org/drupal-7.19-release-notes">Drupal core 7.19</a>.</li> </ul> <p>Also see the <a href="http://drupal.org/project/drupal">Drupal core</a> project page.</p> <h2>Reported by</h2> <ul> <li>The cross-site scripting issue in various Drupal core and contributed modules was reported by t.ashula, and by <a href="http://drupal.org/user/124982">David Rothstein</a> of the Drupal Security Team.</li> <li>The access bypass issue in the Book module was reported by <a href="http://drupal.org/user/1924632">Mark Lindsey</a>.</li> <li>The access bypass issue in the Drupal 7 Image module was reported by <a href="http://drupal.org/user/1605796">Kressin Roger</a>, <a href="http://drupal.org/user/204187">Christian Johansson</a>, <a href="http://drupal.org/user/855656">Anders Olsson</a> and <a href="http://drupal.org/user/245825">saschadrupal</a>.</li> </ul> <h2>Fixed by</h2> <ul> <li>The cross-site scripting issue in various Drupal core and contributed modules was fixed by t.ashula, <a href="http://drupal.org/user/598310">Théodore Biadala</a>, <a href="http://drupal.org/user/172987">Katherine Bailey</a>, <a href="http://drupal.org/user/264148">Steve De Jonghe</a> and <a href="http://drupal.org/user/748566">J. Renée Beach</a>, and by <a href="http://drupal.org/user/96647">Dylan Tack</a>, <a href="http://drupal.org/user/36762">Greg Knaddison</a>, <a href="http://drupal.org/user/124982">David Rothstein</a> and <a href="http://drupal.org/user/22211">Damien Tournoud</a> of the Drupal Security Team.</li> <li>The access bypass issue in the Book module was fixed by <a href="http://drupal.org/user/1924632">Mark Lindsey</a>, and by <a href="http://drupal.org/user/426416">Fox</a>, <a href="http://drupal.org/user/124982">David Rothstein</a> and <a href="http://drupal.org/user/49851">Peter Wolanin</a> of the Drupal Security Team.</li> <li>The access bypass issue in the Drupal 7 Image module was fixed by <a href="http://drupal.org/user/17943">Heine Deelstra</a> of the Drupal Security Team, and by <a href="http://drupal.org/user/855656">Anders Olsson</a>.</li> </ul> <h2>Coordinated by</h2> <ul> <li><a href="http://drupal.org/user/124982">David Rothstein</a>, <a href="http://drupal.org/user/4166">Gábor Hojtsy</a>, <a href="http://drupal.org/user/52142">Stéphane Corlosquet</a>, <a href="http://drupal.org/user/36762">Greg Knaddison</a>, <a href="http://drupal.org/user/17943">Heine Deelstra</a> and <a href="http://drupal.org/user/49851">Peter Wolanin</a> of the Drupal Security Team</li> <li><a href="http://drupal.org/user/148199">Jeremy Thorson</a> of the QA/Testing Infrastructure Team</li> </ul> <h2>Contact and More Information</h2> <p>The Drupal security team can be reached at security at drupal.org or via the contact form at <a href="http://drupal.org/contact">http://drupal.org/contact</a>.</p> <p>Learn more about <a href="http://drupal.org/security-team">the Drupal Security team and their policies</a>, <a href="http://drupal.org/writing-secure-code">writing secure code for Drupal</a>, and <a href="http://drupal.org/security/secure-configuration">securing your site</a>.</p> Security advisories for Drupal core Drupal 6.x Drupal 7.x Wed, 16 Jan 2013 22:07:10 +0000 Drupal Security Team 1890648 at https://drupal.org SA-CORE-2012-004 - Drupal core - Multiple vulnerabilities https://drupal.org/SA-CORE-2012-004 <ul> <li>Advisory ID: DRUPAL-SA-CORE-2012-004</li> <li>Project: <a href="http://drupal.org/project/drupal">Drupal core</a></li> <li>Version: 6.x, 7.x</li> <li>Date: 2012-December-19</li> <li>Security risk: <a href="http://drupal.org/security-team/risk-levels">Moderately critical</a></li> <li>Exploitable from: Remote</li> <li>Vulnerability: Access bypass, Arbitrary PHP code execution</li> </ul> <!--break--><!--break--><h2>Description</h2> <p>Multiple vulnerabilities were fixed in the supported Drupal core versions 6 and 7.</p> <h3>Access bypass (User module search - Drupal 6 and 7)</h3> <p>A vulnerability was identified that allows blocked users to appear in user search results, even when the search results are viewed by unprivileged users.</p> <p>This vulnerability is mitigated by the fact that the default Drupal core user search results only display usernames (and <a href="http://drupal.org/node/1004778">disclosure of usernames is not considered a security vulnerability</a>). However, since modules or themes may override the search results to display more information from each user's profile, this could result in additional information about blocked users being disclosed on some sites.</p> <h3>Access bypass (Upload module - Drupal 6)</h3> <p>A vulnerability was identified that allows information about uploaded files to be displayed in RSS feeds and search results to users that do not have the "view uploaded files" permission.</p> <p>This issue affects Drupal 6 only.</p> <h3>Arbitrary PHP code execution (File upload modules - Drupal 6 and 7)</h3> <p>Drupal core's file upload feature blocks the upload of many files that can be executed on the server by munging the filename. A malicious user could name a file in a manner that bypasses this munging of the filename in Drupal's input validation. </p> <p>This vulnerability is mitigated by several factors: The attacker would need the permission to upload a file to the server. Certain combinations of PHP and filesystems are not vulnerable to this issue, though we did not perform an exhaustive review of the supported PHP versions. Finally: the server would need to allow execution of files in the uploads directory. Drupal core has protected against this with a .htaccess file protection in place from <a href="http://drupal.org/node/65409">SA-2006-006 - Drupal Core - Execution of arbitrary files in certain Apache configurations</a>. Users of IIS should consider <a href="http://drupal.org/node/1543392">updating their web.config</a>. Users of Nginx should confirm that only the index.php and other known good scripts are executable. Users of other webservers should review their configuration to ensure the goals are achieved in some other way.</p> <p><a name="cve-identifiers-issued" id="cve-identifiers-issued" rel="nofollow"></a></p> <h2>CVE identifier(s) issued</h2> <ul> <li>Access bypass (User module search - Drupal 6 and 7): <strong>CVE-2012-5651</strong></li> <li>Access bypass (Upload module - Drupal 6): <strong>CVE-2012-5652</strong></li> <li>Arbitrary PHP code execution (File upload modules - Drupal 6 and 7): <strong>CVE-2012-5653</strong></li> </ul> <h2>Versions affected</h2> <ul> <li>Drupal core 6.x versions prior to 6.27.</li> <li>Drupal core 7.x versions prior to 7.18.</li> </ul> <h2>Solution</h2> <p>Install the latest version:</p> <ul> <li>If you use Drupal 6.x, upgrade to <a href="http://drupal.org/drupal-6.27-release-notes">Drupal core 6.27</a>.</li> <li>If you use Drupal 7.x, upgrade to <a href="http://drupal.org/drupal-7.18-release-notes">Drupal core 7.18</a>.</li> </ul> <p>Also see the <a href="http://drupal.org/project/drupal">Drupal core</a> project page.</p> <h2>Reported by</h2> <ul> <li>The access bypass issue in the User module search results was reported by <a href="http://drupal.org/user/46549">Derek Wright</a> of the Drupal Security Team.</li> <li>The access bypass issue in the Drupal 6 Upload module was reported by <a href="http://drupal.org/user/151544">Simon Rycroft</a>, and by <a href="http://drupal.org/user/22211">Damien Tournoud</a> of the Drupal Security Team.</li> <li>The arbitrary code execution issue was reported by <a href="http://drupal.org/user/181407">Amit Asaravala</a>.</li> </ul> <h2>Fixed by</h2> <ul> <li>The access bypass issue in the User module search results was fixed by <a href="http://drupal.org/user/46549">Derek Wright</a>, <a href="http://drupal.org/user/383424">Ivo Van Geertruyen</a>, <a href="http://drupal.org/user/49851">Peter Wolanin</a>, and <a href="http://drupal.org/user/124982">David Rothstein</a>, all members of the Drupal Security Team.</li> <li>The access bypass issue in the Drupal 6 Upload module was fixed by <a href="http://drupal.org/user/400288">Michaël Dupont</a>, and by <a href="http://drupal.org/user/426416">Fox</a> and <a href="http://drupal.org/user/124982">David Rothstein</a> of the Drupal Security Team.</li> <li>The arbitrary code execution issue was fixed by <a href="http://drupal.org/user/35821">Nathan Haug</a> and <a href="http://drupal.org/user/302225">Justin Klein-Keane</a>, and by <a href="http://drupal.org/user/58170">John Morahan</a> and <a href="http://drupal.org/user/36762">Greg Knaddison</a> of the Drupal Security team. </li> </ul> <h2>Coordinated by</h2> <ul> <li><a href="http://drupal.org/user/148199">Jeremy Thorson</a> QA/Testing infrastructure</li> <li><a href="http://drupal.org/user/91990">Ben Jeavons</a> of the Drupal Security Team</li> <li><a href="http://drupal.org/user/124982">David Rothstein</a> of the Drupal Security Team</li> <li><a href="http://drupal.org/user/4166">Gábor Hojtsy</a> of the Drupal Security Team</li> <li><a href="http://drupal.org/user/36762">Greg Knaddison</a> of the Drupal Security Team</li> <li><a href="http://drupal.org/user/426416">Fox</a> of the Drupal Security Team</li> </ul> <h2>Contact and More Information</h2> <p>The Drupal security team can be reached at security at drupal.org or via the contact form at <a href="http://drupal.org/contact">http://drupal.org/contact</a>.</p> <p>Learn more about <a href="http://drupal.org/security-team">the Drupal Security team and their policies</a>, <a href="http://drupal.org/writing-secure-code">writing secure code for Drupal</a>, and <a href="http://drupal.org/security/secure-configuration">securing your site</a>.</p> Security advisories for Drupal core Drupal 6.x Drupal 7.x Wed, 19 Dec 2012 18:46:26 +0000 Drupal Security Team 1870556 at https://drupal.org SA-CORE-2012-003 - Drupal core - Arbitrary PHP code execution and Information disclosure https://drupal.org/SA-CORE-2012-003 <ul><li>Advisory ID: DRUPAL-SA-CORE-2012-003</li> <li>Project: <a href="http://drupal.org/project/drupal" rel="nofollow">Drupal core</a></li> <li>Version: 7.x</li> <li>Date: 2012-October-17</li> <li>Security risk: <a href="http://drupal.org/security-team/risk-levels" rel="nofollow">Highly critical</a></li> <li>Exploitable from: Remote</li> <li>Vulnerability: Information Disclosure, Arbitrary PHP code execution</li> </ul><h2>Description</h2> <p>Multiple vulnerabilities were discovered in Drupal core.</p> <h3>Arbitrary PHP code execution</h3> <p>A bug in the installer code was identified that allows an attacker to re-install Drupal using an external database server under certain transient conditions. This could allow the attacker to execute arbitrary PHP code on the original server.</p> <p>This vulnerability is mitigated by the fact that the re-installation can only be successful if the site's settings.php file or sites directories are writeable by or owned by the webserver user. Configuring the Drupal installation to be owned by a different user than the webserver user (and not to be writeable by the webserver user) is a <a href="http://drupal.org/node/244924" rel="nofollow">recommended security best practice</a>. However, in all cases the transient conditions expose information to an attacker who accesses install.php, and therefore this security update should be applied to all Drupal 7 sites.</p> <p>CVE: CVE-2012-4553</p> <h3>Information disclosure - OpenID module</h3> <p>For sites using the core OpenID module, an information disclosure vulnerability was identified that allows an attacker to read files on the local filesystem by attempting to log in to the site using a malicious OpenID server.</p> <p>CVE: CVE-2012-4554</p> <h2>Versions affected</h2> <ul><li>Drupal core 7.x versions prior to 7.16.</li> </ul><p>Drupal 6 is not affected.</p> <h2>Solution</h2> <p>Install the latest version:</p> <ul><li>If you use Drupal 7.x, upgrade to <a href="http://drupal.org/node/1815904" rel="nofollow">Drupal core 7.16</a>.</li> </ul><p>If you are unable to deploy the security release immediately, removing or blocking access to install.php is a sufficient mitigation step for the arbitrary PHP code execution vulnerability.</p> <p>Also see the <a href="http://drupal.org/project/drupal" rel="nofollow">Drupal core</a> project page.</p> <h2>Reported by</h2> <ul><li>The arbitrary PHP code execution vulnerability was reported by <a href="http://drupal.org/user/17943" rel="nofollow">Heine Deelstra</a> and <a href="http://drupal.org/user/2317662" rel="nofollow">Noam Rathaus</a> working with Beyond Security's SecuriTeam Secure Disclosure Program. Heine Deelstra is also a member of the Drupal Security Team.</li> <li>The information disclosure vulnerability in the OpenID module was reported by <a href="http://drupal.org/user/2305626" rel="nofollow">Reginaldo Silva</a>.</li> </ul><h2>Fixed by</h2> <ul><li>The arbitrary PHP code execution vulnerability was fixed by <a href="http://drupal.org/user/22211" rel="nofollow">Damien Tournoud</a>, <a href="http://drupal.org/user/124982" rel="nofollow">David Rothstein</a>, <a href="http://drupal.org/user/49851" rel="nofollow">Peter Wolanin</a>, and <a href="http://drupal.org/user/9446" rel="nofollow">Károly Négyesi</a>, all members of the Drupal Security Team.</li> <li>The information disclosure vulnerability in the OpenID module was fixed by <a href="http://drupal.org/user/2305626" rel="nofollow">Reginaldo Silva</a>, <a href="http://drupal.org/user/216078" rel="nofollow">Christian Schmidt</a>, <a href="http://drupal.org/user/56154" rel="nofollow">Vojtěch Kusý</a>, and <a href="http://drupal.org/user/27985" rel="nofollow">Frédéric Marand</a>, and by <a href="http://drupal.org/user/49851" rel="nofollow">Peter Wolanin</a>, <a href="http://drupal.org/user/124982" rel="nofollow">David Rothstein</a>, <a href="http://drupal.org/user/22211" rel="nofollow">Damien Tournoud</a>, and <a href="http://drupal.org/user/17943" rel="nofollow">Heine Deelstra</a> of the Drupal Security Team.</li> </ul><h2>Contact and More Information</h2> <p>The Drupal security team can be reached at security at drupal.org or via the contact form at <a href="http://drupal.org/contact" rel="nofollow">http://drupal.org/contact</a>.</p> <p>Learn more about <a href="http://drupal.org/security-team" rel="nofollow">the Drupal Security team and their policies</a>, <a href="http://drupal.org/writing-secure-code" rel="nofollow">writing secure code for Drupal</a>, and <a href="http://drupal.org/security/secure-configuration" rel="nofollow">securing your site</a>.</p> Security advisories for Drupal core Drupal 7.x Wed, 17 Oct 2012 21:29:30 +0000 Drupal Security Team 1815912 at https://drupal.org SA-CORE-2012-002 - Drupal core multiple vulnerabilities https://drupal.org/SA-CORE-2012-002 <ul><li>Advisory ID: DRUPAL-SA-CORE-2012-002</li> <li>Project: <a href="http://drupal.org/project/drupal" rel="nofollow">Drupal core</a></li> <li>Version: 7.x</li> <li>Date: 2012-May-2</li> <li>Security risk: <a href="http://drupal.org/security-team/risk-levels" rel="nofollow">Critical</a></li> <li>Exploitable from: Remote</li> <li>Vulnerability: Denial of Service, Access bypass, Unvalidated form redirect</li> </ul><h2>Description</h2> <h3>Denial of Service</h3> <p>CVE: CVE-2012-1588</p> <p>Drupal core's text filtering system provides several features including removing inappropriate HTML tags and automatically linking content that appears to be a link. A pattern in Drupal's text matching was found to be inefficient with certain specially crafted strings. This vulnerability is mitigated by the fact that users must have the ability to post content sent to the filter system such as a role with the "post comments" or "Forum topic: Create new content" permission.</p> <h3>Unvalidated form redirect</h3> <p>CVE: CVE-2012-1589</p> <p>Drupal core's Form API allows users to set a destination, but failed to validate that the URL was internal to the site. This weakness could be abused to redirect the login to a remote site with a malicious script that harvests the login credentials and redirects to the live site. This vulnerability is mitigated only by the end user's ability to recognize a URL with malicious query parameters to avoid the social engineering required to exploit the problem.</p> <h3>Access bypass - forum listing</h3> <p>CVE: CVE-2012-1590</p> <p>Drupal core's forum lists fail to check user access to nodes when displaying them in the forum overview page. If an unpublished node was the most recently updated in a forum then users who should not have access to unpublished forum posts were still be able to see meta-data about the forum post such as the post title.</p> <h3>Access bypass - private images</h3> <p>CVE: CVE-2012-1591</p> <p>Drupal core provides the ability to have private files, including images, and Image Styles which create derivative images from an original image that may differ, for example, in size or saturation. Drupal core failed to properly terminate the page request for cached image styles allowing users to access image derivatives for images they should not be able to view. Furthermore, Drupal didn't set the right headers to prevent image styles from being cached in the browser.</p> <h3>Access bypass - content administration</h3> <p>CVE: CVE-2012-2153</p> <p>Drupal core provides the ability to list nodes on a site at admin/content. Drupal core failed to confirm a user viewing that page had access to each node in the list. This vulnerability only concerns sites running a contributed node access module and is mitigated by the fact that users must have a role with the "Access the content overview page" permission. Unpublished nodes were not displayed to users who only had the "Access the content overview page" permission.</p> <h2>Versions affected</h2> <ul><li>Drupal core 7.x versions prior to 7.13.</li> </ul><h2>Solution</h2> <p>Install the latest version:</p> <ul><li>If you use Drupal 7.x, upgrade to <a href="http://drupal.org/node/1558412" rel="nofollow"> Drupal core 7.13</a></li> </ul><p>Also see the <a href="http://drupal.org/project/drupal" rel="nofollow">Drupal core</a> project page.</p> <h2>Reported by</h2> <ul><li>The Denial of Service vulnerability was reported by <a href="http://drupal.org/user/923254" rel="nofollow">Jay Wineinger</a> and <a href="http://drupal.org/user/396253" rel="nofollow">Lin Clark</a>.</li> <li>The unvalidated form redirect vulnerability was reported by <a href="http://drupal.org/user/9446" rel="nofollow">Károly Négyesi</a> of the Drupal Security Team and Katsuhiko Nakanishi.</li> <li>The access bypass in forum listing vulnerability was reported by <a href="http://drupal.org/user/170314" rel="nofollow">Glen W</a>.</li> <li>The access bypass for private images vulnerability was reported by <a href="http://drupal.org/user/243377" rel="nofollow">frega</a>, <a href="http://drupal.org/user/414525" rel="nofollow">Andreas Gonell</a>, <a href="http://drupal.org/user/1271628" rel="nofollow">Jeremy Meier</a> and <a href="http://drupal.org/user/1792496" rel="nofollow">Xenza</a>.</li> <li>The access bypass for the content administration vulnerability was reported by <a href="http://drupal.org/user/155601" rel="nofollow">Jennifer Hodgdon</a>.</li> </ul><h2>Fixed by</h2> <ul><li>The Denial of Service was fixed by <a href="http://drupal.org/user/9446" rel="nofollow">Károly Négyesi</a> of the Drupal Security Team.</li> <li>The unvalidated form redirect was fixed by <a href="http://drupal.org/user/16747" rel="nofollow">Wolfgang Ziegler</a> and <a href="http://drupal.org/user/52142" rel="nofollow">Stéphane Corlosquet</a> of the Drupal Security Team.</li> <li>The access bypass in forum listing was fixed by <a href="http://drupal.org/user/102818" rel="nofollow">Michael Hess</a> of the Drupal Security Team, <a href="http://drupal.org/user/91990" rel="nofollow">Ben Jeavons</a> of the Drupal Security Team and <a href="http://drupal.org/user/65776" rel="nofollow">xjm</a>.</li> <li>The Access bypass for private images was fixed by <a href="http://drupal.org/user/9446" rel="nofollow">Károly Négyesi</a> of the Drupal Security Team, <a href="http://drupal.org/user/22211" rel="nofollow">Damien Tournoud</a> of the Drupal Security Team, <a href="http://drupal.org/user/36762" rel="nofollow">Greg Knaddison</a> of the Drupal Security Team, <a href="http://drupal.org/user/52142" rel="nofollow">Stéphane Corlosquet</a> of the Drupal Security Team, <a href="http://drupal.org/user/1792496" rel="nofollow">Xenza</a> and <a href="http://drupal.org/user/243377" rel="nofollow">frega</a>.</li> <li>The Access bypass for content administration was fixed by <a href="http://drupal.org/user/155601" rel="nofollow">Jennifer Hodgdon</a>.</li> </ul><h2>Contact and More Information</h2> <p>The Drupal security team can be reached at security at drupal.org or via the contact form at <a href="http://drupal.org/contact" rel="nofollow">http://drupal.org/contact</a>.</p> <p>Learn more about <a href="http://drupal.org/security-team" rel="nofollow">the Drupal Security team and their policies</a>, <a href="http://drupal.org/writing-secure-code" rel="nofollow">writing secure code for Drupal</a>, and <a href="http://drupal.org/security/secure-configuration" rel="nofollow">securing your site</a>.</p> Security advisories for Drupal core Drupal 7.x Wed, 02 May 2012 15:17:48 +0000 Drupal Security Team 1557938 at https://drupal.org SA-CORE-2012-001 - Drupal core multiple vulnerabilities https://drupal.org/SA-CORE-2012-001 <ul><li>Advisory ID: DRUPAL-SA-CORE-2012-001</li> <li>Project: <a href="http://drupal.org/project/drupal" rel="nofollow">Drupal core</a></li> <li>Version: 6.x, 7.x</li> <li>Date: 2012-February-01</li> <li>Security risk: <a href="http://drupal.org/security-team/risk-levels" rel="nofollow">Moderately critical</a></li> <li>Exploitable from: Remote</li> <li>Vulnerability: Access bypass, Cross Site Request Forgery, Multiple vulnerabilities</li> </ul><h2>Description</h2> <h3>Cross Site Request Forgery vulnerability in Aggregator module</h3> <p>CVE: CVE-2012-0826<br /> An XSRF vulnerability can force an aggregator feed to update. Since some services are rate-limited (e.g. Twitter limits requests to 150 per hour) this could lead to a denial of service.</p> <p>This issue affects Drupal 6.x and 7.x.</p> <h3>OpenID not verifying signed attributes in SREG and AX</h3> <p>CVE: CVE-2012-0825<br /> A group of security researchers identified a flaw in how some OpenID relying parties implement Attribute Exchange (AX). Not verifying that attributes being passed through AX have been signed could allow an attacker to modify users' information.</p> <p>This issue affects Drupal 6.x and 7.x.</p> <h3>Access bypass in File module</h3> <p>CVE: CVE-2012-0827<br /> When using private files in combination with certain field access modules, the File module will allow users to download the file even if they do not have access to view the field it was attached to.</p> <p>This issue affects Drupal 7.x only.</p> <h2>Versions affected</h2> <ul><li>Drupal 6.x core prior to 6.23.</li> <li>Drupal 7.x core prior to 7.11.</li> </ul><h2>Solution</h2> <p>Install the latest version:</p> <ul><li>If you use Drupal 6.x upgrade to <a href="http://drupal.org/node/1425082" rel="nofollow">6.23</a></li> <li>If you use Drupal 7.x upgrade to <a href="http://drupal.org/node/1425092" rel="nofollow">7.11</a></li> </ul><p>See also the <a href="http://drupal.org/project/drupal" rel="nofollow">Drupal core</a> project page.</p> <h2>Reported by</h2> <ul><li>The Aggregator module CSRF vulnerability was reported by <a href="http://drupal.org/user/96647" rel="nofollow">Dylan Tack</a> of the Drupal Security Team.</li> <li>The OpenID vulnerability was reported by <a href="http://openid.net/2011/05/05/attribute-exchange-security-alert/" rel="nofollow">Rui Wang, Shuo Chen and Xiao Feng Wang</a>.</li> <li>The File module access bypass issue was reported by <a href="http://drupal.org/user/124982" rel="nofollow">David Rothstein</a> of the Drupal Security Team, and by <a href="http://drupal.org/user/214652" rel="nofollow">Sascha Grossenbacher</a>.</li> </ul><h2>Fixed by</h2> <ul><li>Aggregator CSRF issue fixed by <a href="http://drupal.org/user/53892" rel="nofollow">Dave Reid</a> of the Drupal Security Team</li> <li>OpenID issue fixed by <a href="http://drupal.org/user/56154" rel="nofollow">Vojtech Kusy</a> and <a href="http://drupal.org/user/216078" rel="nofollow">Christian Schmidt</a></li> <li>The File module access bypass issue was fixed by <a href="http://drupal.org/user/124982" rel="nofollow">David Rothstein</a> of the Drupal Security Team, <a href="http://drupal.org/user/214652" rel="nofollow">Sascha Grossenbacher</a>, and <a href="http://drupal.org/user/46549" rel="nofollow">Derek Wright</a> of the Drupal Security Team.</li> </ul><h2>Contact and More Information</h2> <p>The Drupal security team can be reached at security at drupal.org or via the contact form at <a href="http://drupal.org/contact" rel="nofollow">http://drupal.org/contact</a>.</p> <p>Learn more about <a href="http://drupal.org/security-team" rel="nofollow">the Drupal Security team and their policies</a>, <a href="http://drupal.org/writing-secure-code" rel="nofollow">writing secure code for Drupal</a>, and <a href="http://drupal.org/security/secure-configuration" rel="nofollow">securing your site</a>.</p> Security advisories for Drupal core Drupal 6.x Drupal 7.x Wed, 01 Feb 2012 22:06:54 +0000 Drupal Security Team 1425084 at https://drupal.org SA-CORE-2011-003 - Drupal core - Access bypass https://drupal.org/node/1231510 <ul> <li>Advisory ID: DRUPAL-SA-CORE-2011-003</li> <li>Project: <a href="http://drupal.org/project/drupal">Drupal core</a></li> <li>Version: 7.x</li> <li>Date: 2011-July-27</li> <li>Security risk: <a href="http://drupal.org/security-team/risk-levels">Less critical</a></li> <li>Exploitable from: Remote</li> <li>Vulnerability: Access bypass</li> </ul> <!--break--><!--break--><h2>Description</h2> <p>CVE: CVE-2011-2726</p> <h3>Access bypass in private file fields on comments. </h3> <p>Drupal 7 contains two new features: the ability to attach File upload fields to any entity type in the system and the ability to point individual File upload fields to the private file directory.</p> <p>If a Drupal site is using these features on comments, and the parent node is denied access (either by a node access module or by being unpublished), the file attached to the comment can still be downloaded by non-privileged users if they know or guess its direct URL.</p> <p>This issue affects Drupal 7.x only.</p> <h2>Versions affected</h2> <ul> <li>Drupal 7.x before version 7.5.</li> </ul> <h2>Solution</h2> <p>Install the latest version:</p> <ul> <li>If you are running Drupal 7.x then upgrade to Drupal 7.5 or <del>7.6</del> 7.7.</li> </ul> <p>The Security Team has released both a pure security update without other bug fixes and a security update combined with other bug fixes and improvements. You can choose to either only include the security update for an immediate fix (which might require less quality assurance and testing) or more fixes and improvements alongside the security fixes by choosing between Drupal 7.5 and Drupal <del>7.6</del> 7.7. Read the <a href="http://drupal.org/drupal-7.7">announcement</a> for more information.</p> <p>See also the <a href="http://drupal.org/project/drupal">Drupal core</a> project page.</p> <h2>Reported by</h2> <ul> <li>The File access bypass was reported by <a href="http://drupal.org/user/254778">Florian Weber</a>.</li> </ul> <h2>Fixed by</h2> <ul> <li>The File access bypass was fixed by <a href="http://drupal.org/user/52142">Stéphane Corlosquet</a> and <a href="http://drupal.org/user/9446">Károly Négyesi</a>, both members of the Drupal security team.</li> </ul> <h2>Contact and More Information</h2> <p>The Drupal security team can be reached at security at drupal.org or via the contact form at <a href="http://drupal.org/contact">http://drupal.org/contact</a>.</p> <p>Learn more about <a href="http://drupal.org/security-team">the Drupal Security team and their policies</a>, <a href="http://drupal.org/writing-secure-code">writing secure code for Drupal</a>, and <a href="http://drupal.org/security/secure-configuration">securing your site</a>.</p> Security advisories for Drupal core Drupal 7.x Wed, 27 Jul 2011 19:32:17 +0000 Drupal Security Team 1231510 at https://drupal.org SA-CORE-2011-002 - Drupal core - Access bypass https://drupal.org/node/1204582 <ul><li>Advisory ID: DRUPAL-SA-CORE-2011-002</li> <li>Project: <a href="http://drupal.org/project/drupal" rel="nofollow">Drupal core</a></li> <li>Version: 7.x</li> <li>Date: 2011-JUNE-29</li> <li>Security risk: <a href="http://drupal.org/security-team/risk-levels" rel="nofollow">Highly critical</a></li> <li>Exploitable from: Remote</li> <li>Vulnerability: Access bypass</li> </ul><h2>Description</h2> <p>CVE: CVE-2011-2687</p> <h3>Access bypass in node listings</h3> <p>Listings showing nodes but not JOINing the node table show all nodes regardless of restrictions imposed by the node_access system. In core, this affects the taxonomy and the forum subsystem.</p> <p>This issue only affects sites using a node access module such as <a href="http://drupal.org/project/content_access" rel="nofollow">content access</a> or <a href="http://drupal.org/project/forum_access" rel="nofollow">forum access</a>. If you do not use any node access system then your site is not affected by this vulnerability. It is still considered a best practice to run the latest release and all site owners are encouraged to upgrade when they can regardless of whether or not they are affected.</p> <p>Note that fixing this issue in contributed modules requires a backwards-compatible API change for modules listing nodes. See <a href="http://drupal.org/node/1204572" title="http://drupal.org/node/1204572" rel="nofollow">http://drupal.org/node/1204572</a> for more details.</p> <p>This issue affects Drupal 7.x only.</p> <h2>Versions affected</h2> <ul><li>Drupal 7.0, 7.1 and 7.2.</li> </ul><h2>Solution</h2> <p>Install the latest version:</p> <ul><li>If you are running Drupal 7.x then upgrade to Drupal <a href="http://drupal.org/node/1204628" rel="nofollow">7.3</a> or <a href="http://drupal.org/node/1204634" rel="nofollow">7.4.</a></li> </ul><p>The Security Team has released both a pure security update without other bug fixes and a security update combined with other bug fixes and improvements. You can choose to either only include the security update for an immediate fix (which might require less quality assurance and testing) or more fixes and improvements alongside the security fixes by choosing between Drupal 7.3 and Drupal 7.4. Read the <a href="http://drupal.org/drupal-7.4" rel="nofollow">announcement</a> for more information.</p> <p>See also the <a href="http://drupal.org/project/drupal" rel="nofollow">Drupal core</a> project page.</p> <h2>Reported by</h2> <ul><li>The access bypass was reported independently by numerous people, including <a href="http://drupal.org/user/214652" rel="nofollow">Sascha Grossenbacher</a>, <a href="http://drupal.org/user/265439" rel="nofollow">Khaled Alhourani</a>, and <a href="http://drupal.org/user/12534" rel="nofollow">Ben Ford</a>.</li> </ul><h2>Fixed by</h2> <ul><li>The access bypass was fixed by <a href="http://drupal.org/user/9446" rel="nofollow">Károly Négyesi</a>, member of the Drupal security team</li> </ul><h2>Contact and More Information</h2> <p>The Drupal security team can be reached at security at drupal.org or via the contact form at <a href="http://drupal.org/contact" rel="nofollow">http://drupal.org/contact</a>.</p> <p>Learn more about <a href="http://drupal.org/security-team" rel="nofollow">the Drupal Security team and their policies</a>, <a href="http://drupal.org/writing-secure-code" rel="nofollow">writing secure code for Drupal</a>, and <a href="http://drupal.org/security/secure-configuration" rel="nofollow">securing your site</a>.</p> Security advisories for Drupal core Drupal 7.x Thu, 30 Jun 2011 00:13:40 +0000 Drupal Security Team 1204582 at https://drupal.org SA-CORE-2011-001 - Drupal core - Multiple vulnerabilities https://drupal.org/node/1168756 <ul><li>Advisory ID: DRUPAL-SA-CORE-2011-001</li> <li>Project: <a href="http://drupal.org/project/drupal" rel="nofollow">Drupal core</a></li> <li>Version: 6.x, 7.x</li> <li>Date: 2011-May-25</li> <li>Security risk: <a href="http://drupal.org/security-team/risk-levels" rel="nofollow">Critical</a></li> <li>Exploitable from: Remote</li> <li>Vulnerability: Access bypass, Cross Site Scripting</li> </ul><h2>Description</h2> <p>CVE: CVE-2011-2687</p> <p>Multiple vulnerabilities and weaknesses were discovered in Drupal.</p> <h3>Reflected cross site scripting vulnerability in error handler</h3> <p>A reflected cross site scripting vulnerability was discovered in Drupal's error handler. Drupal displays PHP errors in the messages area, and a specially crafted URL can cause malicious scripts to be injected into the message. The issue can be mitigated by disabling on-screen error display at admin/settings/error-reporting. This is the recommended setting for production sites.</p> <p>This issue affects Drupal 6.x only.</p> <h3>Cross site scripting vulnerability in Color module</h3> <p>When using re-colorable themes, color inputs are not sanitized. Malicious color values can be used to insert arbitrary CSS and script code. Successful exploitation requires the "Administer themes" permission.</p> <p>This issue affects Drupal 6.x and 7.x.</p> <h3>Access bypass in File module</h3> <p>When using private files in combination with a node access module, the File module allows unrestricted access to private files.</p> <p>This issue affects Drupal 7.x only.</p> <h2>Versions affected</h2> <ul><li>Drupal 7.x before version 7.1.</li> <li>Drupal 6.x before version 6.21.</li> </ul><h2>Solution</h2> <p>Install the latest version:</p> <ul><li>If you are running Drupal 7.x then upgrade to Drupal <a href="http://drupal.org/node/1168910" rel="nofollow">7.1</a> or <a href="http://drupal.org/node/1168946" rel="nofollow">7.2</a>.</li> <li>If you are running Drupal 6.x then upgrade to Drupal <a href="http://drupal.org/node/1168908" rel="nofollow">6.21</a> or <a href="http://drupal.org/node/1168950" rel="nofollow">6.22.</a></li> </ul><p>The Security Team has released both a pure security update without other bug fixes and a security update combined with other bug fixes and improvements. You can choose to either only include the security update for an immediate fix (which might require less quality assurance and testing) or more fixes and improvements alongside the security fixes by choosing between <a href="http://drupal.org/node/1168910" rel="nofollow">Drupal 7.1</a> and <a href="http://drupal.org/node/1168946" rel="nofollow">Drupal 7.2</a> or <a href="http://drupal.org/node/1168908" rel="nofollow">Drupal 6.21</a> and <a href="http://drupal.org/node/1168950" rel="nofollow">Drupal 6.22</a>. </p> <p>See the <a href="http://drupal.org/drupal-7.2" rel="nofollow">release announcement</a> for more information.</p> <p>See also the <a href="http://drupal.org/project/drupal" rel="nofollow">Drupal core</a> project page.</p> <h2>Reported by</h2> <ul><li>The reflected cross site scripting vulnerability was reported by <a href="http://drupal.org/user/17943" rel="nofollow">Heine Deelstra</a> (*).</li> <li>The Color module cross site scripting vulnerability was reported by Kasper Lindgaard, Secunia Research.</li> <li>The File access bypass was reported by Hubert Lecorche, and <a href="https://drupal.org/user/309898" rel="nofollow">Peter Bex</a>.</li> </ul><h2>Fixed by</h2> <ul><li>The reflected cross site scripting vulnerability was fixed by Alan Smithee.</li> <li>The Color module cross site scripting vulnerability was fixed by <a href="http://drupal.org/user/52142" rel="nofollow">Stéphane Corlosquet</a> (*), <a href="http://drupal.org/user/17943" rel="nofollow">Heine Deelstra</a> (*), and <a href="http://drupal.org/user/49851" rel="nofollow">Peter Wolanin</a> (*).</li> <li>The File access bypass was fixed by <a href="http://drupal.org/user/17943" rel="nofollow">Heine Deelstra</a> (*).</li> </ul><p>(*) Member of the Drupal security team.</p> <h2>Contact and More Information</h2> <p>The Drupal security team can be reached at security at drupal.org or via the contact form at <a href="http://drupal.org/contact" rel="nofollow">http://drupal.org/contact</a>.</p> <p>Learn more about <a href="http://drupal.org/security-team" rel="nofollow">the Drupal Security team and their policies</a>, <a href="http://drupal.org/writing-secure-code" rel="nofollow">writing secure code for Drupal</a>, and <a href="http://drupal.org/security/secure-configuration" rel="nofollow">securing your site</a>.</p> Security advisories for Drupal core Drupal 6.x Drupal 7.x Wed, 25 May 2011 18:07:48 +0000 Drupal Security Team 1168756 at https://drupal.org SA-CORE-2010-002 - Drupal core - Multiple vulnerabilities https://drupal.org/node/880476 <ul><li>Advisory ID: DRUPAL-SA-CORE-2010-002</li> <li>Project: Drupal core</li> <li>Version: 5.x, 6.x</li> <li>Date: 2010-August-11</li> <li>Security risk: Critical</li> <li>Exploitable from: Remote</li> <li>Vulnerability: Multiple vulnerabilities</li> </ul><h2>Description</h2> <p>Multiple vulnerabilities and weaknesses were discovered in Drupal.</p> <h3>OpenID authentication bypass</h3> <p>The OpenID module provides users the ability to login to sites using an OpenID account.</p> <p>The OpenID module doesn't implement all the required verifications from the OpenID 2.0 protocol and is vulnerable to a number of attacks.</p> <p>Specifically:<br /> - OpenID should verify that a "openid.response_nonce" has not already been used for an assertion by the OpenID provider<br /> - OpenID should verify the value of openid.return_to as obtained from the OpenID provider<br /> - OpenID must verify that all fields that are required to be signed are signed</p> <p>These specification violations allow malicious sites to harvest positive assertions from OpenID providers and use them on sites using the OpenID module to obtain access to preexisting accounts bound to the harvested OpenIDs. Intercepted assertions from OpenID providers can also be replayed and used to obtain access to user accounts bound to the intercepted OpenIDs.</p> <p>This issue affects Drupal 6.x only. A separate <a href="http://drupal.org/node/880480" rel="nofollow">security announcement and release</a> is published for the contributed OpenID module for Drupal 5.x. </p> <h3>File download access bypass</h3> <p>The upload module allows users to upload files and provides access checking for file downloads.</p> <p>The module looks up files for download in the database and serves them for download after access checking. However, it does not account for the fact that certain database configurations will not consider case differences in file names. If a malicious user uploads a file which only differs in letter case, access will be granted for the earlier upload regardless of actual file access to that.</p> <p>This issue affects Drupal 5.x and 6.x.</p> <h3>Comment unpublishing bypass</h3> <p>The comment module allows users to leave comments on content on the site.</p> <p>The module supports unpublishing comments by privileged users. Users with the "post comments without approval" permission however could craft a URL which allows them to republish previously unpublished comments.</p> <p>This issue affects Drupal 5.x and 6.x.</p> <h3>Actions cross site scripting</h3> <p>The actions feature combined with Drupal's trigger module allows users to configure certain actions to happen when users register, content is submitted, and so on; through a web based interface.</p> <p>Users with "administer actions permission" can enter action descriptions and messages which are not properly filtered on output. Users with content and taxonomy tag submission permissions can create nodes and taxonomy terms which are not properly sanitized for inclusion in action messages and inject arbitrary HTML and script code into Drupal pages. Such a cross-site scripting attack may lead to the malicious user gaining administrative access. Wikipedia has more information about <a href="http://en.wikipedia.org/wiki/Cross-site_scripting" rel="nofollow">cross-site scripting</a> (XSS).</p> <p>This issue affects Drupal 6.x only.</p> <h2>Versions affected</h2> <ul><li>Drupal 6.x before version 6.18 or 6.19.</li> <li>Drupal 5.x before version 5.23.</li> </ul><h2>Solution</h2> <p>Install the latest version:</p> <ul><li>If you are running Drupal 6.x then upgrade to <a href="http://ftp.drupal.org/files/projects/drupal-6.18.tar.gz" rel="nofollow">Drupal 6.18</a> or <a href="http://ftp.drupal.org/files/projects/drupal-6.19.tar.gz" rel="nofollow">Drupal 6.19</a>.</li> <li>If you are running Drupal 5.x then upgrade to <a href="http://ftp.drupal.org/files/projects/drupal-5.23.tar.gz" rel="nofollow">Drupal 5.23</a>.</li> </ul><p>Drupal 5 will no longer be maintained when <a href="http://drupal.org/node/725382" rel="nofollow">Drupal 7 is released</a>. <a href="http://drupal.org/upgrade" rel="nofollow">Upgrading to Drupal 6</a> is recommended.</p> <p>The security team starts a new practice of releasing both a pure security update without other bugfixes and a security update combined with other bug fixes and improvements. You can choose to either only include the security update for an immediate fix (which might require less quality assurance and testing) or more fixes and improvements alongside the security fixes by choosing between Drupal 6.18 and Drupal 6.19. Read <a href="http://drupal.org/drupal-6.19" rel="nofollow">the announcement</a> for more information.</p> <h2>Reported by</h2> <p>The OpenID authentication bypass issues were reported by <a href="http://drupal.org/user/226462" rel="nofollow">Johnny Bufu</a>, <a href="http://drupal.org/user/216078" rel="nofollow">Christian Schmidt</a> and <a href="http://drupal.org/user/17943" rel="nofollow">Heine Deelstra</a> (*).<br /> The file download access bypass was reported by <a href="http://drupal.org/user/16747" rel="nofollow">Wolfgang Ziegler</a>.<br /> The comment unpublish bypass issue was reported by <a href="http://drupal.org/user/17943" rel="nofollow">Heine Deelstra</a> (*).<br /> The actions module cross site scripting was reported by <a href="http://drupal.org/user/302225" rel="nofollow">Justin Klein Keane</a> and <a href="http://drupal.org/user/17943" rel="nofollow">Heine Deelstra</a> (*).</p> <p>(*) Member of the Drupal security team.</p> <h2>Fixed by</h2> <p>The OpenID authentication issues were fixed by <a href="http://drupal.org/user/216078" rel="nofollow">Christian Schmidt</a>, <a href="http://drupal.org/user/17943" rel="nofollow">Heine Deelstra</a> (*) and <a href="http://drupal.org/user/22211" rel="nofollow">Damien Tournoud</a> (*).<br /> The file download access bypass was fixed by <a href="http://drupal.org/user/53892" rel="nofollow">Dave Reid</a> (*) and <a href="http://drupal.org/user/3064" rel="nofollow">Neil Drumm</a> (*).<br /> The comment unpublish bypass issue was fixed by <a href="http://drupal.org/user/17943" rel="nofollow">Heine Deelstra</a> (*).<br /> The actions module cross site scripting was fixed by <a href="http://drupal.org/user/302225" rel="nofollow">Justin Klein Keane</a> and <a href="http://drupal.org/user/17943" rel="nofollow">Heine Deelstra</a> (*).</p> <p>(*) Member of the Drupal security team.</p> <h2>Contact</h2> <p>The security team for Drupal can be reached at security at drupal.org or via the form at <a href="http://drupal.org/contact" title="http://drupal.org/contact" rel="nofollow">http://drupal.org/contact</a>.</p> Security advisories for Drupal core Drupal 5.x Drupal 6.x Wed, 11 Aug 2010 19:53:18 +0000 Drupal Security Team 880476 at https://drupal.org