- Security-news - lists.drupal.org

SA-CONTRIB-2015-057 - Spider Contacts - Multiple vulnerabilities - Unsupported
by security-news＠drupal.org 25 Feb '15

25 Feb '15

View online: https://www.drupal.org/node/2437973 * Advisory ID: DRUPAL-SA-CONTRIB-2015-057 * Project: Spider Contacts [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-February-25 * Security risk: 20/25 ( Highly Critical) AC:Basic/A:None/CI:All/II:All/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Request Forgery, SQL Injection, Multiple vulnerabilities -------- DESCRIPTION --------------------------------------------------------- Spider Contacts module provides a user-friendly way to manage and display contacts. The module doesn't use Drupal's Database API properly, not sanitizing user input on SQL queries and thereby exposing a SQL Injection vulnerability. This vulnerability is mitigated by the fact that the attacker must have a role with the permission "access Spider Contacts category administration". Additionally, the module doesn't sufficiently protect some URLs against CSRF. A malicious user could trick an administrator into deleting contact categories by getting their browser to make a request to a specially-crafted 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 --------------------------------------------------- All versions of Spider Contacts module. Drupal core is not affected. If you do not use the contributed Spider Contacts [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Spider Contacts module you should uninstall it. Also see the Spider Contacts [5] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [7] 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 [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] https://www.drupal.org/project/spider-contacts [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/spider-contacts [5] https://www.drupal.org/project/spider-contacts [6] https://www.drupal.org/user/2301194 [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/contact [9] https://www.drupal.org/security-team [10] https://www.drupal.org/writing-secure-code [11] https://www.drupal.org/security/secure-configuration [12] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-056 - inLinks Integration - Cross Site Scripting (XSS) - Unsupported
by security-news＠drupal.org 25 Feb '15

25 Feb '15

View online: https://www.drupal.org/node/2437969 * Advisory ID: DRUPAL-SA-CONTRIB-2015-056 * Project: inLinks Integration [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-February-25 * Security risk: 16/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- inLinks Integration module enables you to use inLinks product from Text Link Ads third-party service. The module doesn't sufficiently sanitize user input in some path arguments, thereby exposing a Cross Site Scripting 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 --------------------------------------------------- All versions of inLinks Integration module. Drupal core is not affected. If you do not use the contributed inLinks Integration [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the inLinks Integration module you should uninstall it. Also see the inLinks Integration [5] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [7] 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 [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] https://www.drupal.org/project/inlinks [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/inlinks [5] https://www.drupal.org/project/inlinks [6] https://www.drupal.org/user/2301194 [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/contact [9] https://www.drupal.org/security-team [10] https://www.drupal.org/writing-secure-code [11] https://www.drupal.org/security/secure-configuration [12] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-055 - Services single sign-on server helper - Open Redirect - Unsupported
by security-news＠drupal.org 25 Feb '15

25 Feb '15

View online: https://www.drupal.org/node/2437965 * Advisory ID: DRUPAL-SA-CONTRIB-2015-055 * Project: Services single sign-on server helper [1] (third-party module) * Version: 7.x * Date: 2015-February-25 * Security risk: 10/25 ( Moderately Critical) AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:All [2] * Vulnerability: Open Redirect -------- DESCRIPTION --------------------------------------------------------- Services single sign-on server helper module provides functionality to facilitate account information editing on a remote SSO site. The module doesn't validate some user supplied URLs in parameters used for page redirection. An attacker could trick users to visit malicious sites without realizing it. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- All versions of Services single sign-on server helper module. Drupal core is not affected. If you do not use the contributed Services single sign-on server helper [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Services single sign-on server helper module you should uninstall it. Also see the Services single sign-on server helper [5] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [6] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [7] 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 [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] https://www.drupal.org/project/services_sso_server_helper [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/services_sso_server_helper [5] https://www.drupal.org/project/services_sso_server_helper [6] https://www.drupal.org/user/2301194 [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/contact [9] https://www.drupal.org/security-team [10] https://www.drupal.org/writing-secure-code [11] https://www.drupal.org/security/secure-configuration [12] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-054 - SMS Framework - Cross Site Scripting (XSS)
by security-news＠drupal.org 25 Feb '15

25 Feb '15

View online: https://www.drupal.org/node/2437943 * Advisory ID: DRUPAL-SA-CONTRIB-2015-054 * Project: SMS Framework [1] (third-party module) * Version: 6.x * Date: 2015-February-25 * Security risk: 15/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- SMS Framework module enables you to send and receive SMS messages from and into Drupal. The module doesn't sufficiently sanitize user supplied text in message previews, thereby exposing a reflected Cross Site Scripting vulnerability. An attacker could exploit this vulnerability by getting the victim to visit a specially-crafted URL. This vulnerability is mitigated by the fact that the "Send to phone" 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 --------------------------------------------------- * SMS Framework 6.x-1.x versions prior to 6.x-1.1. Drupal core is not affected. If you do not use the contributed SMS Framework [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the SMS Framework module for Drupal 6.x, upgrade to SMS Framework 6.x-1.1 [5] Also see the SMS Framework [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Reinier Battenberg [8] one of the module maintainers * Pere Orga [9] of the Drupal Security Team -------- 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/smsframework [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/smsframework [5] https://www.drupal.org/node/2431717 [6] https://www.drupal.org/project/smsframework [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/2696 [9] https://www.drupal.org/user/2301194 [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

SA-CONTRIB-2015-053 - Entity API - Cross Site Scripting (XSS)
by security-news＠drupal.org 25 Feb '15

25 Feb '15

View online: https://www.drupal.org/node/2437905 * Advisory ID: DRUPAL-SA-CONTRIB-2015-053 * Project: Entity API [1] (third-party module) * Version: 7.x * Date: 2015-February-25 * Security risk: 12/25 ( Moderately Critical) AC:Complex/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- 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. The module doesn't sufficiently sanitize field labels when exposing them through the Token API thereby exposing a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission to administer fields such as "administer taxonomy". -------- 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.6. 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.6 [5] Also see the Entity API [6] project page. -------- REPORTED BY --------------------------------------------------------- * Francisco José Cruz Romanos [7] -------- FIXED BY ------------------------------------------------------------ * Klaus Purer [8] of the Drupal Security Team * Francisco José Cruz Romanos [9] * Wolfgang Ziegler [10] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [11] of the Drupal Security Team * Rick Manelius [12] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact [13]. Learn more about the Drupal Security team and their policies [14], writing secure code for Drupal [15], and securing your site [16]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [17] [1] https://www.drupal.org/project/entity [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/entity [5] https://www.drupal.org/node/2437885 [6] https://www.drupal.org/project/entity [7] https://www.drupal.org/user/848238 [8] https://www.drupal.org/u/klausi [9] https://www.drupal.org/user/848238 [10] https://www.drupal.org/user/16747 [11] https://www.drupal.org/u/klausi [12] https://www.drupal.org/u/rickmanelius [13] https://www.drupal.org/contact [14] https://www.drupal.org/security-team [15] https://www.drupal.org/writing-secure-code [16] https://www.drupal.org/security/secure-configuration [17] https://twitter.com/drupalsecurity

1 0

SA-CONTRIB-2015-052 - RESTful Web Services - Access Bypass
by security-news＠drupal.org 18 Feb '15

18 Feb '15

View online: https://www.drupal.org/node/2428863 * Advisory ID: DRUPAL-SA-CONTRIB-2015-052 * Project: RESTful Web Services [1] (third-party module) * Version: 7.x * Date: 2015-February-18 * Security risk: 12/25 ( Moderately Critical) AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- This module enables you to expose Drupal entities as RESTful web services. It provides a machine-readable interface to exchange resources in JSON, XML and RDF. The RESTWS Basic Auth submodule doesn't sufficiently disable page caching for authenticated requests thereby leaking potentially confidential data to unauthorized users. This vulnerability is mitigated by the fact that the RESTWS Basic Auth submodule must be enabled, page caching must be enabled and permissions for a resource containing sensitive data must be enabled (for example the User resource). -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * RESTWS 7.x-1.x versions prior to 7.x-1.5. * RESTWS 7.x-2.x versions prior to 7.x-2.3. Drupal core is not affected. If you do not use the contributed RESTful Web Services [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the RESTWS module for Drupal 7.x, upgrade to RESTWS 7.x-1.5 [5] or RESTWS 7.x-2.3 [6] Also see the RESTful Web Services [7] project page. -------- REPORTED BY --------------------------------------------------------- * Jason Little [8] -------- FIXED BY ------------------------------------------------------------ * Klaus Purer [9] the module maintainer and member of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Klaus Purer [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/restws [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/restws [5] https://www.drupal.org/node/2428857 [6] https://www.drupal.org/node/2428855 [7] https://www.drupal.org/project/restws [8] https://www.drupal.org/user/143477 [9] https://www.drupal.org/u/klausi [10] https://www.drupal.org/u/klausi [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

SA-CONTRIB-2015-051 - Term Queue - Cross Site Scripting (XSS)
by security-news＠drupal.org 18 Feb '15

18 Feb '15

View online: https://www.drupal.org/node/2428853 * Advisory ID: DRUPAL-SA-CONTRIB-2015-051 * Project: Term Queue [1] (third-party module) * Version: 6.x * Date: 2015-February-18 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Term Queue module allows you to create lists of taxonomy terms and display them in a block. The module doesn't sufficiently sanitize user supplied text in some administration pages, thereby exposing a Cross Site Scripting vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer taxonomy". -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Term Queue 6.x-1.0 Drupal core is not affected. If you do not use the contributed Term Queue [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Term Queue module for Drupal 6.x, upgrade to Term Queue 6.x-1.1 [5] Also see the Term Queue [6] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [7] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Edward Crompton [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [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/term_queue [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/term_queue [5] https://www.drupal.org/node/2428483 [6] https://www.drupal.org/project/term_queue [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/u/eddie_c [9] https://www.drupal.org/user/2301194 [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

