[Security-news] Alinks - Moderately Critical -Access bypass - SA-CONTRIB-2017-058

[security-news at drupal.org]

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

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

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

This module enables you to automatically link keywords to specific URLs.

This module has an insufficient access check on the delete route.

Alinks uses the wrong permission for an access check.


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

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

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

   * Alinks  8.x-1.x versions prior to 8.x-1.1.

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

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

Install the latest version:

   * If you use the Alinks module for Drupal 8.x, upgrade to Alinks 8.x-1.1 
[5]

Also see the Alinks [6] project page.

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

   * Inasse [7]

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

   * Inasse [8]
   * Webflo [9]
   * Greg Boggs [10] the module maintainer

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

   * Michael Hess [11] 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 [12].

Learn more about the Drupal Security team and their policies [13], writing
secure code for Drupal [14], and  securing your site [15].

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


[1] https://www.drupal.org/project/alinks
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/alinks
[5] https://www.drupal.org/project/alinks/releases/8.x-1.1
[6] https://www.drupal.org/project/alinks
[7] https://www.drupal.org/u/insasse
[8] https://www.drupal.org/u/insasse
[9] https://www.drupal.org/u/webflo
[10] https://www.drupal.org/u/greg-boggs
[11] https://www.drupal.org/u/mlhess
[12] https://www.drupal.org/contact
[13] https://www.drupal.org/security-team
[14] https://www.drupal.org/writing-secure-code
[15] https://www.drupal.org/security/secure-configuration
[16] https://twitter.com/drupalsecurity