- Security-news - lists.drupal.org

Values - Critical - Arbitrary PHP code execution - SA-CONTRIB-2015-172
by security-news＠drupal.org 16 Dec '15

16 Dec '15

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

1 0

PSA Drupal core - Critical - Remote installation DRUPAL-PSA-CONTRIB-2015-001
by security-news＠drupal.org 02 Dec '15

02 Dec '15

View online: https://www.drupal.org/PSA-2015-001 * Advisory ID: DRUPAL-PSA-CONTRIB-2015-001 * Project: Drupal core [1] * Version: 6.x, 7.x, 8.x * Date: 2015-December-02 * Security risk: 17/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Exploit/TD:Uncommon [2] * Vulnerability: Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- When a Drupal installation is not completed past the database configuration phase and install.php is left accessible via the internet, any visitor to install.php may complete the installation with a remote database of their selection. Such a malicious user may use the remote database to execute code on the server. The above also applies to sites that react to certain hostnames with an installation page and have a sites folder owned or writable by the webserver. Such inadvertent multisites may occur when no default settings.php is present and directory permissions are misconfigured. These vulnerabilities are mitigated by setting directory and/or file permissions that prevent the webserver from writing to the sites/default/ and sites/ directories. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- Drupal 6 core, Drupal 7 core and Drupal 8 core. -------- SOLUTION ------------------------------------------------------------ Always complete installations fully on servers exposed to the internet. Ensure that the webserver does not own the sites folder and cannot write to the sites folder. Consider removing install.php after installation. Consider installing and automating the execution of Security review [4] which will identify weak file permissions and ownership. Also see the Drupal core [5] project page. -------- COORDINATED BY ------------------------------------------------------ * Heine Deelstra [6] of the Drupal security team * Greg Knaddison [7] of the Drupal security team * Michael Hess [8] 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 [9]. Learn more about the Drupal Security team and their policies [10], writing secure code for Drupal [11], and securing your site [12]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [13] [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/security_review [5] https://www.drupal.org/project/drupal [6] https://www.drupal.org/u/heine [7] https://www.drupal.org/u/greggles [8] https://www.drupal.org/u/mlhess [9] https://www.drupal.org/contact [10] https://www.drupal.org/security-team [11] https://www.drupal.org/writing-secure-code [12] https://www.drupal.org/security/secure-configuration [13] https://twitter.com/drupalsecurity

1 0

Token Insert Entity - Moderately Critical - Access bypass and information disclosure - SA-CONTRIB-2015-171
by security-news＠drupal.org 02 Dec '15

02 Dec '15

View online: https://www.drupal.org/node/2627638 * Advisory ID: DRUPAL-SA-CONTRIB-2015-171 * Project: Token Insert Entity [1] (third-party module) * Version: 7.x * Date: 2015-December-02 * Security risk: 10/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass, Information Disclosure -------- DESCRIPTION --------------------------------------------------------- This module offers a WYSIWYG button to embed rendered entities in fields using a WYSIWYG (normally the body of a node). There is a vulnerability because a user that can create or edit content and has the "insert entity token" permission can insert tokens relating to e.g. an unpublished node and allow any (including anonymous) users to see this rendered node embedded into the main node. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Token Insert Entity 7.x-1.x versions prior to 7.x-1.1. Drupal core is not affected. If you do not use the contributed Token Insert Entity [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Token Insert Entity module for Drupal 7.x, upgrade to Token Insert Entity 7.x-1.1 [5] Also see the Token Insert Entity [6] project page. -------- REPORTED BY --------------------------------------------------------- * killes [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Juampy NR [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Peter Wolanin [9] 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 [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [14] [1] https://www.drupal.org/project/token_insert_entity [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/token_insert_entity [5] https://www.drupal.org/node/2571905 [6] https://www.drupal.org/project/token_insert_entity [7] https://www.drupal.org/user/227 [8] https://www.drupal.org/user/682736 [9] https://www.drupal.org/user/49851 [10] https://www.drupal.org/contact [11] https://www.drupal.org/security-team [12] https://www.drupal.org/writing-secure-code [13] https://www.drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

Apache Solr Search - Moderately Critical - Access Bypass - SA-CONTRIB-2015-170
by security-news＠drupal.org 02 Dec '15

