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

* Advisory ID: DRUPAL-SA-CONTRIB-2017-013 * Project: Acquia Content Hub [1] (third-party module) * Version: 8.x * Date: 2017-February-08 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:All [2] * Vulnerability: Access bypass

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

The Acquia Content Hub module enables the distribution and discovery of content from any source using the Acquia Content Hub [3] service.

The module allows rendering of any arbitrary entity, without performing the appropriate access check. Users browsing to a well crafted URL could access information they may not be authorized to view.

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

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

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

* Acquia Content Hub 8.x-1.x versions prior to 8.x-1.4.

Drupal core is not affected. If you do not use the contributed Acquia Content Hub [5] module, there is nothing you need to do.

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

Install the latest version:

* If you use the Acquia Content Hub module for Drupal 8.x, upgrade to Acquia Content Hub 8.x-1.4 [6]

Also see the Acquia Content Hub [7] project page.

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

* Samuel Mortenson [8]

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

* Alejandro Barrios [9] the module maintainer * Cash William [10] of the Drupal Security Team * Samuel Mortenson [11] * Kyle Browning [12] * Wim Leers [13]

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

* Stéphane Corlosquet [14] 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 [15].

Learn more about the Drupal Security team and their policies [16], writing secure code for Drupal [17], and securing your site [18].

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

[1] https://www.drupal.org/project/acquia_contenthub [2] https://www.drupal.org/security-team/risk-levels [3] https://www.acquia.com/products-services/acquia-content-hub [4] http://cve.mitre.org/ [5] https://www.drupal.org/project/acquia_contenthub [6] https://www.drupal.org/node/2850903 [7] https://www.drupal.org/project/acquia_contenthub [8] https://www.drupal.org/u/samuelmortenson [9] https://www.drupal.org/u/abarrios [10] https://www.drupal.org/u/cashwilliams [11] https://www.drupal.org/u/samuelmortenson [12] https://www.drupal.org/u/kylebrowning [13] https://www.drupal.org/u/wim-leers [14] https://www.drupal.org/u/scor [15] https://www.drupal.org/contact [16] https://www.drupal.org/security-team [17] https://www.drupal.org/writing-secure-code [18] https://www.drupal.org/security/secure-configuration [19] https://twitter.com/drupalsecurity