- Security-news - lists.drupal.org

baidu_analytics - Unsupported - SA-CONTRIB-2017-060
by security-news＠drupal.org 02 Aug '17

02 Aug '17

View online: https://www.drupal.org/node/2899341 * Advisory ID: DRUPAL-SA-CONTRIB-2017-060 * Project: baidu_analytics [1] (third-party module) * Date: 2-Aug-2017 -------- DESCRIPTION --------------------------------------------------------- This module adds the Baidu Analytics web statistics tracking system to your website. 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 baidu_analytics [2] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the baidu_analytics module for Drupal you should uninstall it. Also see the baidu_analytics [3] project page. -------- REPORTED BY --------------------------------------------------------- * Huang jie [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/baidu_analytics [2] https://www.drupal.org/project/baidu_analytics [3] https://www.drupal.org/project/baidu_analytics [4] https://www.drupal.org/user/2388566 [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

html_title - Unsupported - SA-CONTRIB-2017-059
by security-news＠drupal.org 02 Aug '17

02 Aug '17

View online: https://www.drupal.org/node/2899340 * Advisory ID: DRUPAL-SA-CONTRIB-2017-059 * Project: html_title [1] (third-party module) * Date: 2-Aug-2017 -------- DESCRIPTION --------------------------------------------------------- The HTML Title module allows a limited set of HTML markup (em, sub, sup, b, i, strong, cite, code, bdi, wbr) to be used in node titles. 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 html_title [2] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the html_title module for Drupal you should uninstall it. Also see the html_title [3] project page. -------- REPORTED BY --------------------------------------------------------- * Nathaniel Catchpole [4] of the Drupal Security Team -------- 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/html_title [2] https://www.drupal.org/project/html_title [3] https://www.drupal.org/project/html_title [4] https://www.drupal.org/u/catch [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

Alinks - Moderately Critical -Access bypass - SA-CONTRIB-2017-058
by security-news＠drupal.org 02 Aug '17

02 Aug '17

View online: https://www.drupal.org/node/2899334 * Advisory ID: DRUPAL-SA-CONTRIB-2017-058 * Project: Alinks [1] (third-party module) * Version: 8.x * Date: 2017-August-02 * 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 automatically link keywords to specific URLs. This module has an insufficient access check on the delete route. Alinks uses the wrong permission for an access check. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Alinks 8.x-1.x versions prior to 8.x-1.1. Drupal core is not affected. If you do not use the contributed Alinks [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Alinks module for Drupal 8.x, upgrade to Alinks 8.x-1.1 [5] Also see the Alinks [6] project page. -------- REPORTED BY --------------------------------------------------------- * Inasse [7] -------- FIXED BY ------------------------------------------------------------ * Inasse [8] * Webflo [9] * Greg Boggs [10] the module maintainer -------- 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/alinks [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/alinks [5] https://www.drupal.org/project/alinks/releases/8.x-1.1 [6] https://www.drupal.org/project/alinks [7] https://www.drupal.org/u/insasse [8] https://www.drupal.org/u/insasse [9] https://www.drupal.org/u/webflo [10] https://www.drupal.org/u/greg-boggs [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

Drupal Remote Dashboard - Critical - Weak encryption keys - SA-CONTRIB-2017-046
by security-news＠drupal.org 12 Jul '17

12 Jul '17

