View online: https://www.drupal.org/node/2892400
* Advisory ID: DRUPAL-SA-CONTRIB-2017-056 * Project: OAuth [1] (third-party module) * Version: 8.x * Date: 2017-July-05 * Security risk: 15/25 ( Critical) AC:Complex/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Access bypass
-------- DESCRIPTION ---------------------------------------------------------
This module enables you to protect requests via the OAuth authentication protocol.
The module doesn't sufficiently notify the Cache API to avoid caching responses under the scenario in which an authenticated user requests a resource such as unpublished node.
This vulnerability is mitigated by the fact that an attacker must know the available resources in a Drupal site.
-------- CVE IDENTIFIER(S) ISSUED --------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED ---------------------------------------------------
* OAuth 8.x-2.x versions prior to 8.x-2.1.
Drupal core is not affected. If you do not use the contributed OAuth [4] module, there is nothing you need to do.
-------- SOLUTION ------------------------------------------------------------
In addition to updating the code, you must Clear all caches.
* If you use the OAuth module for Drupal 8.x, upgrade to OAuth 8.x-2.1
Also see the OAuth [5] project page.
-------- REPORTED BY ---------------------------------------------------------
* Kevin Dutra [6].
-------- FIXED BY ------------------------------------------------------------
* Kevin Dutra [7] * Juampy NR [8] the module maintainer
-------- COORDINATED BY ------------------------------------------------------
* Michael Hess [9] of the Drupal Security Team Greg Knaddison [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/oauth [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/oauth [5] https://www.drupal.org/project/oauth [6] https://www.drupal.org/user/1312744 [7] https://www.drupal.org/user/1312744 [8] https://www.drupal.org/u/juampynr [9] https://security.drupal.org/user/14049 [10] https://www.drupal.org/u/greggles [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