View online: https://www.drupal.org/node/2782035 * Advisory ID: DRUPAL-SA-CONTRIB-2016-044 * Project: OAuth2 Client [1] (third-party module) * Version: 7.x * Date: 2016-August-10 * Security risk: 10/25 ( Moderately Critical) AC:Complex/A:None/CI:None/II:None/E:Proof/TD:All [2] * Vulnerability: Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- This module provides an OAuth2 client. The module does not check the validity of the state parameter, during server-side flow, before getting a token. This may allow a malicious user to feed a fake access_token to another user, and subsequently provide him fake data from the server. This page explains it in more details: http://www.twobotechnologies.com/blog/2014/02/importance-of-state-in-oau... [3] -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [4] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * OAuth2 Client 7.x-1.x versions prior to 7.x-1.5. Drupal core is not affected. If you do not use the contributed OAuth2 Client [5] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the OAuth2 Client module for Drupal 7.x, upgrade to OAuth2 Client 7.x-1.5 [6] Also see the OAuth2 Client [7] project page. -------- REPORTED BY --------------------------------------------------------- * Jason Woods [8] -------- FIXED BY ------------------------------------------------------------ * Dashamir Hoxha [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Michael Hess [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 https://www.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]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/oauth2_client [2] https://www.drupal.org/security-team/risk-levels [3] http://www.twobotechnologies.com/blog/2014/02/importance-of-state-in-oauth2.... [4] http://cve.mitre.org/ [5] https://www.drupal.org/project/oauth2_client [6] https://www.drupal.org/project/oauth2_client/releases/7.x-1.5 [7] https://www.drupal.org/project/oauth2_client [8] https://www.drupal.org/u/Driskell [9] https://www.drupal.org/u/dashohoxha [10] https://www.drupal.org/u/mlhess [11] https://www.drupal.org/contact [12] https://www.drupal.org/security-team [13] https://www.drupal.org/writing-secure-code [14] https://www.drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity