View online: https://www.drupal.org/node/2881215 * Advisory ID: DRUPAL-SA-CONTRIB-2017-051 * Project: Site verification [1] (third-party module) * Version: 7.x * Date: 2017-May-24 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Proof/TD:Default [2] * Vulnerability: Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- The Site Verify module enables privilege users to verify a site with services like Google Webmaster Tools using meta tags or file uploads. The module doesn't sufficiently sanitize input or restrict uploads. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer site verify". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Site Verify 7.x-1.x versions prior to 7.x-1.2. Drupal core is not affected. If you do not use the contributed Site verification [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Site Verify module for Drupal 7.x, upgrade to Site Verify 7.1-1.2 [5] Also see the Site verification [6] project page. -------- REPORTED BY --------------------------------------------------------- * Kevin Reynen [7] -------- FIXED BY ------------------------------------------------------------ * Kevin Reynen [8] * Damien McKenna [9] of the Drupal Security Team -------- 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/site_verify [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/site_verify [5] https://www.drupal.org/project/site_verify/releases/7.x-1.2 [6] https://www.drupal.org/project/site_verify [7] https://www.drupal.org/u/kreynen [8] https://www.drupal.org/u/kreynen [9] https://www.drupal.org/u/DamienMcKenna [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