- Security-news - lists.drupal.org

Location Map - Moderately Critical - Multiple vulnerabilities - SA-CONTRIB-2017-026
by security-news＠drupal.org 01 Mar '17

01 Mar '17

View online: https://www.drupal.org/node/2857021 * Advisory ID: DRUPAL-SA-CONTRIB-2017-026 * Project: Location Map [1] (third-party module) * Version: 7.x * Date: 2017-March-01 * Security risk: 10/25 ( Moderately Critical) AC:Basic/A:User/CI:None/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting, Access bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to display one simple location map via Google Maps. The module doesn't sufficiently sanitize user input in the configuration text fields of the module (allows any tags and does not respect text format configuration). This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer locationmap". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * locationmap 7.x-2.x versions prior to 7.x-2.4. Drupal core is not affected. If you do not use the contributed Location Map [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install locationmap-7.x-2.4 [5] Also see the Location Map [6] project page. -------- REPORTED BY --------------------------------------------------------- * Stefan Korn [7] -------- FIXED BY ------------------------------------------------------------ * Stefan Korn [8] the module co-maintainer -------- 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/locationmap [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/locationmap [5] https://www.drupal.org/project/locationmap/releases/7.x-2.4 [6] https://www.drupal.org/project/locationmap [7] https://www.drupal.org/user/1942204 [8] https://www.drupal.org/user/1942204 [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

Remember Me - Critical - Unsupported - SA-CONTRIB-2017-025
by security-news＠drupal.org 01 Mar '17

01 Mar '17

View online: https://www.drupal.org/node/2857015 * Advisory ID: DRUPAL-SA-CONTRIB-2017-025 * Project: Remember Me [1] (third-party module) * Version: 7.x * Date: 2017-March-01 -------- DESCRIPTION --------------------------------------------------------- Remember me is a module that allows users to check "Remember me" when logging in. The security team is marking this module unsupported. There is a known security issue with the module that has not been fixed by the maintainer. If you would like to maintain this module, please read: https://www.drupal.org/node/251466 -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [2] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * All versions Drupal core is not affected. If you do not use the contributed Remember Me [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the remember_me module for Drupal 7.x you should uninstall it. Also see the remember_me [4] project page. -------- REPORTED BY --------------------------------------------------------- * Kristiaan Van den Eynde [5] -------- FIXED BY ------------------------------------------------------------ Not applicable -------- 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 [6]. Learn more about the Drupal Security team and their policies [7], writing secure code for Drupal [8], and securing your site [9]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [10] [1] https://www.drupal.org/project/remember_me [2] http://cve.mitre.org/ [3] https://www.drupal.org/project/remember_me [4] https://www.drupal.org/project/remember_me [5] https://www.drupal.org/user/1345130 [6] https://www.drupal.org/contact [7] https://www.drupal.org/security-team [8] https://www.drupal.org/writing-secure-code [9] https://www.drupal.org/security/secure-configuration [10] https://twitter.com/drupalsecurity

1 0

RestWS - Moderately Critical - Information Disclosure - SA-CONTRIB-2017-024
by security-news＠drupal.org 01 Mar '17

01 Mar '17

View online: https://www.drupal.org/node/2857014 * Advisory ID: DRUPAL-SA-CONTRIB-2017-024 * Project: RESTful Web Services [1] (third-party module) * Version: 7.x * Date: 2017-March-01 * Security risk: 12/25 ( Moderately Critical) AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Information Disclosure -------- DESCRIPTION --------------------------------------------------------- RestWS makes Drupal Entity data available in a REST API. The module doesn’t sufficiently check for access to properties when filtering queries. This vulnerability is mitigated by the fact that an attacker must have a role that allows them to access an entity type with access-controlled properties. And the attacker can only query on the property equalling a value supplied by the attacker. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * restws 7.x-2.x versions prior to 7.x-2.7. Drupal core is not affected. If you do not use the contributed RESTful Web Services [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the restws 2.x module for Drupal 7.x, upgrade to restws 7.x-2.7 [5] Also see the RESTful Web Services [6] project page. -------- REPORTED BY --------------------------------------------------------- * Neil Drumm [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Neil Drumm [8] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Micheal 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/restws [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/restws [5] https://www.drupal.org/project/restws/releases/7.x-2.7 [6] https://www.drupal.org/project/restws [7] https://www.drupal.org/u/drumm [8] https://www.drupal.org/u/drumm [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

