Security-news January 2014

security-news@drupal.org

1 participants
10 discussions

SA-CONTRIB-2014-008 - Tribune - Cross Site Scripting (XSS)
by security-news＠drupal.org 29 Jan '14

29 Jan '14

View online: https://drupal.org/node/2184845 * Advisory ID: DRUPAL-SA-CONTRIB-2014-008 * Project: Tribune [1] (third-party module) * Version: 6.x, 7.x * Date: 2014-January-29 * Security risk: Highly critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- A tribune is a type of chatroom. The module doesn't sufficiently filter user provided text from Tribune node titles. This vulnerability is mitigated by the fact that an attacker must have a role with the permission to create a Tribune node. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Tribune 6.x-1.x versions. * Tribune 7.x-3.x versions. Drupal core is not affected. If you do not use the contributed Tribune [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Remove the module or otherwise mitigate the issue. Also see the Tribune [5] project page. -------- REPORTED BY --------------------------------------------------------- * Raynald Mirville [6] -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Laurence Liss [7] provisional member of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at http://drupal.org/contact [8]. Learn more about the Drupal Security team and their policies [9], writing secure code for Drupal [10], and securing your site [11]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [12] [1] http://drupal.org/project/tribune [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/tribune [5] http://drupal.org/project/tribune [6] http://drupal.org/user/2737379 [7] http://drupal.org/user/724750 [8] http://drupal.org/contact [9] http://drupal.org/security-team [10] http://drupal.org/writing-secure-code [11] http://drupal.org/security/secure-configuration [12] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-007 - Services - Multiple access bypass vulnerabilities
by security-news＠drupal.org 29 Jan '14

29 Jan '14

View online: https://drupal.org/node/2184843 * Advisory ID: DRUPAL-SA-CONTRIB-2014-007 * Project: Services [1] (third-party module) * Version: 7.x * Date: 2014-January-29 * Security risk: Highly critical [2] * Exploitable from: Remote * Vulnerability: Multiple access bypass vulnerabilities -------- DESCRIPTION --------------------------------------------------------- This module enables you to expose an API to third party systems using REST, XML-RPC or other protocols. The form API provides a method for developers to submit forms programmatically using the function drupal_form_submit(). During programmatic form submissions, all access checks are deliberately bypassed, and any form element may be submitted regardless of the current user's access level. To facilitate this, a new, optional $form_state['programmed_bypass_access_check'] element has been added to the Drupal 7 form API. If this is provided and set to FALSE, drupal_form_submit() will perform the normal form access checks against the current user while submitting the form, rather than bypassing them. Services relies heavily on programmatic form submission and therefore needs to use this new $form_state['programmed_bypass_access_check'] so that access control parameters and hooks are performed for untrusted users. -------- 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.5. Drupal core is not affected. If you do not use the contributed Services [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Services module for Drupal 7.x, upgrade to Services 7.x-3.6 [5] Also see the Services [6] project page. -------- REPORTED BY --------------------------------------------------------- * wedge [7] * prjcarr [8] -------- FIXED BY ------------------------------------------------------------ * David Rothstein [9] of the Drupal Security Team * Hunter Fox [10] of the Drupal Security Team * Kyle Browning [11], the module maintainer. -------- COORDINATED BY ------------------------------------------------------ * Hunter Fox [12] of the Drupal Security Team * Klaus Purer [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 http://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] http://drupal.org/project/services [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/services [5] https://drupal.org/node/2180373 [6] http://drupal.org/project/services [7] https://drupal.org/user/11442 [8] https://drupal.org/user/1223090 [9] https://drupal.org/user/124982 [10] https://drupal.org/user/426416 [11] https://drupal.org/user/211387 [12] http://drupal.org/user/426416 [13] http://drupal.org/user/262198 [14] http://drupal.org/contact [15] http://drupal.org/security-team [16] http://drupal.org/writing-secure-code [17] http://drupal.org/security/secure-configuration [18] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-006 - Language Switcher Dropdown - Open Redirect
by security-news＠drupal.org 22 Jan '14

22 Jan '14

