[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20120905191749.A2B3C110049@www7.drupal.org>
Date: Wed, 5 Sep 2012 19:17:49 +0000 (UTC)
From: security-news@...pal.org
To: security-news@...pal.org
Subject: [Security-news] SA-CONTRIB-2012-137 - Heartbeat -
Cross Site Request Forgery (CSRF) in heartbeat_comments
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
_______________________________________________
Security-news mailing list
Security-news@...pal.org
Unsubscribe at http://lists.drupal.org/mailman/listinfo/security-news
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists