Security-news

security-news@drupal.org

1 participants
1782 discussions

SA-CONTRIB-2015-074 - Site Documentation - Cross Site Scripting (XSS)
by security-news＠drupal.org 11 Mar '15

11 Mar '15

View online: https://www.drupal.org/node/2450387 * Advisory ID: DRUPAL-SA-CONTRIB-2015-074 * Project: Site Documentation [1] (third-party module) * Version: 6.x * Date: 2015-March-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 --------------------------------------------------------- Site Documentation module enables you to display detailed configuration information. The module doesn't sufficiently sanitize user supplied text in some pages, thereby exposing a Cross Site Scripting vulnerability. This vulnerability is mitigated by the fact that an attacker must have a user with permission to create/edit taxonomy 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 --------------------------------------------------- * Site Documentation 6.x-1.x versions prior to 6.x-1.5. Drupal core is not affected. If you do not use the contributed Site Documentation [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Site Documentation module for Drupal 6.x, upgrade to Site Documentation 6.x-1.5 [5] Also see the Site Documentation [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Nancy Wichmann [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/sitedoc [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/sitedoc [5] https://www.drupal.org/node/2450321 [6] https://www.drupal.org/project/sitedoc [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/101412 [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-073 - Trick Question - Cross Site Scripting (XSS)
by security-news＠drupal.org 04 Mar '15

04 Mar '15

View online: https://www.drupal.org/node/2446065 * Advisory ID: DRUPAL-SA-CONTRIB-2015-073 * Project: Trick Question [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-March-04 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Trick Question is a CAPTCHA-type spam prevention module; a lightweight, compact and simple alternative to larger and more complex modules. The module doesn't sufficiently sanitize user supplied text in some pages, thereby exposing a Cross Site Scripting vulnerability. The vulnerability is mitigated by the fact that an attacker must have the "Administer Trick Question" permission. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Trick Question 6.x-1.x versions prior to 6.x-1.5 * Trick Question 7.x-1.x versions prior to 7.x-1.5 Drupal core is not affected. If you do not use the contributed Trick Question [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Trick Question module for Drupal 6.x, upgrade to Trick Question 6.x-1.5 [5] * If you use the Trick Question module for Drupal 7.x, upgrade to Trick Question 7.x-1.5 [6] Also see the Trick Question [7] project page. -------- REPORTED BY --------------------------------------------------------- * Matt Vance [8] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Martin Joergensen [9] the module maintainer * Matt Vance [10] provisional member of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Matt Vance [11] provisional member 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/trick_question [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/trick_question [5] https://www.drupal.org/node/2373143 [6] https://www.drupal.org/node/2373147 [7] https://www.drupal.org/project/trick_question [8] https://www.drupal.org/user/88338 [9] https://www.drupal.org/user/81257 [10] https://www.drupal.org/user/88338 [11] https://www.drupal.org/user/88338 [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

SA-CONTRIB-2015-072 - Commerce Ogone - Access bypass
by security-news＠drupal.org 04 Mar '15

04 Mar '15

View online: https://www.drupal.org/node/2446051 * Advisory ID: DRUPAL-SA-CONTRIB-2015-072 * Project: Commerce Ogone [1] (third-party module) * Version: 7.x * Date: 2015-March-04 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:None/CI:None/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to use Ogone (Ingenico) as a payment method for Drupal Commerce. Malicious users can trick Commerce Ogone into proceeding with the checkout process without actually going through the Ogone payment process, causing the order status to be set to checkout complete, even though no payment was processed. The vulnerability is mitigated by the fact that the balance to be paid on affected orders remains the full amount, and no payment transaction is linked to the order. -------- 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 Ogone 7.x-1.x versions prior to 7.x-1.5. Drupal core is not affected. If you do not use the contributed Commerce Ogone [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Commerce Ogone module for Drupal 7.x, upgrade to Commerce Ogone 7.x-1.5 [5] Also see the Commerce Ogone [6] project page. -------- REPORTED BY --------------------------------------------------------- * Mathieu Massebœuf [7] -------- FIXED BY ------------------------------------------------------------ * Mathieu Massebœuf [8] * Ivo Van Geertruyen [9] of the Drupal Security Team and module co-maintainer -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [10] of the Drupal Security Team * 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/commerce_ogone [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/commerce_ogone [5] https://www.drupal.org/node/2445835 [6] https://www.drupal.org/project/commerce_ogone [7] https://www.drupal.org/user/974302 [8] https://www.drupal.org/user/974302 [9] https://www.drupal.org/user/383424 [10] https://www.drupal.org/user/262198 [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

