Security-news February 2015

security-news@drupal.org

1 participants
29 discussions

SA-CONTRIB-2015-042 - Node basket - Multiple vulnerabilities - Unsupported
by security-news＠drupal.org 11 Feb '15

11 Feb '15

View online: https://www.drupal.org/node/2424419 * Advisory ID: DRUPAL-SA-CONTRIB-2015-042 * Project: Node basket [1] (third-party module) * Version: 6.x * Date: 2015-February-11 * Security risk: 16/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting, Cross Site Request Forgery, Open Redirect, Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- Node basket module enables you to pick up nodes in a basket. The module doesn't sufficiently sanitize user supplied text in some pages, thereby exposing a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a user with permission to create/edit nodes. Also, the module has CSRF vulnerabilities. A malicious user can cause another user to add/remove nodes of the basket by getting his browser to make a request to a specially-crafted URL. Also, the module has an Open Redirect vulnerability. -------- 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 versions of Node basket module. Drupal core is not affected. If you do not use the contributed Node basket [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Node basket module you should uninstall it. Also see the Node basket [5] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [7] 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 [8]. Learn more about the Drupal Security team and their policies [9], writing secure code for Drupal [10], and securing your site [11]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [12] [1] https://www.drupal.org/project/node_basket [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/node_basket [5] https://www.drupal.org/project/node_basket [6] https://www.drupal.org/user/2301194 [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/contact [9] https://www.drupal.org/security-team [10] https://www.drupal.org/writing-secure-code [11] https://www.drupal.org/security/secure-configuration [12] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-041 - Feature Set - Cross Site Request Forgery (CSRF) - Unsupported
by security-news＠drupal.org 11 Feb '15

11 Feb '15

View online: https://www.drupal.org/node/2424409 * Advisory ID: DRUPAL-SA-CONTRIB-2015-041 * Project: Feature Set [1] (third-party module) * Version: 7.x * Date: 2015-February-11 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:None/CI:None/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- Feature Set module enables you to enable or disable sets of features or modules. The module doesn't sufficiently protect some URLs against CSRF. A malicious user can cause an administrator to enable and disable modules by getting the administrator's browser to make a request to a specially-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 --------------------------------------------------- * All versions of Feature Set module. Drupal core is not affected. If you do not use the contributed Feature Set [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Feature Set module you should uninstall it. Also see the Feature Set [5] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [7] 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 [8]. Learn more about the Drupal Security team and their policies [9], writing secure code for Drupal [10], and securing your site [11]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [12] [1] https://www.drupal.org/project/feature_set [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/feature_set [5] https://www.drupal.org/project/feature_set [6] https://www.drupal.org/user/2301194 [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/contact [9] https://www.drupal.org/security-team [10] https://www.drupal.org/writing-secure-code [11] https://www.drupal.org/security/secure-configuration [12] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-040 - Webform prepopulate block - Cross Site Scripting (XSS)
by security-news＠drupal.org 11 Feb '15

11 Feb '15

View online: https://www.drupal.org/node/2424405 * Advisory ID: DRUPAL-SA-CONTRIB-2015-040 * Project: Webform prepopulate block [1] (third-party module) * Version: 7.x * Date: 2015-February-11 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Webform prepopulate block module enables you to set a webform component to display in a separated block. The module doesn't sufficiently sanitize user supplied text when displaying the block, thereby exposing a Cross Site Scripting vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with permission to create or edit nodes. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Webform prepopulate block 7.x-3.0 Drupal core is not affected. If you do not use the contributed Webform prepopulate block [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Webform prepopulate block module for Drupal 7.x, upgrade to Webform prepopulate block 7.x-3.1 [5] Also see the Webform prepopulate block [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Gabor Szanto [8] the 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/webform_prepopulate_block [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/webform_prepopulate_block [5] https://www.drupal.org/node/2423681 [6] https://www.drupal.org/project/webform_prepopulate_block [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/610310 [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

SA-CONTRIB-2015-039 - Views - Multiple vulnerabilities
by security-news＠drupal.org 11 Feb '15

11 Feb '15

