Security-news July 2017

security-news@drupal.org

1 participants
4 discussions

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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Security-news July 2017