- Security-news - lists.drupal.org

Nodejs - Access bypass - Moderately Critical -- DRUPAL-SA-CONTRIB-2016-007
by security-news＠drupal.org 17 Feb '16

17 Feb '16

View online: https://www.drupal.org/node/2670636 * Advisory ID: DRUPAL-SA-CONTRIB-2016-007 * Project: Node.js integration [1] (third-party module) * Version: 7.x, 8.x * Date: 2016-February-17 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:All [2] * Vulnerability: Information Disclosure -------- DESCRIPTION --------------------------------------------------------- This module provides an API that other modules can use to add realtime capabilities to Drupal, specifically enabling pushing updates to open connected clients. The module doesn't disconnect unauthenticated sockets, allowing those sockets to receive broadcast messages. For sites that only serve authenticated pages, or only allows Node.js connections from authenticated users, the expectation is that only authenticated Drupal users will see broadcast messages. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Node.js 7.x-1.x versions prior to 7.x-1.11. * Node.js 8.x-1.x beta versions prior to 8.x-1.0. Drupal core is not affected. If you do not use the contributed Node.js integration [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Node.js module for Drupal 7.x, upgrade to Node.js 7.x-1.11. [5] * If you use the beta Node.js module for Drupal 8.x, upgrade to Node.js 8.x-1.0. [6] Also see the Node.js integration [7] project page. -------- REPORTED BY --------------------------------------------------------- * Justin Randell [8]. -------- FIXED BY ------------------------------------------------------------ * Justin Randell [9]. * Gergely Lekli [10]. -------- 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/nodejs [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/nodejs [5] https://www.drupal.org/node/2669222 [6] https://www.drupal.org/node/2669224 [7] https://www.drupal.org/project/nodejs [8] https://www.drupal.org/u/beejeebus [9] https://www.drupal.org/u/beejeebus [10] https://www.drupal.org/u/gergely-lekli [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

1 0

Commerce Authorize.Net SIM/DPM Payment Methods - Access Bypass - DRUPAL-SA-CONTRIB-2016-006
by security-news＠drupal.org 17 Feb '16

17 Feb '16

View online: https://www.drupal.org/node/2670632 * Advisory ID: DRUPAL-SA-CONTRIB-2016-006 * Project: Commerce Authorize.Net SIM/DPM Payment Methods [1] (third-party module) * Version: 7.x * Date: 2016-February-17 * Security risk: 15/25 ( Critical) AC:Complex/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to make credit card payments for Drupal Commerce orders via the Authorize.Net payment gateway using either their SIM (hosted payment page) or DPM (direct post method) mechanisms. The module doesn't sufficiently protect against the premature triggering of order completion without successful payment by the manual entry of a specially-constructed URL which contains the correct payment redirect key. This vulnerability is mitigated by the fact that an attacker must know the format of the redirect URL and the current payment redirect key. It's also worth noting that orders prematurely completed in this fashion will *NOT* record a successful payment and thus show an unpaid balance. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Commerce Authorize.Net SIM/DPM Payment Methods versions prior to 7.x-1.4. Drupal core is not affected. If you do not use the contributed Commerce Authorize.Net SIM/DPM Payment Methods [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Commerce Authorize.Net SIM/DPM Payment Methods module for Drupal 7.x, upgrade to Commerce Authorize.Net SIM/DPM Payment Methods 7.x-1.4 [5] Also see the Commerce Authorize.Net SIM/DPM Payment Methods [6] project page. -------- REPORTED BY --------------------------------------------------------- * Matt White [7] -------- FIXED BY ------------------------------------------------------------ * Matt White [8] * Jerry Hudgins [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Rick Manelius [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/commerce_authnet_simdpm [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/commerce_authnet_simdpm [5] https://www.drupal.org/node/2670212 [6] https://www.drupal.org/project/commerce_authnet_simdpm [7] https://www.drupal.org/user/266840 [8] https://www.drupal.org/user/266840 [9] https://www.drupal.org/user/96266 [10] https://www.drupal.org/user/680072 [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

CAS - Moderately Critical - Information Disclosure - DRUPAL-SA-CONTRIB-2016-005
by security-news＠drupal.org 10 Feb '16

10 Feb '16