DownloadFile- Critical - Unsupported - SA-CONTRIB-2017-023
by security-news＠drupal.org 22 Feb '17

22 Feb '17

View online: https://www.drupal.org/node/2854983 * Advisory ID: DRUPAL-SA-CONTRIB-2017-023 * Project: DownloadFile [1] (third-party module) * Version: 7.x * Date: 2017-Jan-25 * Security risk: 19/25 ( Critical) AC:None/A:None/CI:Some/II:Some/E:Proof/TD:All [2] -------- DESCRIPTION --------------------------------------------------------- DownloadFile is a module to direct download files or images. The security team is marking this module unsupported. There is a known security issue with the module that has not been fixed by the maintainer. If you would like to maintain this module, please read: https://www.drupal.org/node/251466 -------- 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 Drupal core is not affected. If you do not use the contributed download file [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the download_file module for Drupal 7.x you should uninstall it. Also see the download file [5] project page. -------- REPORTED BY --------------------------------------------------------- * Julian Pustkuchen [6] -------- FIXED BY ------------------------------------------------------------ Not applicable -------- 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 [7]. Learn more about the Drupal Security team and their policies [8], writing secure code for Drupal [9], and securing your site [10]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [11] [1] https://www.drupal.org/project/download_file [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/download_file [5] https://www.drupal.org/project/download_file [6] https://www.drupal.org/user/291091 [7] https://www.drupal.org/contact [8] https://www.drupal.org/security-team [9] https://www.drupal.org/writing-secure-code [10] https://www.drupal.org/security/secure-configuration [11] https://twitter.com/drupalsecurity

1 0

Views - Moderately Critical - Access Bypass - SA-CONTRIB-2017-022
by security-news＠drupal.org 22 Feb '17

22 Feb '17

View online: https://www.drupal.org/node/2854980 * Advisory ID: DRUPAL-SA-CONTRIB-2017-022 * Project: Views [1] (third-party module) * Version: 7.x * Date: 2017-February-22 * Security risk: 10/25 ( Moderately Critical) AC:Complex/A:None/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The Views module allows site builders to create listings of various data in the Drupal database. The Views module fails to add the required query tags to listings of Taxonomy Terms, which could cause private data stored on Taxonomy Terms to be leaked to users without permision to view it. This is mitigated by the fact that a View must exist that lists Taxonomy Terms which contain private data. If all the data on Taxonomy Terms is public or there are no applicable Views, then your site is unaffected. -------- 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 7.x-3.x versions prior to 7.x-3.14. 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 7.x, upgrade to views 7.x-3.15 [5] Also see the Views [6] project page. -------- REPORTED BY --------------------------------------------------------- * Chris Thornett [7] -------- FIXED BY ------------------------------------------------------------ * Chris Thornett [8] * dawehner [9] * xjm [10] of the Drupal Security Team -------- 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/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/project/views/releases/7.x-3.15 [6] https://www.drupal.org/project/views [7] https://www.drupal.org/user/2352928 [8] https://www.drupal.org/user/2352928 [9] https://www.drupal.org/u/dawehner [10] https://www.drupal.org/u/xjm [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

Unpublished 404 - Critical - Unsupported - SA-CONTRIB-2017-021
by security-news＠drupal.org 22 Feb '17

22 Feb '17

View online: https://www.drupal.org/node/2854981 * Advisory ID: DRUPAL-SA-CONTRIB-2017-021 * Project: Unpublished 404 [1] (third-party module) * Version: 7.x * Date: 2017-Jan-25 * Security risk: 19/25 ( Critical) AC:None/A:None/CI:Some/II:Some/E:Proof/TD:All [2] -------- DESCRIPTION --------------------------------------------------------- The purpose of this module is to emit a 404 error when a user tries to access a unpublished pages. The security team is marking this module unsupported. There is a known security issue with the module that has not been fixed by the maintainer. If you would like to maintain this module, please read: https://www.drupal.org/node/251466 -------- 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 Drupal core is not affected. If you do not use the contributed unpublished 404 [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the unpublished_404 module for Drupal 7.x you should uninstall it. Also see the unpublished 404 [5] project page. -------- REPORTED BY --------------------------------------------------------- * Rune Schjellerup Philosof [6] -------- FIXED BY ------------------------------------------------------------ Not applicable -------- 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 [7]. Learn more about the Drupal Security team and their policies [8], writing secure code for Drupal [9], and securing your site [10]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [11] [1] https://www.drupal.org/project/unpublished_404 [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/unpublished_404 [5] https://www.drupal.org/project/unpublished_404 [6] https://www.drupal.org/user/629892 [7] https://www.drupal.org/contact [8] https://www.drupal.org/security-team [9] https://www.drupal.org/writing-secure-code [10] https://www.drupal.org/security/secure-configuration [11] https://twitter.com/drupalsecurity

1 0

Timezone Detect - Moderately Critical - Cross Site Request Forgery - SA-CONTRIB-2017-020
by security-news＠drupal.org 22 Feb '17

22 Feb '17

View online: https://www.drupal.org/node/2854962 * Advisory ID: DRUPAL-SA-CONTRIB-2017-020 * Project: Timezone Detect [1] (third-party module) * Version: 7.x * Date: 2017-February-22 * 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 --------------------------------------------------------- This module enables sites to automatically detect and set user timezones via JavaScript. The module does not sufficiently protect against Cross-Site Request Forgery (CSRF): an attacker could use this vulnerability to manipulate a user's timezone setting. The security implication of this issue depends on the site. It can range from minor annoyance to some level of a bigger bug on a site that relies on the timezone for some more important purpose. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Timezone Detect 7.x-1.x versions prior to 7.x-1.2. Drupal core is not affected. If you do not use the contributed Timezone Detect [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Timezone Detect module for Drupal 7.x, upgrade to Timezone Detect 7.x-1.2 [5] Also see the Timezone Detect [6] project page. -------- REPORTED BY --------------------------------------------------------- * Greg Knaddison [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Jordan Magnuson [8] the module maintainer -------- 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/timezone_detect [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/timezone_detect [5] https://www.drupal.org/project/timezone_detect/releases/7.x-1.2 [6] https://www.drupal.org/project/timezone_detect [7] https://www.drupal.org/u/greggles [8] https://www.drupal.org/u/jordanmagnuson [9] https://www.drupal.org/u/greggles [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

Metatag -Moderately Critical - Information disclosure - SA-CONTRIB-2017-019
by security-news＠drupal.org 15 Feb '17

15 Feb '17

View online: https://www.drupal.org/node/2852937 * Advisory ID: DRUPAL-SA-CONTRIB-2017-019 * Project: Metatag [1] (third-party module) * Version: 7.x * Date: 2017-February-15 * Security risk: 11/25 ( Moderately Critical) AC:Complex/A:None/CI:Some/II:None/E:Proof/TD:Uncommon [2] * Vulnerability: Information Disclosure -------- DESCRIPTION --------------------------------------------------------- This module enables you to add a variety of meta tags to a site for helping with a site's search engine results and to customize how content is shared on social networks. The module doesn't sufficiently protect against data being cached that might contain information related to a specific user. This vulnerability is mitigated by the fact that a site must have a page with sensitive data in the page title that varies per logged in user. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Metatag 7.x-1.x versions prior to 7.x-1.21. Drupal core is not affected. If you do not use the contributed Metatag [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Metatag module for Drupal 7.x, upgrade to Metatag 7.x-1.21 [5]. Also see the Metatag [6] project page. -------- REPORTED BY --------------------------------------------------------- * Matthias Hutterer [7] * torokrita [8] -------- FIXED BY ------------------------------------------------------------ * Damien McKenna [9] the module maintainer. * Klaus Purer [10] of the Drupal Security Team. -------- COORDINATED BY ------------------------------------------------------ * Damien McKenna [11] the module maintainer. * 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/metatag [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/metatag [5] https://www.drupal.org/project/metatag/releases/7.x-1.21 [6] https://www.drupal.org/project/metatag [7] https://www.drupal.org/u/mh86 [8] https://www.drupal.org/u/torokrita [9] https://www.drupal.org/u/damienmckenna [10] https://www.drupal.org/u/klausi [11] https://www.drupal.org/u/damienmckenna [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

RESTful - Moderately Critical - Access Bypass - SA-CONTRIB-2017-018
by security-news＠drupal.org 15 Feb '17

15 Feb '17

View online: https://www.drupal.org/node/2852928 * Advisory ID: DRUPAL-SA-CONTRIB-2017-018 * Project: RESTful [1] (third-party module) * Version: 7.x * Date: 2017-February-15 * Security risk: 11/25 ( Moderately Critical) AC:Complex/A:User/CI:Some/II:Some/E:Theoretical/TD:Uncommon [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to build a RESTful API for your Drupal site. The restful_token_auth module (a sub-module) doesn't validate the status of users when logging them in. This results in a blocked user being able to operate normally with the RESTful actions, even after being blocked. This vulnerability is mitigated by the fact that an attacker must be in possession of the credentials of a previously blocked user. It is also mitigated by the attacker only will have the access corresponding to the roles of the blocked user. Finally this only affects sites that use the sub-module, restful_token_auth. -------- 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.8. * RESTful 7.x-2.x versions prior to 7.x-2.16. 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_token_auth sub-module for Drupal 7.x, upgrade to RESTful 7.x-1.8 [5] or RESTful 7.x-2.16 [6] Also see the RESTful [7] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [8] of the Drupal Security Team * Roy Segall [9] -------- FIXED BY ------------------------------------------------------------ * Mateu Aguiló Bosch [10] the module maintainer * Michael Hess [11] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Michael Hess [12] of the Drupal Security Team * David Snopek [13] 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/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/2852761 [6] https://www.drupal.org/node/2852759 [7] https://www.drupal.org/project/restful [8] https://www.drupal.org/user/2301194 [9] https://www.drupal.org/user/1812910 [10] https://www.drupal.org/user/550110 [11] https://www.drupal.org/user/102818 [12] https://www.drupal.org/user/102818 [13] https://www.drupal.org/user/266527 [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

Flag clear - Moderately Critical - Cross Site Request Forgery (CSRF) - SA-CONTRIB-2017-017
by security-news＠drupal.org 15 Feb '17

15 Feb '17

View online: https://www.drupal.org/node/2852924 * Advisory ID: DRUPAL-SA-CONTRIB-2017-017 * Project: Flag clear [1] (third-party module) * Version: 7.x * Date: 2017-February-15 * Security risk: 10/25 ( Moderately Critical) AC:Basic/A:Admin/CI:None/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Request Forgery -------- DESCRIPTION --------------------------------------------------------- The Flag clear module allows administrators to remove user flags for content. This functionality is often useful in user-submission use-cases, where users do not necessarily need to unflag things on their own. The module doesn't sufficiently protect from CSRF attacks. The unflagging links do not include a token. This vulnerability is mitigated by the fact that an attacker must be targeting users with the 'clear flags' role. They must also discover a valid combination of flag, content and user IDs for flagged content. -------- 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 Flag clear module versions prior to 7.x-2.0. Drupal core is not affected. If you do not use the contributed Flag clear [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Flag clear module for Drupal 7.x, upgrade to Flag clear 7.x-2.0 [5] Also see the Flag clear [6] project page. -------- REPORTED BY --------------------------------------------------------- * Neil Drumm [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Zak Huber [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/flag_clear [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/flag_clear [5] https://www.drupal.org/node/2614438 [6] https://www.drupal.org/project/flag_clear [7] https://www.drupal.org/user/3064 [8] https://www.drupal.org/user/1437276/ [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