View online: https://drupal.org/node/2179123 * Advisory ID: DRUPAL-SA-CONTRIB-2014-006 * Project: Language Switcher Dropdown [1] (third-party module) * Version: 7.x * Date: 2014-January-22 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Open Redirect -------- DESCRIPTION --------------------------------------------------------- The Language Switcher Dropdown module enables you to place a block with a convenient drop-down language switcher. After choosing a value the user is redirected to the url of the relevant language. The module doesn't check that the url provided is a valid internal path prior to redirecting. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Language Switcher Dropdown 7.x-1.x versions prior to 7.x-1.4. Drupal core is not affected. If you do not use the contributed Language Switcher Dropdown [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Language switcher dropdown module for Drupal 7.x, upgrade to Language Switcher Dropdown 7.x-1.4 [5] Also see the Language Switcher Dropdown [6] project page. -------- REPORTED BY --------------------------------------------------------- * Eric Peterson [7] -------- FIXED BY ------------------------------------------------------------ * Mohammed J. Razem [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Lee Rowlands [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 http://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] http://drupal.org/project/lang_dropdown [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/lang_dropdown [5] https://drupal.org/node/1614372 [6] http://drupal.org/project/lang_dropdown [7] http://drupal.org/user/1467594 [8] https://drupal.org/user/255384 [9] http://drupal.org/user/395439 [10] http://drupal.org/contact [11] http://drupal.org/security-team [12] http://drupal.org/writing-secure-code [13] http://drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-005 - Leaflet - Access bypass
by security-news＠drupal.org 22 Jan '14

22 Jan '14

View online: https://drupal.org/node/2179103 * Advisory ID: DRUPAL-SA-CONTRIB-2014-005 * Project: Leaflet [1] (third-party module) * Version: 7.x * Date: 2014-January-22 * Security risk: Critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The Leaflet module enables you to display an interactive map using the Leaflet library, using entities as map features. The module exposes complete data from entities used as map features to any site visitor with a Javascript inspector (like Firebug). -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Leaflet 7.x-1.x versions prior to 7.x-1.1. Drupal core is not affected. If you do not use the contributed Leaflet [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Leaflet module version for Drupal 7.x, upgrade to Leaflet 7.x-1.1 [5] Also see the Leaflet [6] project page. -------- REPORTED BY --------------------------------------------------------- * Interdruper [7] * Chris Hood [8] -------- FIXED BY ------------------------------------------------------------ * Gabriel Carleton-Barnes [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 http://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] http://drupal.org/project/leaflet [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/leaflet [5] https://drupal.org/node/2178655 [6] http://drupal.org/project/leaflet [7] http://drupal.org/user/2437374 [8] http://drupal.org/user/279264 [9] http://drupal.org/user/1682976 [10] http://drupal.org/user/36762 [11] http://drupal.org/contact [12] http://drupal.org/security-team [13] http://drupal.org/writing-secure-code [14] http://drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-004 - Secure Cookie Data - Faulty Hashing
by security-news＠drupal.org 22 Jan '14

22 Jan '14

View online: https://drupal.org/node/2179099 * Advisory ID: DRUPAL-SA-CONTRIB-2014-004 * Project: Secure Cookie Data [1] (third-party module) * Version: 7.x * Date: 2014-January-22 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Information Disclosure, Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- This module allows for storing data securely in a cookie through implementing the Secure Cookie Protocol [3]. .... Ability to alter trusted data in the cookie The module did an incorrect comparison of the HMAC [4] value, allowing a bypass of the HMAC verification which allows changing the cookie value. .... Known encryption key value The key for the HMAC provided a default that was hardcoded. The module relied on the extension of the base class to provide a per site specific key. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [5] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Secure Cookie Data 7.x-2.x versions prior to 7.x-2.1. Drupal core is not affected. If you do not use the contributed Secure Cookie Data [6] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Secure Cookie Data module upgrade to Secure Cookie Data 7.x-2.1 [7] Also see the Secure Cookie Data [8] project page. -------- REPORTED BY --------------------------------------------------------- * Heine Deelstra [9] of the Drupal Security Team * Jonathan Kuma [10] module maintainer -------- FIXED BY ------------------------------------------------------------ * Antonio Almeida [11] and Jonathan Kuma [12] the module maintainers. -------- COORDINATED BY ------------------------------------------------------ * Heine Deelstra [13] and Greg Knaddison [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 http://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] http://drupal.org/project/secure_cookie_data [2] http://drupal.org/security-team/risk-levels [3] http://www.cse.msu.edu/~alexliu/publications/Cookie/cookie.pdf [4] http://en.wikipedia.org/wiki/Hash-based_message_authentication_code [5] http://cve.mitre.org/ [6] http://drupal.org/project/secure_cookie_data [7] https://drupal.org/node/2178505 [8] http://drupal.org/project/secure_cookie_data [9] https://drupal.org/user/17943 [10] https://drupal.org/user/1919440 [11] https://drupal.org/user/8859 [12] https://drupal.org/user/1919440 [13] https://drupal.org/user/17943 [14] https://drupal.org/user/36762 [15] http://drupal.org/contact [16] http://drupal.org/security-team [17] http://drupal.org/writing-secure-code [18] http://drupal.org/security/secure-configuration [19] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-003 - Doubleclick for Publishers DFP - Cross Site Scripting (XSS)
by security-news＠drupal.org 22 Jan '14

22 Jan '14

View online: https://drupal.org/node/2179085 * Advisory ID: DRUPAL-SA-CONTRIB-2014-003 * Project: Doubleclick for Publishers (DFP) [1] (third-party module) * Version: 7.x * Date: 2014-January-22 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module enables you to create blocks to place advertisements from the Google Double Click for Publishers API (DFP). The module doesn't sufficiently sanitize the slot names prior to output into HTML. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer dfp". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * DFP 7.x-1.x versions prior to 7.x-1.2. Drupal core is not affected. If you do not use the contributed Doubleclick for Publishers (DFP) [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the DFP module for Drupal 7.x, upgrade to Google DFP 7.x-1.2 [5] Also see the Doubleclick for Publishers (DFP) [6] project page. -------- REPORTED BY --------------------------------------------------------- * Matt Vance [7] -------- FIXED BY ------------------------------------------------------------ * Matt Vance [8] * Beth Binkovitz [9], provisional member of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Beth Binkovitz [10], provisional member of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at http://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] http://drupal.org/project/dfp [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/dfp [5] https://drupal.org/node/2172167 [6] http://drupal.org/project/dfp [7] https://drupal.org/user/88338 [8] http://drupal.org/user/88338 [9] https://drupal.org/user/161263 [10] https://drupal.org/user/161263 [11] http://drupal.org/contact [12] http://drupal.org/security-team [13] http://drupal.org/writing-secure-code [14] http://drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-002 - Anonymous Posting - Cross Site Scripting (XSS)
by security-news＠drupal.org 15 Jan '14

15 Jan '14

View online: https://drupal.org/node/2173321 * Advisory ID: DRUPAL-SA-CONTRIB-2014-002 * Project: Anonymous Posting [1] (third-party module) * Version: 7.x * Date: 2014-01-15 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module allows anonymous users to fill in their contact information (name, email and homepage) when posting any content type including Forum Topics. This allows the submitted name to be shown instead of the usual anonymous string provided by Drupal core. The module doesn't properly sanitize the name submitted by the anonymous user before it is output. This vulnerability is mitigated only by the fact that use of anonymous posting data must be enabled on a per content type basis by a user with permission to do so since it is not enabled by default. However when configured for it's intended purpose, the vulnerability is not mitigated. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Anonymous Posting 7.x-1.x versions 7.x-1.2 and 7.x-1.3 Drupal core is not affected. If you do not use the contributed Anonymous Posting [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ * Install the latest version: 7.x-1.4 [5] Also see the Anonymous Posting [6] project page. -------- REPORTED BY --------------------------------------------------------- * drikc [7] the module maintainer -------- FIXED BY ------------------------------------------------------------ * drikc [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Rick Manelius [9] provisional member of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at http://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] http://drupal.org/project/anonymous_posting [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/anonymous_posting [5] https://drupal.org/node/2173437 [6] http://drupal.org/project/anonymous_posting [7] http://drupal.org/user/13299 [8] http://drupal.org/user/13299 [9] http://drupal.org/user/680072 [10] http://drupal.org/contact [11] http://drupal.org/security-team [12] http://drupal.org/writing-secure-code [13] http://drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity

1 0

SA-CORE-2014-001 - Drupal core - Multiple vulnerabilities
by security-news＠drupal.org 15 Jan '14

15 Jan '14