View online: https://www.drupal.org/node/2666448 * Advisory ID: DRUPAL-SA-CONTRIB-2014-0XX * Project: CAS [1] (third-party module) * Version: 7.x * Date: 2016-February-10 * Security risk: 12/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:None/E:Proof/TD:All [2] * Vulnerability: Information Disclosure -------- DESCRIPTION --------------------------------------------------------- This module enables you to use your Drupal site as a client or server for the single sign on protocol CAS. This vulnerability only affects sites that use the "CAS Server" sub module. The module doesn't allow an administrator to restrict which CAS clients are allowed authenticate with the Drupal CAS server. A malicious CAS client can trick your users into exposing information about themselves, including: username, uid, email, account created date, account language, and roles. This vulnerability is mitigated by the fact that a user must click a specially formed link from the malicious site and log into your Drupal CAS server with their credentials. If the user already has an active session with your Drupal CAS server, then that step is skipped. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * CAS 7.x-1.x versions prior to 7.x-1.5. Drupal core is not affected. If you do not use the contributed CAS [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you are using the CAS Server sub-module, upgrade to CAS 7.x-1.5 [5] and configure the "white list" of accepted CAS clients that are allowed to authenticate with your CAS server. * If you use the CAS module but NOT the server sub-module, then do nothing. Also see the CAS [6] project page. -------- REPORTED BY --------------------------------------------------------- * GUSTAV0 [7] -------- FIXED BY ------------------------------------------------------------ * Brian Osborne [8] the module maintainer * Robert Wohleb [9] * Olarin [10] -------- 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/cas [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/cas [5] https://drupal.org/node/2665642 [6] https://www.drupal.org/project/cas [7] https://www.drupal.org/u/gustav0 [8] https://www.drupal.org/user/XXXUID [9] https://www.drupal.org/u/rwohleb [10] https://www.drupal.org/u/olarin [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

1 0

Embedded Media Field - Moderately Critical - Access Bypass - DRUPAL-SA-CONTRIB-2016-004
by security-news＠drupal.org 10 Feb '16

10 Feb '16

View online: https://www.drupal.org/node/2666446 * Advisory ID: DRUPAL-SA-CONTRIB-2016-pending * Project: Embedded Media Field [1] (third-party module) * Version: 6.x * Date: 2016-February-10 * Security risk: 19/25 ( Critical) AC:Complex/A:None/CI:All/II:All/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module enables you to to display video, image, and audio files from various third party providers The module doesn't sufficiently sanitize path arguments under certain scenarios. This vulnerability is mitigated by the fact that an attacker must be able to trick an administrator into visiting a carefully crafted URL. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Embedded Media Field 6.x-1.x all versions. * Embedded Media Field 6.x-2.x versions prior to 6.x-2.7. Versions of Embedded Media Field for Drupal 7 are not affected. Drupal core is not affected. If you do not use the contributed Embedded Media Field [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Embedded Media Field module for Drupal 6.x, upgrade to Embedded Media Field 6.x-2.7 [5] Also see the Embedded Media Field [6] project page. -------- REPORTED BY --------------------------------------------------------- * Cash Williams (cashwilliams) [7] -------- FIXED BY ------------------------------------------------------------ * Dave Hansen-Lange (dalin) [8] -------- COORDINATED BY ------------------------------------------------------ * Michael Hess [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/emfield [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/emfield [5] https://www.drupal.org/node/2665632 [6] https://www.drupal.org/project/emfield [7] https://www.drupal.org/u/cashwilliams [8] https://www.drupal.org/u/dalin [9] https://www.drupal.org/u/mlhess [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

Open Atrium - Moderately Critical - Access Bypass - SA-CONTRIB-2016-003
by security-news＠drupal.org 27 Jan '16

27 Jan '16

View online: https://www.drupal.org/node/2657654 * Advisory ID: DRUPAL-SA-CONTRIB-2016-003 * Project: Open Atrium [1] (third-party module) * Version: 7.x * Date: 2016-January-27 * Security risk: 13/25 ( Moderately Critical) AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- Open Atrium allows you to control access via a hierarchy of public and private spaces and sub-spaces. If a public sub-space is created within a private parent-space, the content nodes of the public sub-space are accessible to users who are not members of the parent private space. This issue only affects sites that use private sub-spaces. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Open Atrium 7.x-2.x versions prior to 7.x-2.53. Drupal core is not affected. If you do not use the contributed Open Atrium [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ * Upgrade to the latest version, 7.x-2.53 [5] If you are not able to fully upgrade to the latest version, ensure private sub-spaces are directly marked as private and are not seen publicly in a private parent space. Also see the Open Atrium [6] project page. -------- REPORTED BY --------------------------------------------------------- * Mike Potter [7], Open Atrium maintainer. -------- FIXED BY ------------------------------------------------------------ * Mike Potter [8], Open Atrium maintainer. * Scott Henry [9], Open Atrium co-maintainer. -------- COORDINATED BY ------------------------------------------------------ * Hunter Fox [10] of the Drupal Security Team * Ben Jeavons [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/openatrium [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/openatrium [5] https://www.drupal.org/node/2657640 [6] https://www.drupal.org/project/openatrium [7] https://www.drupal.org/u/mpotter [8] https://www.drupal.org/u/mpotter [9] https://www.drupal.org/u/scottalan [10] https://www.drupal.org/user/426416 [11] https://www.drupal.org/u/coltrane [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

RedHen CRM - Moderately Critical - Cross Site Scripting (XSS) - SA-CONTRIB-2016-002
by security-news＠drupal.org 13 Jan '16

13 Jan '16

View online: https://www.drupal.org/node/2649800 * Advisory ID: DRUPAL-SA-CONTRIB-2016-002 * Project: RedHen CRM [1] (third-party module) * Version: 7.x * Date: 2016-January-13 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Redhen set of modules allows you to build a CRM features in a Drupal site. When rendering individual Contacts, this module does not properly filter the certain data prior to display. When rendering listing of notes or engagement scores, these modules do not properly filter certain data before display. This vulnerability is mitigated by the fact that an attacker must have an authenticated user account with access to edit a contact, administer engagement scores, or administer taxonomies. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Redhen 7.x-1.x versions prior to 7.x-1.11. Drupal core is not affected. If you do not use the contributed RedHen CRM [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the RedHen module for Drupal 7.x, upgrade to Redhen 7.x-1.11 [5] Workaround (if you are unable to update the module immediately): * In the display settings for your Redhen Contact Types (admin/structure/redhen/contact_types), hide "name" on all display modes. * Restrict access to "Administer Engagement Scores" and "Administer Taxonomies" to trusted users. Also see the RedHen CRM [6] project page. -------- REPORTED BY --------------------------------------------------------- * Mikko Rantanen [7] * Gabe Carleton-Barnes [8], a module maintainer * Greg Knaddison [9] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Jaymz Rhime [10], a module maintainer * Gabe Carleton-Barnes [11], a module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [12] 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 [13]. Learn more about the Drupal Security team and their policies [14], writing secure code for Drupal [15], and securing your site [16]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [17] [1] https://www.drupal.org/project/redhen [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/redhen [5] https://www.drupal.org/node/2649780 [6] https://www.drupal.org/project/redhen [7] https://www.drupal.org/user/1004738 [8] https://www.drupal.org/user/1682976 [9] https://www.drupal.org/user/36762 [10] https://www.drupal.org/user/3181097 [11] https://www.drupal.org/user/1682976 [12] https://www.drupal.org/user/36762 [13] https://www.drupal.org/contact [14] https://www.drupal.org/security-team [15] https://www.drupal.org/writing-secure-code [16] https://www.drupal.org/security/secure-configuration [17] https://twitter.com/drupalsecurity

1 0

Field Group - Moderately Critical - Cross Site Scripting (XSS) - SA-CONTRIB-2016-001
by security-news＠drupal.org 06 Jan '16

06 Jan '16

View online: https://www.drupal.org/node/2645350 * Advisory ID: DRUPAL-SA-CONTRIB-2016-001 * Project: Field Group [1] (third-party module) * Version: 7.x * Date: 2016-January-06 * Security risk: 12/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Field Group module enables you to group fields on entity forms and entity displays. When adding a HTML element as group, the user has the option to add custom HTML attributes on the group. Via this option, a malicious user can embed scripts within the page, resulting in a Cross-site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker has to be able to configure field display settings, which usually needs a higher level permission such as /Administer vocabularies and terms/. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Field Group 7.x-1.x versions prior to 7.x-1.5. Drupal core is not affected. If you do not use the contributed Field Group [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Field Group module for Drupal 7.x, upgrade to Field Group 7.x-1.5 [5] Also see the Field Group [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Nils Destoop [8], module maintainer * Pere Orga [9] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * David Snopek [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/field_group [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/field_group [5] https://www.drupal.org/node/2644832 [6] https://www.drupal.org/project/field_group [7] https://www.drupal.org/u/pere-orga [8] https://www.drupal.org/user/361625 [9] https://www.drupal.org/u/pere-orga [10] https://www.drupal.org/user/266527 [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

Block Class- Critical - Cross Site Scripting (XSS) - SA-CONTRIB-2015-175
by security-news＠drupal.org 16 Dec '15

16 Dec '15