View online: https://www.drupal.org/node/2877388 * Advisory ID: DRUPAL-SA-CONTRIB-2017-046 * Project: Drupal Remote Dashboard [1] (third-party module) * Version: 7.x, 8.x * Date: 2017-May-10 * Security risk: 17/25 ( Critical) AC:Complex/A:None/CI:All/II:All/E:Theoretical/TD:Uncommon [2] * Vulnerability: Access bypass, Information Disclosure -------- DESCRIPTION --------------------------------------------------------- *UPDATE (2017-07-12)*: This SA originally only mentioned the Drupal 8 version of the module, but it was later discovered that this issue affected the Drupal 7 version as well. We've updated the SA for the Drupal 7 security release. Sorry for the confusion! This module enables you to remotely access remote Drupal sites to monitor and manage them all from one central place. The module doesn't sufficiently ensure that the system administrator uses a strong enough encryption key per the requirements of the encryption type, which leads to weak encryption for the communication between the management dashboard and the remote site which could be decrypted by an adequately equipped 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 --------------------------------------------------- * DRD 8.x-3.x versions prior to 8.x-3.2. * DRD 7.x-2.x versions prior to 7.x-2.10 Drupal core is not affected. If you do not use the contributed Drupal Remote Dashboard [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the DRD module for Drupal 8.x, upgrade to DRD 8.x-3.2 [5] * If you use the DRD module for Drupal 7.x, upgrade to DRD 7.x-2.10 [6] Also see the Drupal Remote Dashboard [7] project page. -------- REPORTED BY --------------------------------------------------------- * David Snopek [8] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Jürgen Haas [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * David Snopek [10] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact [11]. Learn more about the Drupal Security team and their policies [12], writing secure code for Drupal [13], and securing your site [14]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/drd [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/drd [5] https://www.drupal.org/project/drd/releases/8.x-3.2 [6] https://www.drupal.org/project/drd/releases/7.x-2.10 [7] https://www.drupal.org/project/drd [8] https://www.drupal.org/user/266527 [9] https://www.drupal.org/user/168924 [10] https://www.drupal.org/user/266527 [11] https://www.drupal.org/contact [12] https://www.drupal.org/security-team [13] https://www.drupal.org/writing-secure-code [14] https://www.drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

DrupalChat - Critical - Multiple vulnerabilities - SA-CONTRIB-2017-057
by security-news＠drupal.org 12 Jul '17

12 Jul '17

View online: https://www.drupal.org/node/2892404 * Advisory ID: DRUPAL-SA-CONTRIB-2017-057 * Project: DrupalChat [1] (third-party module) * Version: 7.x * Date: 2017-July-05 * 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 --------------------------------------------------------- *UPDATE (2017-07-12)*: This SA originally recommended version 2.6, but it was incorrectly tagged. We've updated the SA to recommend version 2.7. Sorry for the confusion! DrupalChat allows visitors of your Drupal site to chat with each other privately or together in a public chatroom. The module did not confirm the validity of a chat request, resulting in a Cross Site Request Forgery (CSRF) vulnerability which enables an attacker to trick a user to send arbitrary chat messages to any user. The The module did not filter administrator provided text, leading to a Cross Site Scripting (XSS) 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 --------------------------------------------------- * DrupalChat 7.x-2.x versions prior to 7.x-2.7. Drupal core is not affected. If you do not use the contributed DrupalChat [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the DrupalChat module for Drupal 7.x, upgrade to DrupalChat 7.x-2.7 [5] Also see the DrupalChat [6] project page. -------- REPORTED BY --------------------------------------------------------- * Elin Yordanov [7] -------- FIXED BY ------------------------------------------------------------ * Shashwat Srivastava [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Michael Hess [9] of the Drupal Security Team * 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/drupalchat [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/drupalchat [5] https://www.drupal.org/project/drupalchat/releases/7.x-2.7 [6] https://www.drupal.org/project/drupalchat [7] https://www.drupal.org/user/1274938 [8] https://www.drupal.org/u/darklrd [9] https://www.drupal.org/u/mlhess [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

DrupalChat - Critical - Multiple vulnerabilities - SA-CONTRIB-2017-057
by security-news＠drupal.org 05 Jul '17

05 Jul '17

View online: https://www.drupal.org/node/2892404 * Advisory ID: DRUPAL-SA-CONTRIB-2017-057 * Project: DrupalChat [1] (third-party module) * Version: 7.x * Date: 2017-July-05 * 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 --------------------------------------------------------- DrupalChat allows visitors of your Drupal site to chat with each other privately or together in a public chatroom. The module did not confirm the validity of a chat request, resulting in a Cross Site Request Forgery (CSRF) vulnerability which enables an attacker to trick a user to send arbitrary chat messages to any user. The The module did not filter administrator provided text, leading to a Cross Site Scripting (XSS) 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 --------------------------------------------------- * DrupalChat 7.x-2.x versions prior to 7.x-2.2. Drupal core is not affected. If you do not use the contributed DrupalChat [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the DrupalChat module for Drupal 7.x, upgrade to DrupalChat 7.x-2.6 [5] Also see the DrupalChat [6] project page. Also see the DrupalChat [7] project page. -------- REPORTED BY --------------------------------------------------------- * Elin Yordanov [8] -------- FIXED BY ------------------------------------------------------------ * Shashwat Srivastava [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Michael Hess [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/drupalchat [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/drupalchat [5] https://www.drupal.org/project/drupalchat/releases/7.x-2.6 [6] https://www.drupal.org/project/drupalchat [7] https://www.drupal.org/project/drupalchat [8] https://www.drupal.org/user/1274938 [9] https://www.drupal.org/u/darklrd [10] https://www.drupal.org/u/mlhess [11] https://www.drupal.org/u/greggles [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

OAuth - Critical - Access Bypass - SA-CONTRIB-2017-056
by security-news＠drupal.org 05 Jul '17

05 Jul '17

View online: https://www.drupal.org/node/2892400 * Advisory ID: DRUPAL-SA-CONTRIB-2017-056 * Project: OAuth [1] (third-party module) * Version: 8.x * Date: 2017-July-05 * Security risk: 15/25 ( Critical) AC:Complex/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to protect requests via the OAuth authentication protocol. The module doesn't sufficiently notify the Cache API to avoid caching responses under the scenario in which an authenticated user requests a resource such as unpublished node. This vulnerability is mitigated by the fact that an attacker must know the available resources in a Drupal site. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * OAuth 8.x-2.x versions prior to 8.x-2.1. Drupal core is not affected. If you do not use the contributed OAuth [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ In addition to updating the code, you must Clear all caches. * If you use the OAuth module for Drupal 8.x, upgrade to OAuth 8.x-2.1 Also see the OAuth [5] project page. -------- REPORTED BY --------------------------------------------------------- * Kevin Dutra [6]. -------- FIXED BY ------------------------------------------------------------ * Kevin Dutra [7] * Juampy NR [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Michael Hess [9] of the Drupal Security Team 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/oauth [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/oauth [5] https://www.drupal.org/project/oauth [6] https://www.drupal.org/user/1312744 [7] https://www.drupal.org/user/1312744 [8] https://www.drupal.org/u/juampynr [9] https://security.drupal.org/user/14049 [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

SMTP - Moderatley Critical - Information Disclosure - SA-CONTRIB-2017-055
by security-news＠drupal.org 28 Jun '17

28 Jun '17

View online: https://www.drupal.org/node/2890357 * Advisory ID: DRUPAL-SA-CONTRIB-2017-055 * Project: SMTP Authentication Support [1] (third-party module) * Version: 7.x, 8.x * Date: 2017-June-28 * Security risk: 10/25 ( Moderately Critical) AC:Complex/A:None/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] * Vulnerability: Information Disclosure -------- DESCRIPTION --------------------------------------------------------- This SMTP module enables you to send mail using a third party (non-system) mail service instead of the local system mailer included with Drupal. When this module is in debugging mode, it will log privileged information. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * smtp 8.x-1.x versions prior to 8.x-1.0-beta3. * smtp 7.x-1.x versions prior to 7.x-1.7. Drupal core is not affected. If you do not use the contributed SMTP Authentication Support [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the smtp module for Drupal 8.x, upgrade to smtp 8.x-1.0-beta3 [5] * If you use the smtp module for Drupal 7.x, upgrade to smtp 7.x-1.7 [6] Also see the SMTP Authentication Support [7] project page. -------- REPORTED BY --------------------------------------------------------- * Baysaa [8] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Fabiano Sant'Ana [9] the module maintainer * José San Martin [10] the module maintainer * David Snopek [11] of the Drupal Security Team * Cash Williams [12] of the Drupal Security Team * Michael Hess [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/smtp [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/smtp [5] https://www.drupal.org/project/smtp/releases/8.x-1.0-beta3 [6] https://www.drupal.org/project/smtp/releases/7.x-1.7 [7] https://www.drupal.org/project/smtp [8] https://www.drupal.org/user/1358394 [9] https://www.drupal.org/user/25523 [10] https://www.drupal.org/user/72012 [11] https://www.drupal.org/user/266527 [12] https://www.drupal.org/user/421070 [13] https://www.drupal.org/user/102818 [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

Services - Critical - SQL Injection - SA-CONTRIB-2017-054
by security-news＠drupal.org 28 Jun '17

28 Jun '17

View online: https://www.drupal.org/node/2890353 * Advisory ID: DRUPAL-SA-CONTRIB-2017-054 * Project: Services [1] (third-party module) * Version: 7.x * Date: 2017-June-28 * Security risk: 19/25 ( Critical) AC:None/A:User/CI:All/II:All/E:Theoretical/TD:Default [2] * Vulnerability: SQL Injection -------- DESCRIPTION --------------------------------------------------------- This module provides a standardized solution for building API's so that external clients can communicate with Drupal. The module doesn't sufficiently sanitize column names provided by the client when they are querying for data and trying to sort it. This vulnerability is mitigated by the fact that a site must have an "Index" resource enabled and the attacker must know the endpoint's 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 --------------------------------------------------- * Services 7.x-3.x versions prior to 7.x-3.20 Drupal core is not affected. If you do not use the contributed Services [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install services version 7.x-3.20 [5] of the module or disable any Index resources within your endpoint(s). Also see the Services [6] project page. -------- REPORTED BY --------------------------------------------------------- * John Morahan [7] -------- FIXED BY ------------------------------------------------------------ * Tyler Frankenstein [8], a module maintainer * John Morahan [9] -------- COORDINATED BY ------------------------------------------------------ * Michael Hess [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/services [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/services [5] https://www.drupal.org/project/services/releases/7.x-3.20 [6] https://www.drupal.org/project/services [7] https://www.drupal.org/user/58170 [8] https://www.drupal.org/user/XXXUID [9] https://www.drupal.org/user/58170 [10] https://www.drupal.org/u/mlhess [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

Drupal Core - Multiple Vulnerabilities - SA-CORE-2017-003
by security-news＠drupal.org 21 Jun '17

21 Jun '17