02 Dec '15

View online: https://www.drupal.org/node/2627580 * Advisory ID: DRUPAL-SA-CONTRIB-2015-170 * Project: Apache Solr Search [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-December-02 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:None/CI:None/II:Some/E:Proof/TD:Default [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to connect to an Apache Solr search server to provide a replacement for Drupal core content search and provide both extra features and better search performance and relevance. The module doesn't correctly check access when attempting to delete non-default search environments. This vulnerability is mitigated by the fact that the site must have a non-default environment configured and an attacker must discover the ID of the environment. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Apache Solr Search 6.x-3.x versions prior to 6.x-3.1. * Apache Solr Search 7.x-1.x versions prior to 7.x-1.8. Drupal core is not affected. If you do not use the contributed Apache Solr Search [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Apache Solr Search module for Drupal 6.x, upgrade to Apache Solr Search 6.x-3.1 [5] * If you use the Apache Solr Search module for Drupal 7.x, upgrade to Apache Solr Search 7.x-1.8 [6] Also see the Apache Solr Search [7] project page. -------- REPORTED BY --------------------------------------------------------- * Peter Clarke [8] -------- FIXED BY ------------------------------------------------------------ * Dave Reid [9] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Peter Wolanin [10] of the Drupal Security Team, and a module maintainer -------- 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/apachesolr [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/apachesolr [5] https://www.drupal.org/node/2627584 [6] https://www.drupal.org/node/2627582 [7] https://www.drupal.org/project/apachesolr [8] https://www.drupal.org/user/883708 [9] https://www.drupal.org/user/53892 [10] https://www.drupal.org/user/49851 [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

1 0

Chat Room - Moderately Critical - Access Bypass - SA-CONTRIB-2015-169
by security-news＠drupal.org 02 Dec '15

02 Dec '15

View online: https://www.drupal.org/node/2627478 * Advisory ID: DRUPAL-SA-CONTRIB-2015-169 * Project: Chat Room [1] (third-party module) * Version: 7.x * Date: 2015-December-02 * Security risk: 11/25 ( Moderately Critical) AC:Complex/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- Chat Room enables site owners to integrate chats into nodes by adding the chat room field to them. The module relies on a websocket connection to send chat messages to the client. The module doesn't sufficiently validate access before setting up the websocket. As a result, users may receive messages from chat rooms they don't have access to via the websocket. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Chat Room 7.x-2.x versions prior to 7.x-2.2. Drupal core is not affected. If you do not use the contributed Chat Room [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Chat Room module for Drupal 7.x, upgrade to Chat Room 7.x-2.2 [5] Also see the Chat Room [6] project page. -------- REPORTED BY --------------------------------------------------------- * Gergely Lekli [7] -------- FIXED BY ------------------------------------------------------------ * Gergely Lekli [8] -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [9] 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 [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [14] [1] https://www.drupal.org/project/chatroom [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/chatroom [5] https://www.drupal.org/node/2627428 [6] https://www.drupal.org/project/chatroom [7] https://www.drupal.org/user/930940 [8] https://www.drupal.org/user/930940 [9] https://www.drupal.org/user/36762 [10] https://www.drupal.org/contact [11] https://www.drupal.org/security-team [12] https://www.drupal.org/writing-secure-code [13] https://www.drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

Mollom - Critical - Access bypass - SA-CONTRIB-2015-168
by security-news＠drupal.org 02 Dec '15

02 Dec '15