View online: https://www.drupal.org/node/2636502 * Advisory ID: DRUPAL-SA-CONTRIB-2015-175 * Project: Block Class [1] (third-party module) * Version: 7.x * Date: 2015-December-16 * Security risk: 19/25 ( Critical) AC:None/A:Admin/CI:All/II:All/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module enables you to add custom classes to blocks. The module doesn't sufficiently scrub class names written by a malicious block class administrator. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Administer block classes". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * block_class 7.x-2.x versions prior to 7.x-2.2. Drupal core is not affected. If you do not use the contributed Block Class [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the block_class module for Drupal 7.x, upgrade to block_class 7.x-2.2 [5] Also see the Block Class [6] project page. -------- REPORTED BY --------------------------------------------------------- * Neil Drumm [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Berend de Boer [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Ben Dougherty [9] of the Drupal Security Team * Owen Barton [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/block_class [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/block_class [5] https://www.drupal.org/node/2636498 [6] https://www.drupal.org/project/block_class [7] https://www.drupal.org/user/23 [8] https://www.drupal.org/user/143552 [9] https://www.drupal.org/user/1852732 [10] https://www.drupal.org/user/19668 [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

Open Atrium - Critical - Cross Site Scripting (XSS) - SA-CONTRIB-2015-174
by security-news＠drupal.org 16 Dec '15

16 Dec '15

View online: https://www.drupal.org/node/2636380 * Advisory ID: DRUPAL-SA-CONTRIB-2015-174 * Project: Open Atrium [1] (third-party module) * Version: 7.x * Date: 2015-December-16 * Security risk: 17/25 ( Critical) AC:None/A:None/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Open Atrium distribution enables you to create an intranet. Open Atrium Core module doesn't sufficiently sanitize some user supplied text, leading to a reflected Cross Site Scripting vulnerability (XSS). -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Open Atrium distribution 7.x-2.x versions prior to 7.x-2.51 * Open Atrium Core module 7.x-2.x versions prior to 7.x-2.66 Drupal core is not affected. If you do not use the contributed Open Atrium [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Open Atrium distribution for Drupal 7.x: * Upgrade to Open Atrium 7.x-2.51 If you use the Open Atrium Core module for Drupal 7.x: * Upgrade to Open Atrium Core 7.x-2.66 [5] Also see the Open Atrium [6] project page. -------- REPORTED BY --------------------------------------------------------- * kris84 [7] * jbylsma [8] -------- FIXED BY ------------------------------------------------------------ * kris84 [9] * Mike Potter [10], a module maintainer -------- 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/openatrium [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/openatrium [5] https://www.drupal.org/node/2636350 [6] https://www.drupal.org/project/openatrium [7] https://www.drupal.org/user/142812 [8] https://www.drupal.org/u/jbylsma [9] https://www.drupal.org/user/142812 [10] https://www.drupal.org/user/616192 [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

Select2 Field Widget - Critical - Cross Site Scripting (XSS) - SA-CONTRIB-2015-173
by security-news＠drupal.org 16 Dec '15

16 Dec '15

View online: https://www.drupal.org/node/2636352 * Advisory ID: DRUPAL-SA-CONTRIB-2015-173 * Project: Select2 Field Widget [1] (third-party module) * Version: 7.x * Date: 2015-December-16 * Security risk: 17/25 ( Critical) AC:None/A:None/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Select2 Field Widget module enables you to use the select2 library for field widgets. The module doesn't sufficiently sanitize some user supplied text, leading to a reflected Cross Site Scripting vulnerability (XSS). -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Select2 Field Widget 7.x-2.x versions prior to 7.x-2.8. Drupal core is not affected. If you do not use the contributed Select2 Field Widget [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Select2 Field Widget module for Drupal 7.x, upgrade to Select2 Field Widget 7.x-2.9 [5] Also see the Select2 Field Widget [6] project page. -------- REPORTED BY --------------------------------------------------------- * kris84 [7] * jbylsma [8] -------- FIXED BY ------------------------------------------------------------ * kris84 [9] * Zoltán Kisgyörgy [10], module maintainer * Zoltan Keresztes [11], module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [12] 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 [13]. Learn more about the Drupal Security team and their policies [14], writing secure code for Drupal [15], and securing your site [16]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [17] [1] https://www.drupal.org/project/select2widget [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/select2widget [5] https://www.drupal.org/node/2636114 [6] https://www.drupal.org/project/select2widget [7] https://www.drupal.org/user/142812 [8] https://www.drupal.org/u/jbylsma [9] https://www.drupal.org/user/142812 [10] https://www.drupal.org/u/k_zoltan [11] https://www.drupal.org/user/2768895 [12] https://www.drupal.org/user/2301194 [13] https://www.drupal.org/contact [14] https://www.drupal.org/security-team [15] https://www.drupal.org/writing-secure-code [16] https://www.drupal.org/security/secure-configuration [17] https://twitter.com/drupalsecurity

1 0