Security-news

security-news@drupal.org

1 participants
1782 discussions

Page Access - Unsupported - SA-CONTRIB-2017-75
by security-news＠drupal.org 20 Sep '17

20 Sep '17

View online: https://www.drupal.org/node/2910306 * Advisory ID: DRUPAL-SA-CONTRIB-2017-75 * Project: Page Access [1] (third-party module) * Date: 20-September-2017 -------- DESCRIPTION --------------------------------------------------------- This module will provide the option to give the View and Edit access for users and roles on each node 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 -------- VERSIONS AFFECTED --------------------------------------------------- * All versions Drupal core is not affected. If you do not use the contributed Page Access [2] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Page Access module for Drupal you should uninstall it. Also see the Page Access [3] project page. -------- REPORTED BY --------------------------------------------------------- * Frédéric Buclin [4] -------- 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 [5]. Learn more about the Drupal Security team and their policies [6], writing secure code for Drupal [7], and securing your site [8]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [9] [1] https://www.drupal.org/project/page_access [2] https://www.drupal.org/project/page_access [3] https://www.drupal.org/project/page_access [4] https://www.drupal.org/u/lpsolit [5] https://www.drupal.org/contact [6] https://www.drupal.org/security-team [7] https://www.drupal.org/writing-secure-code [8] https://www.drupal.org/security/secure-configuration [9] https://twitter.com/drupalsecurity

1 0

Flag clear - Moderately Critical - CSRF - DRUPAL-SA-CONTRIB-2017-074
by security-news＠drupal.org 13 Sep '17

13 Sep '17

View online: https://www.drupal.org/node/2908592 * Advisory ID: DRUPAL-SA-CONTRIB-2017-074 * Project: Flag clear [1] (third-party module) * Version: 7.x * Date: 2017-September-13 * Security risk: 14/25 ( Moderately Critical) AC:None/A:None/CI:None/II:Some/E:Theoretical/TD:Default [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 confirm a user's intent to take unflagging actions. -------- 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-1.10. 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-1.10 [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/project/flag_clear/releases/7.x-1.10 [6] https://www.drupal.org/project/flag_clear [7] https://www.drupal.org/u/drumm [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

CAPTCHA - Moderately Critical - Denial of Service - SA-CONTRIB-2017-073
by security-news＠drupal.org 06 Sep '17

06 Sep '17

View online: https://www.drupal.org/node/2907137 * Advisory ID: DRUPAL-SA-CONTRIB-2017-073 * Project: CAPTCHA [1] (third-party module) * Version: 7.x * Date: 2017-September-06 * Security risk: 10/25 ( Moderately Critical) AC:Basic/A:None/CI:None/II:None/E:Proof/TD:Default [2] * Vulnerability: Denial of Service -------- DESCRIPTION --------------------------------------------------------- This module enables you to use various techniques to block automated scripts / robots from submitting content to a site, e.g. to block spam comments. The module doesn't properly store the session ID of visitors who are given a session which could lead to a Denial of Service attack. This vulnerability is mitigated by the fact that Drupal does not give a session to all visitors, especially when used with advanced caching systems like Varnish. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * CAPTCHA 7.x-1.x versions prior to 7.x-1.5. Drupal core is not affected. If you do not use the contributed CAPTCHA [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the CATPCHA module for Drupal 7.x, upgrade to CAPTCHA 7.x-1.5. [5] Also see the CAPTCHA [6] project page. -------- REPORTED BY --------------------------------------------------------- * Nightwalker3000 [7] -------- FIXED BY ------------------------------------------------------------ * Fabiano Sant'Ana [8], the module's maintainer. -------- COORDINATED BY ------------------------------------------------------ * Lee Rowlands [9] of the Drupal Security Team. * Damien McKenna [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/captcha [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/captcha [5] https://www.drupal.org/project/captcha/releases/7.x-1.5 [6] https://www.drupal.org/project/captcha [7] https://www.drupal.org/u/nightwalker3000 [8] https://www.drupal.org/u/wundow [9] https://www.drupal.org/u/larowlan [10] https://www.drupal.org/u/damienmckenna [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

Clientside Validation - Critical - Arbitary PHP Execution - DRUPAL-SA-CONTRIB-2017-072
by security-news＠drupal.org 06 Sep '17

06 Sep '17

View online: https://www.drupal.org/node/2907118 * Advisory ID: DRUPAL-SA-CONTRIB-2017-072 * Project: Clientside Validation [1] (third-party module) * Version: 7.x * Date: 2017-September-06 * Security risk: 16/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Arbitrary PHP code execution -------- DESCRIPTION --------------------------------------------------------- The Clientside Validation module enables you to have clientside (Javascript) validation on your forms. The module does not sufficiently validate parameters of a POST request made when validating a CAPTCHA. For the 1.x version of this module, this vulnerability is mitigated by the fact that the CAPTCHA module must be enabled and the 'validate captcha' option of the Clientside Validation module must be enabled (this option is enabled by default). For the 2.x version of this module, this vulnerability is mitigated by the fact that the CAPTCHA module must be enabled and the Clientside Validation captcha submodule must be enabled. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Clientside Validation 7.x-1.x versions prior to 7.x-1.44. * Clientside Validation 7.x-2.x versions prior to 7.x-2.0-beta1. Drupal core is not affected. If you do not use the contributed Clientside Validation [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the 1.x version of Clientside Validation module for Drupal 7.x, upgrade to Clientside Validation 7.x-1.45 [5] * If you use the 2.x version of Clientside Validation module for Drupal 7.x, upgrade to Clientside Validation 7.x-2.0-beta2 [6] Also see the Clientside Validation [7] project page. -------- REPORTED BY --------------------------------------------------------- * Daniel-SCRT [8] -------- FIXED BY ------------------------------------------------------------ * Jelle Sebreghts [9] the module maintainer -------- 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/clientside_validation [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/clientside_validation [5] https://www.drupal.org/project/clientside_validation/releases/7.x-1.45 [6] https://www.drupal.org/project/clientside_validation/releases/7.x-2.0-beta2 [7] https://www.drupal.org/project/clientside_validation [8] https://www.drupal.org/u/daniel-scrt [9] https://www.drupal.org/u/jelle_s [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

H5P - Critical - Reflected Cross Site Scripting (XSS) - DRUPAL-SA-CONTRIB-2017-071
by security-news＠drupal.org 30 Aug '17

30 Aug '17

View online: https://www.drupal.org/node/2905692 * Advisory ID: DRUPAL-SA-CONTRIB-2017-071 * Project: H5P- Create and Share Rich Content and Applications [1] (third-party module) * Version: 7.x * Date: 2017-August-30 * Security risk: 18/25 ( Critical) AC:None/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The H5P module helps create interactive videos, question sets, drag and drop questions, multichoice questions, boardgames, presentations, flashcards and more using Drupal. The module does not sufficiently filter text prior to printing it back to the page, leading to a Reflected Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that many modern browsers contain protection against some kinds of Reflected XSS vulnerabilities. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * H5P 7.x-1.x versions prior to 7.x-1.32. Drupal core is not affected. If you do not use the contributed H5P- Create and Share Rich Content and Applications [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the H5P module for Drupal 7.x, upgrade to H5P 7.x-1.32 [5] Also see the H5P- Create and Share Rich Content and Applications [6] project page. -------- REPORTED BY --------------------------------------------------------- * Johan Westin [7] -------- FIXED BY ------------------------------------------------------------ * Thomas Marstrander [8] * Pål Jørgensen [9] -------- 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/h5p [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/h5p [5] https://www.drupal.org/project/h5p/releases/7.x-1.32 [6] https://www.drupal.org/project/h5p [7] https://www.drupal.org/user/2314400 [8] https://www.drupal.org/u/thomasmars [9] https://www.drupal.org/user/1091732 [10] https://www.drupal.org/user/36762 [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

Commerce invoices - Highly Critical - SQL Injection and Cross Site scripting - DRUPAL-SA-CONTRIB-2017-070
by security-news＠drupal.org 30 Aug '17

30 Aug '17

View online: https://www.drupal.org/node/2905691 * Advisory ID: DRUPAL-SA-CONTRIB-2017-070 * Project: Commerce Invoices [1] (third-party module) * Version: 7.x * Date: 2017-August-30 * Security risk: 20/25 ( Highly Critical) AC:None/A:None/CI:All/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting, SQL Injection -------- DESCRIPTION --------------------------------------------------------- Commerce Invoices allows you to enter an Invoice number, Company name and Amount and it will generate an Invoice that the client can pay on your site using any payment method supported by Drupal commerce. -------- SQL INJECTION ------------------------------------------------------- The module did not properly use Drupal's database API when querying the database with user supplied values, allowing an attacker to send a specially crafted request to modify the query or potentially perform additional queries. The vulnerability is mitigated by the fact that the attacker must have the 'access checkout' permission - this permission is commonly granted. -------- STORED CROSS SITE SCRIPTING (XSS) ----------------------------------- The module did not filter user-supplied text prior to printing that text back to users of the site. The vulnerability is mitigated by the fact that the attacker must have the 'access checkout' permission - this permission is commonly granted. -------- 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 Commerce invoice versions prior to 7.x-1.1 Drupal core is not affected. If you do not use the contributed Commerce Invoices [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Commerce invoice module for Drupal 7.x, upgrade to Commerce invoice 7.x-1.1 [5] Special note: the module's strings have changed. Any site that uses Drupal's localization system should review and update the translated strings on the site. Also see the Commerce Invoices [6] project page. -------- REPORTED BY --------------------------------------------------------- * Jean-Francois Hovinne [7] -------- FIXED BY ------------------------------------------------------------ * Samuel Solís [8] the module maintainer * Jean-Francois Hovinne [9] of the Drupal Security Team * Greg Knaddison [10] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [11] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact [12]. Learn more about the Drupal Security team and their policies [13], writing secure code for Drupal [14], and securing your site [15]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [16] [1] https://www.drupal.org/project/commerce_invoices [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/commerce_invoices [5] https://www.drupal.org/project/commerce_invoices/releases/7.x-1.1 [6] https://www.drupal.org/project/commerce_invoices [7] https://www.drupal.org/user/139209 [8] https://www.drupal.org/user/1232954 [9] https://www.drupal.org/user/139209 [10] https://www.drupal.org/user/36762 [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

Update on Views Ajax vulnerability for Drupal 7 Views and Drupal 8 core. -- PSA-2017-002
by security-news＠drupal.org 17 Aug '17

17 Aug '17

View online: https://www.drupal.org/PSA-2017-002 * Advisory ID: DRUPAL-PSA-2017-002 * Project: Drupal contributed modules * Version: 7.x, 8.x * Date: 2017-Aug-16 -------- DESCRIPTION --------------------------------------------------------- The Drupal Security Team is now aware that the Views ajax access bypass vulnerability (DRUPAL-SA-CONTRIB-2017-068 [1] and SA-CORE-2017-004 [2]) released 16 Aug 2017 is more severe than originally announced, because many widely used contrib modules don't have access restrictions set on the default views they provide. Any view that does not have access controls on the default (master) display may be vulnerable. The vulnerability does not require any authentication to be exploited. A successful exploit results in some non-public data being made public. Sites running versions of Views prior to 7.x-3.17 or Drupal 8 core prior to version 8.3.7 (including Drupal 8.1.x and 8.2.x) should update immediately. Drupal 7 core is only affected if the Views module is enabled. If you are unable to update Views, you can mitigate this by editing views that contain sensitive data in the Views UI and making sure they utilise one of the permission controls - such as 'require a role' or 'require a permission'. See Views permissions manual page [3] for more information. -------- 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 [4]. Learn more about the Drupal Security Team and their policies [5], writing secure code for Drupal [6], and securing your site [7]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [8] [1] https://www.drupal.org/node/2902604 [2] https://www.drupal.org/SA-CORE-2017-004 [3] https://www.drupal.org/docs/7/modules/views/views-howtos/views-permissions [4] https://www.drupal.org/contact [5] https://www.drupal.org/security-team [6] https://www.drupal.org/writing-secure-code [7] https://www.drupal.org/security/secure-configuration [8] https://twitter.com/drupalsecurity

1 0

Entity Reference - Moderately Critical - Access Bypass - DRUPAL-SA-CONTRIB-2017-067
by security-news＠drupal.org 16 Aug '17

16 Aug '17

View online: https://www.drupal.org/node/2902596 * Advisory ID: DRUPAL-SA-CONTRIB-2017-067 * Project: Entity reference [1] (third-party module) * Version: 7.x * Date: 2017-August-16 * Security risk: 12/25 ( Moderately Critical) AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The entity reference module provides a field type that can reference arbitrary entities. In a vulnerable configuration, an attacker could determine the titles of nodes they do not have access to. This is mitigated as only entity reference fields using the "simple" entity selector are vulnerable, and the attack is not possible if any access control (i.e. node access) is in place (the attacker's role is missing only the "access content" permission to be able to view the 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 --------------------------------------------------- * entityreference 7.x-1.x versions prior to 7.x-1.5. Drupal core is not affected. If you do not use the contributed Entity reference [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the entityreference module for Drupal 7.x, upgrade to entityreference 7.x-1.5 [5] Also see the Entity reference [6] project page. -------- REPORTED BY --------------------------------------------------------- * Greg Knaddison [7] of the Drupal Security Team * Aaron Ott [8] -------- FIXED BY ------------------------------------------------------------ * David Pascoe-Deslauriers [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [10] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact [11]. Learn more about the Drupal Security team and their policies [12], writing secure code for Drupal [13], and securing your site [14]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/entityreference [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/entityreference [5] https://www.drupal.org/node/2902583 [6] https://www.drupal.org/project/entityreference [7] https://www.drupal.org/u/greggles [8] https://www.drupal.org/user/154069 [9] https://www.drupal.org/u/spotzero [10] https://www.drupal.org/user/2301194 [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

Views refresh - Moderately Critical - Access Bypass - DRUPAL-SA-CONTRIB-2017-069
by security-news＠drupal.org 16 Aug '17

16 Aug '17

View online: https://www.drupal.org/node/2902606 * Advisory ID: DRUPAL-SA-CONTRIB-2017-069 * Project: Views Refresh [1] (third-party module) * Version: 7.x, 8.x * Date: 2017-August-16 * Security risk: 14/25 ( Moderately Critical) AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- When creating a view, you can optionally use Ajax to update the displayed data via filter parameters. The views refresh module did not restrict access to the Ajax endpoint to only views configured to use Ajax. This is mitigated if you have access restrictions on the view. It is best practice to always include some form of access restrictions on all views, even if you are using another module to display them. -------- 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 fresh versions prior to 7.x-1.2. Drupal core is not affected. If you do not use the contributed Views refresh [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the views refresh module for Drupal 7.x, upgrade to views refresh 7.x-1.2 [5] Also see the Views refresh [6] project page. -------- REPORTED BY --------------------------------------------------------- * Maxim Podorov [7] -------- FIXED BY ------------------------------------------------------------ * Maxim Podorov [8] the module maintainer * Klaus Purer [9] * Daniel Wehner [10] * Michael Hess [11] of the Drupal Security Team * Len Swaneveld [12] * Wim Leers [13] * Peter Wolanin [14] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Michael Hess [15] 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 [16]. Learn more about the Drupal Security team and their policies [17], writing secure code for Drupal [18], and securing your site [19]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [20] [1] https://www.drupal.org/project/views_refresh [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/views_refresh [5] https://www.drupal.org/project/views_refresh/releases/7.x-1.2 [6] https://www.drupal.org/project/views_refresh [7] https://www.drupal.org/u/maximpodorov [8] https://www.drupal.org/u/maximpodorov [9] https://www.drupal.org/u/klausi [10] https://www.drupal.org/u/dawehner [11] https://www.drupal.org/u/mlhess [12] https://www.drupal.org/user/690914 [13] https://www.drupal.org/user/99777 [14] https://www.drupal.org/u/pwolanin [15] https://www.drupal.org/u/mlhess [16] https://www.drupal.org/contact [17] https://www.drupal.org/security-team [18] https://www.drupal.org/writing-secure-code [19] https://www.drupal.org/security/secure-configuration [20] https://twitter.com/drupalsecurity

1 0

Views - Moderately Critical - Access Bypass - DRUPAL-SA-CONTRIB-2017-068
by security-news＠drupal.org 16 Aug '17

16 Aug '17

View online: https://www.drupal.org/node/2902604 * Advisory ID: DRUPAL-SA-CONTRIB-2014-0XX * Project: Views [1] (third-party module) * Version: 7.x, 8.x * Date: 2017-August-16 * Security risk: 14/25 ( Moderately Critical) AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- When creating a view, you can optionally use Ajax to update the displayed data via filter parameters. The views subsystem/module did not restrict access to the Ajax endpoint to only views configured to use Ajax. This is mitigated if you have access restrictions on the view. It is best practice to always include some form of access restrictions on all views, even if you are using another module to display them. -------- 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 versions prior to 7.x-3.17. 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.17 [5] Also see the Views [6] project page. -------- REPORTED BY --------------------------------------------------------- * Maxim Podorov [7] -------- FIXED BY ------------------------------------------------------------ * Klaus Purer [8] * Daniel Wehner [9] * Michael Hess [10] of the Drupal Security Team * Len Swaneveld [11] * Wim Leers [12] * Peter Wolanin [13] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Michael Hess [14] 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 [15]. Learn more about the Drupal Security team and their policies [16], writing secure code for Drupal [17], and securing your site [18]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [19] [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.17 [6] https://www.drupal.org/project/views [7] https://www.drupal.org/u/maximpodorov [8] https://www.drupal.org/u/klausi [9] https://www.drupal.org/u/dawehner [10] https://www.drupal.org/u/mlhess [11] https://www.drupal.org/user/690914 [12] https://www.drupal.org/user/99777 [13] https://www.drupal.org/u/pwolanin [14] https://www.drupal.org/u/mlhess [15] https://www.drupal.org/contact [16] https://www.drupal.org/security-team [17] https://www.drupal.org/writing-secure-code [18] https://www.drupal.org/security/secure-configuration [19] 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