SA-CONTRIB-2015-050 - Services Basic Authentication - Access bypass - Unsupported
by security-news＠drupal.org 18 Feb '15

18 Feb '15

View online: https://www.drupal.org/node/2428851 * Advisory ID: DRUPAL-SA-CONTRIB-2015-050 * Project: Services Basic Authentication [1] (third-party module) * Version: 7.x * Date: 2015-February-18 * Security risk: 15/25 ( Critical) AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:All [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- Services Basic Authentication module adds HTTP basic authentication for Services module. A user could get unauthorized access to resources under some circumstances. This vulnerability is mitigated by the fact that the authentication works correctly when page caching is disabled. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * All versions of Services Basic Authentication module. Drupal core is not affected. If you do not use the contributed Services Basic Authentication [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ If you use the Services Basic Authentication module you should uninstall it Also see the Services Basic Authentication [5] project page. -------- REPORTED BY --------------------------------------------------------- * Marvin Whitfield [6] * Matt Supko [7] -------- FIXED BY ------------------------------------------------------------ Not applicable. -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [8] of the Drupal Security Team * Mori Sugimoto [9] of the Drupal Security Team * 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/services_basic_auth [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/services_basic_auth [5] https://www.drupal.org/project/services_basic_auth [6] https://www.drupal.org/user/631814 [7] https://www.drupal.org/user/499020 [8] https://www.drupal.org/user/36762 [9] https://www.drupal.org/user/82971 [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

SA-CONTRIB-2015-049 - Navigate - Cross Site Scripting (XSS)
by security-news＠drupal.org 18 Feb '15

18 Feb '15

View online: https://www.drupal.org/node/2428815 * Advisory ID: DRUPAL-SA-CONTRIB-2015-049 * Project: Navigate [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-February-18 * Security risk: 16/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- Navigate is a customizable navigation bar for Drupal. The module doesn't sufficiently sanitize user input when displaying the Navigate bar. Because the vulnerability is a Reflected Cross Site Scripting, the only mitigating factor is that the victim must be tricked into visiting a specially crafted malicious 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 --------------------------------------------------- * Navigate 6.x-1.x versions prior to 6.x-1.1. * Navigate 7.x-1.x versions prior to 7.x-1.1. Drupal core is not affected. If you do not use the contributed Navigate [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Navigate module for Drupal 6.x, upgrade to Navigate 6.x-1.1 [5] * If you use the Navigate module for Drupal 7.x, upgrade to Navigate 7.x-1.1 [6] Also see the Navigate [7] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [8] of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Amit Goyal [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/navigate [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/navigate [5] https://www.drupal.org/node/2428505 [6] https://www.drupal.org/node/2428503 [7] https://www.drupal.org/project/navigate [8] https://www.drupal.org/user/2301194 [9] https://www.drupal.org/user/56441 [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

SA-CONTRIB-2015-048 - Avatar Uploader - Arbitrary PHP code execution
by security-news＠drupal.org 18 Feb '15

18 Feb '15

View online: https://www.drupal.org/node/2428793 * Advisory ID: DRUPAL-SA-CONTRIB-2015-048 * Project: Avatar Uploader [1] (third-party module) * Version: 6.x, 7.x * Date: 2015-February-18 * Security risk: 16/25 ( Critical) AC:None/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Arbitrary PHP code execution -------- DESCRIPTION --------------------------------------------------------- Avatar Uploader module provides an alternative way to upload user pictures. The module doesn't sufficiently enforce file extensions when an avatar is uploaded, allowing users to bypass Drupal's normal file upload protections to install malicious HTML or executable code to the server. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "upload avatar file", and that the fix for SA-2006-006 - Drupal Core - Execution of arbitrary files in certain Apache configurations [3] should prevent code execution in typical Apache configurations. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [4] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Avatar Uploader 6.x-1.x versions prior to 6.x-1.3. Drupal core is not affected. If you do not use the contributed Avatar Uploader [5] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Avatar Uploader module for Drupal 6.x, upgrade to Avatar Uploader 6.x-1.3 [6] Also see the Avatar Uploader [7] project page. -------- REPORTED BY --------------------------------------------------------- * Liran Tal [8] -------- FIXED BY ------------------------------------------------------------ * Robbin Gaoxin Zhao [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/avatar-uploader [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/node/65409 [4] http://cve.mitre.org/ [5] https://www.drupal.org/project/avatar-uploader [6] https://www.drupal.org/node/2427069 [7] https://www.drupal.org/project/avatar-uploader [8] https://www.drupal.org/user/1315712 [9] https://www.drupal.org/user/616818 [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