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

* Advisory ID: DRUPAL-SA-CONTRIB-2015-172 * Project: Values [1] (third-party module) * Version: 7.x * Date: 2015-December-16 * Security risk: 16/25 ( Critical) AC:Basic/A:Admin/CI:All/II:All/E:Proof/TD:Uncommon [2] * Vulnerability: Arbitrary PHP code execution

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

This module enables you to create key|value pairs for use in list fields, webforms etc.

The module includes an import page that runs eval() on an exported code block (ctools), but the permission for the page does not warn about security concerns of importing raw php code like this (trusted permission).

This vulnerability is mitigated by the fact that an attacker must have a role with the permission "import value sets".

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

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

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

* Values 7.x-1.x versions prior to 7.x-1.2.

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

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

Install the latest version:

* If you use the values module for Drupal 7.x, upgrade to Values 7.x-1.2 [5]

Also see the Values [6] project page.

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

* Sam Becker [7]

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

* Chris Eastwood [8] the module maintainer

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

* Greg Knaddison [9] of the Drupal Security Team * 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/values [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/values [5] https://www.drupal.org/node/2622534 [6] https://www.drupal.org/project/values [7] https://www.drupal.org/user/1485048 [8] https://www.drupal.org/user/823702 [9] https://www.drupal.org/u/greggles [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