View online: https://www.drupal.org/node/2627448 * Advisory ID: DRUPAL-SA-CONTRIB-2015-168 * Project: Mollom [1] (third-party module) * Version: 6.x * Date: 2015-December-02 * Security risk: 16/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The Mollom module allows users to protect their website from spam. As part of the spam protection, Mollom enables the website administrator to create a blacklist. When content is submitted that matches terms on the black list it will be automatically marked as spam and rejected per the site configuration. The module doesn't sufficiently check for access when accessing or modifying the blacklist for the site. This enables a potential attacker to add, update, or remove their own terms to a site-wide blacklist. The potential exists for an attacker to remove existing blacklist terms which could allow their content to be accepted onto the 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 --------------------------------------------------- * Mollom 6.x-2.x versions between 6.x-2.7 through 6.x-2.14. This does not affect the modules for Drupal 7 or Drupal 8. Drupal core is not affected. If you do not use the contributed Mollom [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Mollom module for Drupal 6.x, upgrade to Mollom 6.x-2.15 [5] Also see the Mollom [6] project page. -------- REPORTED BY --------------------------------------------------------- * Nick Veenhof [7], module maintainer -------- FIXED BY ------------------------------------------------------------ * Nick Veenhof [8], module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [9] 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 [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [14] [1] https://www.drupal.org/project/mollom [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/mollom [5] https://www.drupal.org/node/2626872 [6] https://www.drupal.org/project/mollom [7] https://www.drupal.org/user/122682 [8] https://www.drupal.org/user/122682 [9] https://www.drupal.org/user/2301194 [10] https://www.drupal.org/contact [11] https://www.drupal.org/security-team [12] https://www.drupal.org/writing-secure-code [13] https://www.drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

RESTful - Less Critical - Access bypass - SA-CONTRIB-2015-167
by security-news＠drupal.org 02 Dec '15

02 Dec '15

View online: https://www.drupal.org/node/2627444 * Advisory ID: DRUPAL-SA-CONTRIB-2015-167 * Project: RESTful [1] (third-party module) * Version: 7.x * Date: 2015-December-02 * Security risk: 8/25 ( Less Critical) AC:Complex/A:None/CI:None/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- RESTful module allows Drupal to be operated via RESTful HTTP requests, using best practices for security, performance, and usability. The module doesn't sufficiently validate some user input. Specific code could be run arbitrarily by an attacker in certain circumstances. This vulnerability is mitigated by the fact that only sites with a custom implementation of methods from a specific class are affected. Also, that custom code would need to affect data or impact the site in some way. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * RESTful 7.x-1.x versions prior to 7.x-1.6. Drupal core is not affected. If you do not use the contributed RESTful [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the RESTful 7.x-1.x module for Drupal 7.x, upgrade to RESTful 7.x-1.6 [5] Also see the RESTful [6] project page. -------- REPORTED BY --------------------------------------------------------- * Dan James [7] -------- FIXED BY ------------------------------------------------------------ * Mateu Aguiló Bosch [8], module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [9] 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 [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [14] [1] https://www.drupal.org/project/restful [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/restful [5] https://www.drupal.org/node/2627046 [6] https://www.drupal.org/project/restful [7] https://www.drupal.org/user/1147930 [8] https://www.drupal.org/u/e0ipso [9] https://www.drupal.org/u/pere-orga [10] https://www.drupal.org/contact [11] https://www.drupal.org/security-team [12] https://www.drupal.org/writing-secure-code [13] https://www.drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

Encrypt - Moderately Critical - Weak Encryption - SA-CONTRIB-2015-166
by security-news＠drupal.org 18 Nov '15

18 Nov '15

View online: https://www.drupal.org/node/2618362 * Advisory ID: DRUPAL-SA-CONTRIB-2015-166 * Project: Encrypt [1] (third-party module) * Version: 7.x * Date: 2015-November-18 * Security risk: 11/25 ( Moderately Critical) AC:Complex/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Weak Encryption -------- DESCRIPTION --------------------------------------------------------- This module enables you to encrypt data within Drupal using a user-configurable encryption method and key provider. The module did not sufficiently validate good configurations and api usage resulting in multiple potential weaknesses depending on module usage. The default encryption method could theoretically leak the key for known plaintexts. This vulnerability is mitigated by the fact that an attacker would need to have access to the encrypted data which is generally not possible without a breach of the database. The default key provider uses the Drupal private key, which means that it could potentially be leaked which puts other elements of the site at risk. This vulnerability is mitigated by requiring the default combination of encryption method and key provider for the Drupal private key to be potentially leaked. Users of the module are likely to employ a key of their own creation, rather than use the Drupal private key. Another encryption method included with the module uses a cipher that can leak structural information about the plaintext. This vulnerability is mitigated by the fact that it would only affect encryptions of large quantities of data, such as files and data of shorter lengths would not be affected. The default key created by the module is generated by a MD5 hash, which is not as strong as using truly random bytes of data. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Encrypt 7.x-2.x versions prior to 7.x-2.2. Drupal core is not affected. If you do not use the contributed Encrypt [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Encrypt module for Drupal 7.x, upgrade to Encrypt 7.x-2.2 [5] Once installed, review your settings and alter it to use a key provider and encryption method that is not deprecated. If data was encrypted with a deprecated key provider or encryption method then you should also re-encrypt all that data. Also see the Encrypt [6] project page. -------- REPORTED BY --------------------------------------------------------- * Heine Deelstra [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Rick Hawkins [8] the module maintainer * Greg Knaddison [9] of the Drupal Security Team * Heine Deelstra [10] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [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/encrypt [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/encrypt [5] https://www.drupal.org/node/2618254 [6] https://www.drupal.org/project/encrypt [7] https://www.drupal.org/user/17943 [8] https://www.drupal.org/user/352283 [9] https://www.drupal.org/user/36762 [10] https://www.drupal.org/user/17943 [11] https://www.drupal.org/user/36762 [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