SA-CONTRIB-2015-071 - Simple Subscription - Cross Site Scripting (XSS)
by security-news＠drupal.org 04 Mar '15

04 Mar '15

View online: https://www.drupal.org/node/2446019 * Advisory ID: DRUPAL-SA-CONTRIB-2015-071 * Project: Simple subscription [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-March-04 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module enables you to add a block to allow visitors to subscribe to a site's newsletter. The module failed to sanitize some block content, leading to a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer blocks". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Simple Subscription 6.x-1.x versions prior to 6.x-1.1. * Simple Subscription 7.x-1.x versions prior to 7.x-1.1. Drupal core is not affected. If you do not use the contributed Simple Subscription [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Simple Subscription module for Drupal 6.x, upgrade to Simple Subscription 6.x-1.1 [5] * If you use the Simple Subscription module in branch 7.x-1.x for Drupal 7.x, upgrade to Simple Subscription 7.x-1.1 [6] * If you use the Simple Subscription module in branch 7.x-2.x for Drupal 7.x, there is nothing to do, this branch is secure Also see the Simple Subscription [7] project page. -------- REPORTED BY --------------------------------------------------------- * Matt Vance [8] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Matt Vance [9] provisional member of the Drupal Security Team * SebCorbin [10] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Michael Hess [11] of the Drupal Security Team * Matt Vance [12] provisional member of the Drupal Security Team * Aaron Ott [13] provisional member 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 [14]. Learn more about the Drupal Security team and their policies [15], writing secure code for Drupal [16], and securing your site [17]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [18] [1] https://www.drupal.org/project/simple_subscription [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/simple_subscription [5] https://www.drupal.org/node/2437931 [6] https://www.drupal.org/node/2437933 [7] https://www.drupal.org/project/simple_subscription [8] https://www.drupal.org/user/88338 [9] https://www.drupal.org/user/88338 [10] https://www.drupal.org/user/412171 [11] https://security.drupal.org/user/14049 [12] https://www.drupal.org/user/88338 [13] https://www.drupal.org/user/154069 [14] https://www.drupal.org/contact [15] https://www.drupal.org/security-team [16] https://www.drupal.org/writing-secure-code [17] https://www.drupal.org/security/secure-configuration [18] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-070 - Mover - Cross Site Scripting (XSS) - Unsupported
by security-news＠drupal.org 04 Mar '15

04 Mar '15

View online: https://www.drupal.org/node/2445977 * Advisory ID: DRUPAL-SA-CONTRIB-2015-070 * Project: Mover [1] (third-party module) * Version: 6.x * Date: 2015-March-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 --------------------------------------------------------- The Mover modules provide the ability to move content between Drupal sites. The module doesn't sufficiently sanitize user supplied text in some pages, thereby exposing a Cross Site Scripting vulnerability. This vulnerability is mitigated by the fact that an attacker must have permission to create/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 --------------------------------------------------- * Mover 6.x-1.0 Drupal core is not affected. If you do not use the contributed Mover [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Mover module you should uninstall it. Also see the Mover [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/mover [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/mover [5] https://www.drupal.org/project/mover [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-069 - Taxonomy Accordion - Cross Site Scripting (XSS) - Unsupported
by security-news＠drupal.org 04 Mar '15

04 Mar '15

View online: https://www.drupal.org/node/2445973 * Advisory ID: DRUPAL-SA-CONTRIB-2015-069 * Project: Taxonomy Accordion [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-March-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 --------------------------------------------------------- Taxonomy Accordion module creates a block for each taxonomy vocabularies. The module doesn't sufficiently sanitize user supplied text in some pages, thereby exposing a Cross Site Scripting vulnerability. This vulnerability is mitigated by the fact that an attacker must have a user allowed to create/edit taxonomy 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 --------------------------------------------------- * All versions of Taxonomy Accordion module Drupal core is not affected. If you do not use the contributed Taxonomy Accordion [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Taxonomy Accordion module you should uninstall it. Also see the Taxonomy Accordion [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/taxonomy_accordion [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/taxonomy_accordion [5] https://www.drupal.org/project/taxonomy_accordion [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-068 - Campaign Monitor - Cross Site Request Forgery (CSRF) - Unsupported
by security-news＠drupal.org 04 Mar '15