View online: https://drupal.org/SA-CORE-2014-001 * Advisory ID: DRUPAL-SA-CORE-2014-001 * Project: Drupal core [1] * Version: 6.x, 7.x * Date: 2014-January-15 * Security risk: Highly critical [2] * Exploitable from: Remote * Vulnerability: Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- Multiple vulnerabilities were fixed in the supported Drupal core versions 6 and 7. .... Impersonation (OpenID module - Drupal 6 and 7 - Highly critical) A vulnerability was found in the OpenID module that allows a malicious user to log in as other users on the site, including administrators, and hijack their accounts. This vulnerability is mitigated by the fact that the malicious user must have an account on the site (or be able to create one), and the victim must have an account with one or more associated OpenID identities. .... Access bypass (Taxonomy module - Drupal 7 - Moderately critical) The Taxonomy module provides various listing pages which display content tagged with a particular taxonomy term. Custom or contributed modules may also provide similar lists. Under certain circumstances, unpublished content can appear on these pages and will be visible to users who should not have permission to see it. This vulnerability is mitigated by the fact that it only occurs on Drupal 7 sites which upgraded from Drupal 6 or earlier. .... Security hardening (Form API - Drupal 7 - Not critical) The form API provides a method for developers to submit forms programmatically using the function drupal_form_submit(). During programmatic form submissions, all access checks are deliberately bypassed, and any form element may be submitted regardless of the current user's access level. This is normal and expected behavior for most uses of programmatic form submissions; however, there are cases where custom or contributed code may need to send data provided by the current (untrusted) user to drupal_form_submit() and therefore need to respect access control on the form. To facilitate this, a new, optional $form_state['programmed_bypass_access_check'] element has been added to the Drupal 7 form API. If this is provided and set to FALSE, drupal_form_submit() will perform the normal form access checks against the current user while submitting the form, rather than bypassing them. This change does not fix a security issue in Drupal core itself, but rather provides a method for custom or contributed code to fix security issues that would be difficult or impossible to fix otherwise. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Drupal core 6.x versions prior to 6.30. * Drupal core 7.x versions prior to 7.26. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use Drupal 6.x, upgrade to Drupal core 6.30 [4]. * If you use Drupal 7.x, upgrade to Drupal core 7.26 [5]. Also see the Drupal core [6] project page. -------- REPORTED BY --------------------------------------------------------- * The OpenID module impersonation issue was reported by Christian Mainka [7] and Vladislav Mladenov. * The Taxonomy module access bypass issue was reported by Matt Vance [8], and by Damien Tournoud [9] of the Drupal Security Team. * The form API access bypass issue was reported by David Rothstein [10] of the Drupal Security Team. -------- FIXED BY ------------------------------------------------------------ * The OpenID module impersonation issue was fixed by Damien Tournoud [11], Heine Deelstra [12], Peter Wolanin [13], and David Rothstein [14], all of the Drupal Security Team. * The Taxonomy module access bypass issue was fixed by Jibran Ijaz [15], and by Lee Rowlands [16] of the Drupal Security Team. * The form API access bypass issue was fixed by Damien Tournoud [17] and David Rothstein [18] of the Drupal Security Team, and by Marc Ingram [19] and Kyle Browning [20]. -------- COORDINATED BY ------------------------------------------------------ * The Drupal Security Team [21] -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at http://drupal.org/contact [22]. Learn more about the Drupal Security team and their policies [23], writing secure code for Drupal [24], and securing your site [25]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [26] [1] http://drupal.org/project/drupal [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/drupal-6.30-release-notes [5] http://drupal.org/drupal-7.26-release-notes [6] http://drupal.org/project/drupal [7] https://drupal.org/user/1096424 [8] https://drupal.org/user/88338 [9] https://drupal.org/user/22211 [10] https://drupal.org/user/124982 [11] https://drupal.org/user/22211 [12] https://drupal.org/user/17943 [13] https://drupal.org/user/49851 [14] https://drupal.org/user/124982 [15] https://drupal.org/user/1198144 [16] https://drupal.org/user/395439 [17] https://drupal.org/user/22211 [18] https://drupal.org/user/124982 [19] https://drupal.org/user/77320 [20] https://drupal.org/user/211387 [21] http://drupal.org/security-team [22] http://drupal.org/contact [23] http://drupal.org/security-team [24] http://drupal.org/writing-secure-code [25] http://drupal.org/security/secure-configuration [26] https://twitter.com/drupalsecurity

1 0

PSA-2014-001 - Media - Access Bypass
by security-news＠drupal.org 08 Jan '14

08 Jan '14