1 0

UC Profile - Moderately Critical - Information Disclosure - SA-CONTRIB-2015-165
by security-news＠drupal.org 11 Nov '15

11 Nov '15

View online: https://www.drupal.org/node/2613444 * Advisory ID: DRUPAL-SA-CONTRIB-2015-165 * Project: UC Profile [1] (third-party module) * Version: 6.x * Date: 2015-November-11 * Security risk: 11/25 ( Moderately Critical) AC:Complex/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Information Disclosure -------- DESCRIPTION --------------------------------------------------------- UC Profile module enables you to collect profile fields for users during the checkout process of Ubercart as a checkout pane. The module doesn't sufficiently check access to profiles under certain circumstances. Depending on the information being collected, sensitive data may be exposed. This vulnerability is mitigated by the fact that only sites that store data to the anonymous user's profile are affected. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * UC Profile 6.x-1.x versions prior to 6.x-1.3 Drupal core is not affected. If you do not use the contributed UC Profile [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the UC Profile module for Drupal 6.x, upgrade to UC Profile 6.x-1.3 [5] Also see the UC Profile [6] project page. -------- REPORTED BY --------------------------------------------------------- * Will Long [7] -------- FIXED BY ------------------------------------------------------------ * Chris Wells [8], module maintainer * Patrick Corbett [9], module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [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/uc_profile [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/uc_profile [5] https://www.drupal.org/node/2612812 [6] https://www.drupal.org/project/uc_profile [7] https://www.drupal.org/user/1175666 [8] https://www.drupal.org/user/74392 [9] https://www.drupal.org/user/90604 [10] https://www.drupal.org/u/pere-orga [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

1 0

MAYO theme - Moderately Critical - Cross Site Scripting (XSS) - SA-CONTRIB-2015-164
by security-news＠drupal.org 11 Nov '15

11 Nov '15

View online: https://www.drupal.org/node/2613424 * Advisory ID: DRUPAL-SA-CONTRIB-2015-164 * Project: MAYO [1] (third-party theme) * Version: 7.x * Date: 2015-November-11 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- MAYO theme enables you to change certain theme settings via the administration interface. Some theme settings aren't sufficiently sanitized. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Administer themes". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * All MAYO 7.x-2.x versions prior to 7.x-2.6 * All MAYO 7.x-1.x versions prior to 7.x-1.4 Drupal core is not affected. If you do not use the contributed MAYO [4] theme, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the MAYO theme for Drupal 7.x-2.x, upgrade to MAYO 7.x-2.6 [5] * If you use the MAYO theme for Drupal 7.x-1.x, upgrade to MAYO 7.x-1.4 [6] Also see the MAYO [7] project page. -------- REPORTED BY --------------------------------------------------------- * Kisugi Ai [8] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * John Powell [9] the theme maintainer * Kisugi Ai [10] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [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/mayo [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/mayo [5] https://www.drupal.org/node/2613048 [6] https://www.drupal.org/node/2613046 [7] https://www.drupal.org/project/mayo [8] https://www.drupal.org/user/1284976 [9] https://www.drupal.org/user/797068 [10] https://www.drupal.org/user/1284976 [11] https://www.drupal.org/u/pere-orga [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

1 0