04 Mar '15

View online: https://www.drupal.org/node/2445971 * Advisory ID: DRUPAL-SA-CONTRIB-2015-068 * Project: Campaign Monitor [1] (third-party module) * Version: 7.x * Date: 2015-March-04 * 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 --------------------------------------------------------- Campaign Monitor module integrates the Campaign Monitor API into Drupal. The module doesn't sufficiently protect some URLs against CSRF. A malicious user can cause another user to enable and disable list subscriptions by getting their 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 --------------------------------------------------- * Campaign Monitor 7.x-1.0 Drupal core is not affected. If you do not use the contributed Campaign Monitor [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Campaign Monitor module for Drupal 7 you should uninstall it. Also see the Campaign Monitor [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/campaignmonitor [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/campaignmonitor [5] https://www.drupal.org/project/campaignmonitor [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-067 - Finder - Open Redirect - Unsupported
by security-news＠drupal.org 04 Mar '15

04 Mar '15

View online: https://www.drupal.org/node/2445967 * Advisory ID: DRUPAL-SA-CONTRIB-2015-067 * Project: Finder [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-March-04 * Security risk: 9/25 ( Less Critical) AC:Complex/A:None/CI:None/II:None/E:Theoretical/TD:All [2] * Vulnerability: Open Redirect -------- DESCRIPTION --------------------------------------------------------- Finder module allows you to create flexible faceted search forms to find entities such as nodes or users based on the values of fields and database attributes. The provided function finder_form_goto() is susceptible to a phishing attack. An attacker could formulate a redirect in a way that gets the Drupal site to send the user to an arbitrarily provided 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 Finder module Drupal core is not affected. If you do not use the contributed Finder [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Finder module you should uninstall it. Also see the Finder [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/finder [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/finder [5] https://www.drupal.org/project/finder [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-066 - Tracking Code - Cross Site Request Forgery (CSRF) - Unsupported
by security-news＠drupal.org 04 Mar '15

04 Mar '15

View online: https://www.drupal.org/node/2445961 * Advisory ID: DRUPAL-SA-CONTRIB-2015-066 * Project: Tracking Code [1] (third-party module) * Version: 7.x * Date: 2015-March-04 * 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 --------------------------------------------------------- Tracking Code module allows you to create tracking code snippets and control their visibility. The module doesn't sufficiently protect some URLs against CSRF. A malicious user can cause an administrator to disable tracking codes by getting their 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 Tracking Code module Drupal core is not affected. If you do not use the contributed Tracking Code [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Tracking Code module you should uninstall it. Also see the Tracking Code [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/tracking_code [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/tracking_code [5] https://www.drupal.org/project/tracking_code [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-065 - Registration codes - Multiple vulnerabilities - Unsupported
by security-news＠drupal.org 04 Mar '15

04 Mar '15

View online: https://www.drupal.org/node/2445955 * Advisory ID: DRUPAL-SA-CONTRIB-2015-065 * Project: Registration codes [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-March-04 * 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 -------- DESCRIPTION --------------------------------------------------------- Registration codes module allows new account registrations only for users who provide a valid registration code. The module was not properly sanitizing user supplied text in some pages, thereby exposing XSS vulnerabilities. Additionally, some URLs were not protected against CSRF, a malicious user can cause an administrator to delete rules by getting their browser to make a request to a specially-crafted URL. The XSS vulnerabilities may be mitigated by the fact that an attacker must have a user allowed to create/edit taxonomy terms or 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 Registration codes Drupal core is not affected. If you do not use the contributed Registration codes [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Registration codes module you should uninstall it. Also see the Registration codes [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/regcode [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/regcode [5] https://www.drupal.org/project/regcode [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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Security-news