View online: https://www.drupal.org/node/2424403 * Advisory ID: DRUPAL-SA-CONTRIB-2015-039 * Project: Views [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-February-11 * Security risk: 8/25 ( Less Critical) AC:Basic/A:Admin/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] * Vulnerability: Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- The Views module provides a flexible method for Drupal site designers to control how lists and tables of content, users, taxonomy terms and other data are presented. .... Open redirect vulnerability The module does not sanitize user provided URLs when processing the page to break the lock on Views being edited, thereby exposing an open redirect attack vector. This vulnerability is mitigated by the fact that the Views UI submodule must be enabled. .... Access bypass vulnerability The module does not protect the default Views configurations that ship with the module sufficiently, thereby exposing possibly protected information to unprivileged users. This vulnerability is mitigated by the fact that it only affects sites that have not granted the common "access content" or "access comments" permission to untrusted users. Furthermore, these default views configurations are disabled by default and must be enabled by an administrator. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Views 6.x-2.x versions prior to 6.x-2.18. * Views 6.x-3.x versions prior to 6.x-3.2. * Views 7.x-3.x versions prior to 7.x-3.10. Drupal core is not affected. If you do not use the contributed Views [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Views module for Drupal 6.x, upgrade to Views 6.x-2.18 [5] or Views 6.x-3.2 [6] * If you use the Views module for Drupal 7.x, upgrade to Views 7.x-3.10 [7] Also see the Views [8] project page. -------- REPORTED BY --------------------------------------------------------- * Open Redirect: Klaus Purer [9] of the Drupal Security Team * Access bypass: Daniel Wehner [10] the module maintainer -------- FIXED BY ------------------------------------------------------------ * Daniel Wehner [11] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [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/views [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/views [5] https://www.drupal.org/node/2424101 [6] https://www.drupal.org/node/2424097 [7] https://www.drupal.org/node/2424103 [8] https://www.drupal.org/project/views [9] https://www.drupal.org/u/klausi [10] https://www.drupal.org/u/dawehner [11] https://www.drupal.org/u/dawehner [12] https://www.drupal.org/u/klausi [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

SA-CONTRIB-2015-038 - Facebook Album Fetcher - Cross Site Scripting (XSS) - Unsupported
by security-news＠drupal.org 04 Feb '15

04 Feb '15

View online: https://www.drupal.org/node/2420161 * Advisory ID: DRUPAL-SA-CONTRIB-2015-038 * Project: Facebook Album Fetcher [1] (third-party module) * Version: 7.x * Date: 2015-February-04 * Security risk: 12/25 ( Moderately Critical) AC:Complex/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Facebook Album Fetcher module allows you to fetch Facebook albums from a Facebook account. The module incorrectly prints fields without proper sanitization thereby exposing a Cross Site Scripting vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "access administration pages". -------- 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 versions of Facebook Album Fetcher. Drupal core is not affected. If you do not use the contributed Facebook Album Fetcher [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Facebook Album Fetcher module you should uninstall it. Also see the Facebook Album Fetcher [5] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [7] of the Drupal Security Team * Rick Manelius [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/facebook_album_fetcher [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/facebook_album_fetcher [5] https://www.drupal.org/project/facebook_album_fetcher [6] https://www.drupal.org/user/2301194 [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/680072 [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

SA-CONTRIB-2015-037 - Path Breadcrumbs - Access Bypass
by security-news＠drupal.org 04 Feb '15

04 Feb '15

View online: https://www.drupal.org/node/2420139 * Advisory ID: DRUPAL-SA-CONTRIB-2015-037 * Project: Path Breadcrumbs [1] (third-party module) * Version: 7.x * Date: 2015-February-04 * Security risk: 12/25 ( Moderately Critical) AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to configure breadcrumbs for any Drupal page. The module doesn't check node access on 403 Not Found pages. As a result, unpublished content data can be shown to unprivileged user. This vulnerability is mitigated by the fact that it is possible to configure proper access control in Path Breadcrumbs items with “Selection Rules” from the UI. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Path Breadcrumbs 7.x-3.x versions prior to 7.x-3.2 Drupal core is not affected. If you do not use the contributed Path Breadcrumbs [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Path Breadcrumbs module for Drupal 7.x, upgrade to Path Breadcrumbs 7.x-3.2 [5] Also see the Path Breadcrumbs [6] project page. -------- REPORTED BY --------------------------------------------------------- * Nicholas Thompson [7] -------- FIXED BY ------------------------------------------------------------ * Kate Marshalkina [8] and Evgeniy Maslovskiy [9], the module maintainers -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [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/path_breadcrumbs [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/path_breadcrumbs [5] https://www.drupal.org/node/2420121 [6] https://www.drupal.org/project/path_breadcrumbs [7] https://www.drupal.org/user/59351 [8] https://www.drupal.org/u/kalabro [9] https://www.drupal.org/user/810676 [10] https://www.drupal.org/u/greggles [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

SA-CONTRIB-2015-036 - Public Download Count - Cross Site Scripting (XSS) - Unsupported
by security-news＠drupal.org 04 Feb '15

04 Feb '15

View online: https://www.drupal.org/node/2420119 * Advisory ID: DRUPAL-SA-CONTRIB-2015-036 * Project: Public Download Count [1] (third-party module) * Version: 7.x * Date: 2015-February-04 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Public Download Count module keeps track of file download counts. The module doesn't sufficiently sanitize user supplied text in the Download counts report page thereby exposing a Cross Site Scripting vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with permission to create or edit nodes. -------- 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 versions of Public Download Count module. Drupal core is not affected. If you do not use the contributed Public Download Count [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Public Download Count module you should uninstall it. Also see the Public Download Count [5] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [7] 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 [8]. Learn more about the Drupal Security team and their policies [9], writing secure code for Drupal [10], and securing your site [11]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [12] [1] https://www.drupal.org/project/pubdlcnt [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/pubdlcnt [5] https://www.drupal.org/project/pubdlcnt [6] https://www.drupal.org/user/2301194 [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/contact [9] https://www.drupal.org/security-team [10] https://www.drupal.org/writing-secure-code [11] https://www.drupal.org/security/secure-configuration [12] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-035 - Ajax Timeline - Cross Site Scripting (XSS)
by security-news＠drupal.org 04 Feb '15

04 Feb '15

View online: https://www.drupal.org/node/2420099 * Advisory ID: DRUPAL-SA-CONTRIB-2015-035 * Project: Ajax Timeline [1] (third-party module) * Version: 7.x * Date: 2015-February-04 * Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Ajax Timeline module enables you to display a vertical timeline of nodes based off a date field or created date of the configured nodes. The module doesn't sufficiently escape node titles when displaying the timeline, allowing a malicious user to inject code. This vulnerability is mitigated by the fact that an attacker must have a role with permission to create or edit nodes of the type configured for the timeline. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Ajax Timeline 7.x-1.x versions prior to 7.x-1.1. Drupal core is not affected. If you do not use the contributed Ajax Timeline [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Ajax Timeline module for Drupal 7.x, upgrade to Ajax Timeline 7.x-1.1 [5]. Also see the Ajax Timeline [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Bryan Sharpe [8] the 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/ajax_timeline [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/ajax_timeline [5] https://www.drupal.org/node/2419971 [6] https://www.drupal.org/project/ajax_timeline [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/2512258 [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

SA-CONTRIB-2015-034 - Commerce WeDeal - Open Redirect
by security-news＠drupal.org 04 Feb '15

04 Feb '15

View online: https://www.drupal.org/node/2420089 * Advisory ID: DRUPAL-SA-CONTRIB-2015-034 * Project: Commerce WeDeal [1] (third-party module) * Version: 7.x * Date: 2015-February-04 * Security risk: 10/25 ( Moderately Critical) AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:All [2] * Vulnerability: Open Redirect -------- DESCRIPTION --------------------------------------------------------- Commerce WeDeal module enables you to do Commerce payments through the payment provider WeDeal. The module doesn't sufficiently check a query parameter used for page redirection, thereby leading to an Open Redirect vulnerability. -------- 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 WeDeal 7.x-1.x versions prior to 7.x-1.3. Drupal core is not affected. If you do not use the contributed Commerce WeDeal [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Commerce WeDeal module for Drupal 7.x, upgrade to Commerce WeDeal 7.x-1.3 [5] Also see the Commerce WeDeal [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Jeroen Bobbeldijk [8] the 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/commerce_wedeal [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/commerce_wedeal [5] https://www.drupal.org/node/2419483 [6] https://www.drupal.org/project/commerce_wedeal [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/1853532 [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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Security-news February 2015