[Security-news] SA-CONTRIB-2015-068 - Campaign Monitor - Cross Site Request Forgery (CSRF) - Unsupported

security-news at drupal.org security-news at drupal.org
Wed Mar 4 19:47:33 UTC 2015


View online: https://www.drupal.org/node/2445971

   * Advisory ID: DRUPAL-SA-CONTRIB-2015-068
   * Project: Campaign Monitor [1]     (third-party module)
   * Version: 7.x
   * Date: 2015-March-04
   * Security risk: 13/25 ( Moderately Critical)
     AC:Basic/A:None/CI:None/II:Some/E:Theoretical/TD:All [2]
   * Vulnerability: Cross Site Request Forgery

-------- DESCRIPTION
---------------------------------------------------------

Campaign Monitor module integrates the Campaign Monitor API into Drupal.

The module doesn't sufficiently protect some URLs against CSRF. A malicious
user can cause another user to enable and disable list subscriptions by
getting their browser to make a request to a specially-crafted URL.


-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------

   * /A CVE identifier [3] will be requested, and added upon issuance, in
     accordance with Drupal Security Team processes./

-------- VERSIONS AFFECTED
---------------------------------------------------

   * Campaign Monitor 7.x-1.0

Drupal core is not affected. If you do not use the contributed Campaign
Monitor [4] module, there is nothing you need to do.

-------- SOLUTION
------------------------------------------------------------

If you use the Campaign Monitor module for Drupal 7 you should uninstall it.

Also see the Campaign Monitor [5] project page.

-------- REPORTED BY
---------------------------------------------------------

   * Pere Orga [6] of the Drupal Security Team

-------- FIXED BY
------------------------------------------------------------

Not applicable.

-------- COORDINATED BY
------------------------------------------------------

   * Pere Orga [7] 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 https://www.drupal.org/contact [8].

Learn more about the Drupal Security team and their policies [9], writing
secure code for Drupal [10], and  securing your site [11].

Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [12]


[1] https://www.drupal.org/project/campaignmonitor
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/campaignmonitor
[5] https://www.drupal.org/project/campaignmonitor
[6] https://www.drupal.org/user/2301194
[7] https://www.drupal.org/user/2301194
[8] https://www.drupal.org/contact
[9] https://www.drupal.org/security-team
[10] https://www.drupal.org/writing-secure-code
[11] https://www.drupal.org/security/secure-configuration
[12] https://twitter.com/drupalsecurity



More information about the Security-news mailing list