View online: https://www.drupal.org/SA-CORE-2017-003 Drupal 8.3.4 and Drupal 7.56, are maintenance releases which contain fixes for security vulnerabilities. Download Drupal 8.3.4 [1] Download Drupal 7.56 [2] *Updating your existing Drupal 8 and 7 sites is strongly recommended (see instructions for Drupal 8 [3] and for Drupal 7 [4]).* This release fixes security issues only; there are no new features nor non-security-related bug fixes in this release. See the 8.3.4 release notes [5] and the 7.56 release notes [6] for details on important changes and known issues affecting this release. Read on for details of the security vulnerabilities that were fixed in this release. * Advisory ID: DRUPAL-SA-CORE-2017-003 * Project: Drupal core [7] * Version: 7.x, 8.x * Date: 2017-June-21 * Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- .... PECL YAML parser unsafe object handling - Critical - Drupal 8 - CVE-2017-6920 PECL YAML parser does not handle PHP objects safely during certain operations within Drupal core. This could lead to remote code execution. .... File REST resource does not properly validate - Less Critical - Drupal 8 - CVE-2017-6921 The file REST resource does not properly validate some fields when manipulating files. A site is only affected by this if the site has the RESTful Web Services (rest) module enabled, the file REST resource is enabled and allows PATCH requests, and an attacker can get or register a user account on the site with permissions to upload files and to modify the file resource. .... Files uploaded by anonymous users into a private file system can be accessed by other anonymous users - Moderately Critical - Drupal 7 and Drupal 8 - CVE-2017-6922 Private files that have been uploaded by an anonymous user but not permanently attached to content on the site should only be visible to the anonymous user that uploaded them, rather than all anonymous users. Drupal core did not previously provide this protection, allowing an access bypass vulnerability to occur. This issue is mitigated by the fact that in order to be affected, the site must allow anonymous users to upload files into a private file system. The security team has also received reports that this vulnerability is being exploited for spam purposes, similar to the scenario discussed in PSA-2016-003 [8] for the public file system. -------- VERSIONS AFFECTED --------------------------------------------------- * Drupal core 7.x versions prior to 7.56 [9] * Drupal core 8.x versions prior to 8.3.4 [10] -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use Drupal 7.x, upgrade to Drupal core 7.56 [11] * If you use Drupal 8.x, upgrade to Drupal core 8.3.4 [12] Also see the Drupal core [13] project page. -------- REPORTED BY --------------------------------------------------------- .... PECL YAML parser unsafe object handling * Samuel Mortenson [14] .... File REST resource does not properly validate * Samuel Mortenson [15] .... Files uploaded by anonymous users into a private file system can be accessed by other anonymous users * Greg Knaddison [16] of the Drupal Security team * Mori Sugimoto [17] of the Drupal Security team * iancawthorne [18] -------- FIXED BY ------------------------------------------------------------ .... PECL YAML parser unsafe object handling * XJM [19] of the Drupal Security team * Alex Pott [20] of the Drupal Security team * Peter Wolanin [21] of the Drupal Security team .... File REST resource does not properly validate * Samuel Mortenson [22] * Wim Leers [23] * Alex Pott [24] of the Drupal Security team * XJM [25] of the Drupal Security team * Sascha Grossenbacher [26] .... Files uploaded by anonymous users into a private file system can be accessed by other anonymous users * David Rothstein [27] of the Drupal Security team * Peter Wolanin [28] of the Drupal Security team * Michael Hess [29] of the Drupal Security team * XJM [30] of the Drupal Security team * Chris McCafferty [31] of the Drupal Security team * Lee Rowlands [32] of the Drupal Security team * Alex Pott [33] of the Drupal Security team * Nathaniel Catchpole [34] of the Drupal Security team * Stefan Ruijsenaars [35] of the Drupal Security team * Nate Haug [36] * Gareth Goodwin [37] -------- 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 [38]. Learn more about the Drupal Security team and their policies [39], writing secure code for Drupal [40], and securing your site [41]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [42] [1] http://ftp.drupal.org/files/projects/drupal-8.3.4.tar.gz [2] http://ftp.drupal.org/files/projects/drupal-7.56.tar.gz [3] https://www.drupal.org/node/2700999 [4] https://www.drupal.org/node/1494290 [5] https://www.drupal.org/project/drupal/releases/8.3.4 [6] https://www.drupal.org/project/drupal/releases/7.56 [7] https://www.drupal.org/project/drupal [8] https://www.drupal.org/psa-2016-003 [9] https://www.drupal.org/project/drupal/releases/7.56 [10] https://www.drupal.org/project/drupal/releases/8.3.4 [11] https://www.drupal.org/project/drupal/releases/7.56 [12] https://www.drupal.org/project/drupal/releases/8.3.4 [13] https://www.drupal.org/project/drupal [14] https://www.drupal.org/user/2582268 [15] https://www.drupal.org/user/2582268 [16] https://www.drupal.org/u/greggles [17] https://www.drupal.org/u/dokumori [18] https://www.drupal.org/u/iancawthorne [19] https://www.drupal.org/u/xjm [20] https://www.drupal.org/u/alexpott [21] https://www.drupal.org/u/pwolanin [22] https://www.drupal.org/u/samuel.mortenson [23] https://www.drupal.org/u/wim-leers [24] https://www.drupal.org/u/alexpott [25] https://www.drupal.org/u/xjm [26] https://www.drupal.org/u/Berdir [27] https://www.drupal.org/u/David_Rothstein [28] https://www.drupal.org/u/pwolanin [29] https://www.drupal.org/u/mlhess [30] https://www.drupal.org/u/xjm [31] https://www.drupal.org/u/cilefen [32] https://www.drupal.org/u/larowlan [33] https://www.drupal.org/u/alexpott [34] https://www.drupal.org/u/catch [35] https://www.drupal.org/u/stefanr-0 [36] https://www.drupal.org/u/quicksketch [37] https://www.drupal.org/u/smaz [38] https://www.drupal.org/contact [39] https://www.drupal.org/security-team [40] https://www.drupal.org/writing-secure-code [41] https://www.drupal.org/security/secure-configuration [42] https://twitter.com/drupalsecurity

1 0