View online: https://drupal.org/node/2169767 * Advisory ID: PSA-2014-001 * Project: Media [1] (third-party module) * Version: 7.x * Date: 2014-01-08 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access Bypass -------- DESCRIPTION --------------------------------------------------------- This is a public service announcement regarding the "import media" permission, labeled as "Import media files from the local file system," provided by the Media module. The Media module provides a method for Drupal administrators to import existing files from an arbitrary location on the server. Users with the 'import media' permission can import any file from the server as local Drupal files, even those outside the Drupal install directory, which could lead to information disclosure. As such, this permission should be granted to trusted site administrators. In the 7.x-2.x version of the module, you may disable the sub-module named "Media Bulk Upload" to disable this functionality. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Media module for Drupal 7.x Drupal core is not affected. If you do not use the contributed Media [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Only grant trusted site administrators the "import media" permission. This permission is not marked as a restricted permission in the following versions: * Media module 7.x-1.x versions prior to 7.x-1.4 [5] * Media module 7.x-2.x versions prior to 7.x-2.0-alpha3+37-dev Upgrading to the latest release is recommended, but not required. Also see the Media [6] project page. -------- REPORTED BY --------------------------------------------------------- * robearls [7] * Dave Reid [8] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Dave Reid [9] the module maintainer and of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Dave Reid [10] the module maintainer and 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 http://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] http://drupal.org/project/media [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/media [5] https://drupal.org/node/2169795 [6] http://drupal.org/project/media [7] https://drupal.org/user/2460638 [8] https://drupal.org/user/53892 [9] https://drupal.org/user/53892 [10] http://drupal.org/user/53892 [11] http://drupal.org/contact [12] http://drupal.org/security-team [13] http://drupal.org/writing-secure-code [14] http://drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2014-001 - Entity API - Access Bypass
by security-news＠drupal.org 08 Jan '14

08 Jan '14

View online: https://drupal.org/node/2169595 * Advisory ID: DRUPAL-SA-CONTRIB-2014-001 * Project: Entity API [1] (third-party module) * Version: 7.x * Date: 2014-January-08 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The Entity API module extends the entity API of Drupal core in order to provide a unified way to deal with entities and their properties. .... Comment, User and Node Statistics property access bypass The module's entity wrapper access API doesn't sufficiently protect comment, user and node statistics properties from unprivileged user access. This vulnerability is mitigated by the fact that a module must be enabled that relies on the Entity property access API and it must be configured to expose either comment, user or node statistics properties. One example would be the RESTful Web Services module (RESTWS) with the permission configured to access the comment, user or node resource for untrusted web service consumers. .... Entity list property access bypass The module's entity wrapper access API doesn't sufficiently check entity access on referenced entities such as taxonomy terms. This vulnerability is mitigated by the fact that a module must be enabled that uses the access() method of entity metadata wrappers to determine access to a property which references multiple entities to which access is not granted. One example would be the RESTful Web Services module (RESTWS) with respectively configured permissions on an entity property or (entity reference) field, for example a list of (unaccessible) referenced user entities on a node entity. .... Unpublished comments access bypass The module's entity_access() API doesn't protect unpublished comments from being viewed by unprivileged users. This vulnerability is mitigated by the fact a module must be enabled which uses the provided entity access API on comments and the comment module 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 --------------------------------------------------- * Entity API 7.x-1.x versions prior to 7.x-1.3. Drupal core is not affected. If you do not use the contributed Entity API [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Entity API module for Drupal 7.x, upgrade to Entity API 7.x-1.3 [5] Also see the Entity API [6] project page. -------- REPORTED BY --------------------------------------------------------- * The Comment, User and Node Statistics property access bypass was reported by Clemens Tolboom [7]. * The Entity list property access bypass was reported by Neil Drumm [8] of the Drupal Security Team. * The Unpublished comments access bypass was reported by Ezra Barnett Gildesgame [9]. -------- FIXED BY ------------------------------------------------------------ * The Comment, User and Node Statistics property access bypass was fixed by Klaus Purer [10] of the Drupal Security Team, Wolfgang Zieger [11] the module maintainer, Clemens Tolboom [12] and Herman van Rink [13]. * The Entity list property access bypass was fixed by Wolfgang Zieger [14] the module maintainer. * The Unpublished comments access bypass was fixed by Klaus Purer [15] of the Drupal Security Team and Jakob Perry [16]. -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [17] 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 http://drupal.org/contact [18]. Learn more about the Drupal Security team and their policies [19], writing secure code for Drupal [20], and securing your site [21]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [22] [1] http://drupal.org/project/entity [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/entity [5] https://drupal.org/node/2169589 [6] http://drupal.org/project/entity [7] https://drupal.org/user/125814 [8] https://drupal.org/user/3064 [9] https://drupal.org/user/69959 [10] https://drupal.org/user/262198 [11] https://drupal.org/user/16747 [12] https://drupal.org/user/125814 [13] https://drupal.org/user/449000 [14] https://drupal.org/user/16747 [15] https://drupal.org/user/262198 [16] https://drupal.org/user/45640 [17] https://drupal.org/user/262198 [18] http://drupal.org/contact [19] http://drupal.org/security-team [20] http://drupal.org/writing-secure-code [21] http://drupal.org/security/secure-configuration [22] 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 January 2014