• Advisory ID: DRUPAL-SA-CONTRIB-2015-128
• Project: me aliases (third-party module)
• Version: 6.x, 7.x
• Date: 2015-June-24
• Security risk: 11/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:None/E:Theoretical/TD:All
• Vulnerability: Access bypass

Description

‘me aliases’ module provides shortcut paths to current user’s pages, eg user/me, blog/me, user/me/edit, tracker/me etc.

The view user argument handler for the ‘me’ module has an access bypass vulnerability where it does not check the supplied argument against the current user. This allows any user to access the content served by the view by substituting ‘me’ in the URL with a user id even when they don’t have permission to access the content.

These only affects Views which use the Views ‘me’ user argument handler.

CVE identifier(s) issued

• A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

• me aliases 7.x-1.x versions prior to 7.x-1.2
• me aliases 6.x-2.x versions prior to 6.x-2.10

Drupal core is not affected. If you do not use the contributed me aliases module, there is nothing you need to do.

Solution

Install the latest version:

• If you use the ‘me aliases’ module for Drupal 7.x, upgrade to me 7.x-1.2
• If you use the ‘me aliases’ module for Drupal 6.x, upgrade to me 6.x-2.10

Also see the me aliases project page.

Reported by

• akosipax

Fixed by

• nohup the module maintainer
• Stella Power of the Drupal Security Team

Coordinated by

• Stella Power 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.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

• Advisory ID: DRUPAL-SA-CONTRIB-2015-127
• Project: HybridAuth Social Login (third-party module)
• Version: 7.x
• Date: 2015-June-24
• Security risk: 8/25 ( Less Critical) AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:Uncommon
• Vulnerability: Access bypass

Description

The HybridAuth Social Login module enables you to allow visitors to authenticate or login to a Drupal site using their identities from social networks like Facebook or Twitter.

The module allows account creation through social login when the configuration is set to allow user registration by administrators only.

This vulnerability is mitigated by the fact that a site must be configured to allow user registration by administrators only and that authenticated user accounts can access sensitive data that would otherwise not be shown to anonymous users.

CVE identifier(s) issued

• A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

• HybridAuth Social Login 7.x-2.x versions prior to 7.x-2.13.

Drupal core is not affected. If you do not use the contributed HybridAuth Social Login module, there is nothing you need to do.

Solution

Install the latest version:

• If you use the HybridAuth Social Login module for Drupal 7.x, upgrade to HybridAuth Social Login 7.x-2.13

Also see the HybridAuth Social Login project page.

Reported by

• Tomas Fulopp

Fixed by

• Andrew Berezovsky the module maintainer

Coordinated by

• Klaus Purer 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.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

• Advisory ID: DRUPAL-SA-CONTRIB-2015-126
• Project: Content Construction Kit (CCK) (third-party module)
• Version: 6.x
• Date: 2015-June-17
• Security risk: 9/25 ( Less Critical) AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:Default
• Vulnerability: Open Redirect

Description

The Content Construction Kit (CCK) project is a set of modules that allows you to add custom fields to nodes using a web browser.

CCK uses a “destinations” query string parameter in URLs to redirect users to new destinations after completing an action on a few administration pages. Under certain circumstances, malicious users can use this parameter to construct a URL that will trick users into being redirected to a 3rd party website, thereby exposing the users to potential social engineering attacks.

See also: SA-CORE-2015-002

CVE identifier(s) issued

• A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

• Content Construction Kit (CCK) 6.x-2.x versions prior to 6.x-2.10.

Drupal core is not affected. If you do not use the contributed Content Construction Kit (CCK) module, there is nothing you need to do.

Solution

Install the latest version:

• If you use the Content Construction Kit (CCK) module for Drupal 6.x, upgrade to Content Construction Kit (CCK) 6.x-2.10

Also see the Content Construction Kit (CCK) project page.

Reported by

• Michael Smith
• David Rothstein of the Drupal Security Team

Fixed by

• Pere Orga of the Drupal Security Team
• Neil Drumm, module maintainer and member of the Drupal Security Team

Coordinated by

• 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.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

• Advisory ID: DRUPAL-SA-CONTRIB-2015-125
• Project: Acquia Cloud Site Factory Connector (third-party module)
• Version: 7.x
• Date: 2015-June-17
• Security risk: 9/25 ( Less Critical) AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:Default
• Vulnerability: Open Redirect

Description

Acquia Cloud Site Factory provides an environment and a robust set of tools that simplify management of many Drupal sites, allowing you to quickly deliver and manage any number of websites.

The module ships with a modified version of the core Overlay JavaScript file, which is vulnerable to an open redirect attack (see SA-CORE-2015-002).

Only sites with the Overlay module enabled are vulnerable.

CVE identifier(s) issued

• A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

• Acquia Cloud Site Factory 7.x-1.x versions prior to 7.x-1.14

Drupal core is not affected. If you do not use the contributed Acquia Cloud Site Factory Connector module, there is nothing you need to do.

Solution

Install the latest version:

• If you use the Acquia Cloud Site Factory module for Drupal 7.x, upgrade to Acquia Cloud Site Factory 7.x-1.14

Also see the Acquia Cloud Site Factory Connector project page.

Reported by

• Jeroen Vreuls
• David Rothstein of the Drupal Security Team
• Pere Orga of the Drupal Security Team

Fixed by

• Stéphane Corlosquet, module maintainer and member of the Drupal Security Team

Coordinated by

• 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.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

• Advisory ID: DRUPAL-SA-CONTRIB-2015-124
• Project: LABjs (third-party module)
• Version: 7.x
• Date: 2015-June-17
• Security risk: 9/25 ( Less Critical) AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:Default
• Vulnerability: Open Redirect

Description

The LABjs module integrates LABjs with Drupal for web performance optimization.

The module ships with a modified version of the core Overlay JavaScript file, which is vulnerable to an open redirect attack (see SA-CORE-2015-002).

Only sites with the Overlay module enabled are vulnerable.

CVE identifier(s) issued

• A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

• LABjs 7.x-1.x versions prior to 7.x-1.7.

Drupal core is not affected. If you do not use the contributed LABjs module, there is nothing you need to do.

Solution

Install the latest version:

• If you use the LABjs module for Drupal 7.x, upgrade to LABjs 7.x-1.7.

Also see the LABjs project page.

Reported by

• Jeroen Vreuls
• David Rothstein of the Drupal Security Team

Fixed by

• Pere Orga of the Drupal Security Team
• David Rothstein of the Drupal Security Team
• Hai-Nam Nguyen the module maintainer

Coordinated by

• 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.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

• Advisory ID: DRUPAL-SA-CONTRIB-2015-123
• Project: jQuery Update (third-party module)
• Version: 7.x
• Date: 2015-June-17
• Security risk: 9/25 ( Less Critical) AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:Default
• Vulnerability: Open Redirect

Description

The jQuery Update module enables you to update jQuery on your site.

The module ships with a modified version of the core Overlay JavaScript file, which is vulnerable to an open redirect attack (see SA-CORE-2015-002).

Only sites with the Overlay module enabled are vulnerable.

CVE identifier(s) issued

• A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

• jQuery Update 7.x-2.x versions prior to 7.x-2.6

Drupal core is not affected. If you do not use the contributed jQuery Update module, there is nothing you need to do.

Solution

Install the latest version:

• If you use the jQuery Update module 2.x branch, upgrade to jQuery Update 7.x-2.6

Also see the jQuery Update project page.

Reported by

• Jeroen Vreuls
• David Rothstein of the Drupal Security Team

Fixed by

• Pere Orga of the Drupal Security Team
• David Rothstein of the Drupal Security Team
• Rob Loach the module maintainer

Coordinated by

• 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.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

• Advisory ID: DRUPAL-SA-CORE-2015-002
• Project: Drupal core
• Version: 6.x, 7.x
• Date: 2015-June-17
• Security risk: 15/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:Default
• Vulnerability: Access bypass, Information Disclosure, Open Redirect, Multiple vulnerabilities

Description

Impersonation (OpenID module – Drupal 6 and 7 – 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 victim must have an account with an associated OpenID identity from a particular set of OpenID providers (including, but not limited to, Verisign, LiveJournal, or StackExchange).

Open redirect (Field UI module – Drupal 7 – Less critical)

The Field UI module uses a “destinations” query string parameter in URLs to redirect users to new destinations after completing an action on a few administration pages. Under certain circumstances, malicious users can use this parameter to construct a URL that will trick users into being redirected to a 3rd party website, thereby exposing the users to potential social engineering attacks.

This vulnerability is mitigated by the fact that only sites with the Field UI module enabled are affected.

Drupal 6 core is not affected, but see the similar advisory for the Drupal 6 contributed CCK module: SA-CONTRIB-2015-126

Open redirect (Overlay module – Drupal 7 – Less critical)

The Overlay module displays administrative pages as a layer over the current page (using JavaScript), rather than replacing the page in the browser window. The Overlay module does not sufficiently validate URLs prior to displaying their contents, leading to an open redirect vulnerability.

This vulnerability is mitigated by the fact that it can only be used against site users who have the “Access the administrative overlay” permission, and that the Overlay module must be enabled.

Information disclosure (Render cache system – Drupal 7 – Less critical)

On sites utilizing Drupal 7’s render cache system to cache content on the site by user role, private content viewed by user 1 may be included in the cache and exposed to non-privileged users.

This vulnerability is mitigated by the fact that render caching is not used in Drupal 7 core itself (it requires custom code or the contributed Render Cache module to enable) and that it only affects sites that have user 1 browsing the live site. Exposure is also limited if an administrative role has been assigned to the user 1 account (which is done, for example, by the Standard install profile that ships with Drupal core).

CVE identifier(s) issued

• Impersonation (OpenID module – Drupal 6 and 7): CVE-2015-3234
• Open redirect (Field UI module – Drupal 7): CVE-2015-3232
• Open redirect (Overlay module – Drupal 7: CVE-2015-3233
• Information disclosure (Render cache system – Drupal 7): CVE-2015-3231

Versions affected

• Drupal core 6.x versions prior to 6.36
• Drupal core 7.x versions prior to 7.38

Solution

Install the latest version:

• If you use Drupal 6.x, upgrade to Drupal core 6.36
• If you use Drupal 7.x, upgrade to Drupal core 7.38

Also see the Drupal core project page.

Reported by

Impersonation in the OpenID module:

• Vladislav Mladenov
• Christian Mainka
• Christian Koßmann

Open redirect in the Field UI module:

• Michael Smith

Open redirect in the Overlay module:

• Jeroen Vreuls
• David Rothstein of the Drupal Security Team

Information disclosure in the render cache system:

• Nathaniel Catchpole of the Drupal Security Team

Fixed by

Impersonation in the OpenID module:

• Christian Schmidt, OpenID module maintainer
• Christian Mainka
• Christian Koßmann

Open redirect in the Field UI module:

• Yves Chedemois, Field UI module maintainer
• Damien McKenna provisional member of the Drupal Security Team
• Pere Orga of the Drupal Security Team
• David Rothstein of the Drupal Security Team
• Klaus Purer of the Drupal Security Team

Open redirect in the Overlay module:

• Jeroen Vreuls
• Ben Dougherty of the Drupal Security Team
• David Rothstein of the Drupal Security Team
• Katherine Senzee, Overlay module maintainer

Information disclosure in the render cache system:

• David Rothstein of the Drupal Security Team
• Wim Leers
• willzyx

Coordinated by

• 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.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

• Advisory ID: DRUPAL-SA-CONTRIB-2015-122
• Project: Administration Views (third-party module)
• Version: 7.x
• Date: 2015-June-17
• Security risk: 12/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:Default
• Vulnerability: Access bypass

Description

This module replaces administrative overview/listing pages with Views for improved usability.

When combined with other contributed or custom modules, the Administration Views module improperly grants users access to administration pages including the permissions page.

This vulnerability is mitigated by the fact that it does not appear in the module itself, but only when combined with select other custom or contributed modules.

CVE identifier(s) issued

• A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

• Administration Views 7.x-1.x versions prior to 7.x-1.4.

Drupal core is not affected. If you do not use the contributed Administration Views module, there is nothing you need to do.

Solution

Install the latest version:

• If you use the Administration Views module for Drupal 7.x, upgrade to Administration Views 7.x-1.4

Also see the Administration Views project page.

Reported by

• Barry Fisher

Fixed by

• Robert

Coordinated by

• Pere Orga of the Drupal Security Team
• Greg Knaddison 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.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

• Advisory ID: DRUPAL-SA-CONTRIB-2015-121
• Project: The eXtensible Catalog (XC) Drupal Toolkit (third-party module)
• Version: 6.x, 7.x
• Date: 2015-June-17
• Security risk: 15/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:Default
• Vulnerability: Cross Site Request Forgery

Description

The eXtensible Catalog Drupal Toolkit is a set of Drupal modules to harvest records of the XC Schema format from a Metadata Services Toolkit (MST).

The XC NCIP Provider module doesn’t sufficiently protect some URLs against CSRF. A malicious user can cause a user with “administer ncip providers” permission to alter NCIP providers by getting their browser to make a request to a specially-crafted URL.

This vulnerability is mitigated by the fact that only sites that have the XC NCIP Provider module enabled are affected.

CVE identifier(s) issued

• A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

• All versions of The eXtensible Catalog (XC) Drupal Toolkit

Drupal core is not affected. If you do not use the contributed The eXtensible Catalog (XC) Drupal Toolkit module, there is nothing you need to do.

Solution

If you use The eXtensible Catalog (XC) Drupal Toolkit you should uninstall it.

Also see the The eXtensible Catalog (XC) Drupal Toolkit project page.

Reported by

• Pere Orga of the Drupal Security Team

Fixed by

Not applicable.

Coordinated by

• Pere Orga 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.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

• Advisory ID: DRUPAL-SA-CONTRIB-2015-120
• Project: Inline Entity Form (third-party module)
• Version: 7.x
• Date: 2015-June-17
• Security risk: 7/25 ( Less Critical) AC:Basic/A:Admin/CI:None/II:None/E:Theoretical/TD:All
• Vulnerability: Cross Site Scripting

Description

The Inline Entity Form module provides a field widget for inline management (creation, modification, removal) of referenced entities.

The module doesn’t sufficiently sanitize user supplied text, thereby exposing a Cross Site Scripting vulnerability.

This vulnerability is mitigated by the fact that an attacker must have a role with permission to create/edit fields.

CVE identifier(s) issued

• A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

• Inline Entity Form 7.x-1.x versions prior to 7.x-1.6.

Drupal core is not affected. If you do not use the contributed Inline Entity Form module, there is nothing you need to do.

Solution

Install the latest version:

• If you use the Inline Entity Form module for Drupal 7.x, upgrade to Inline Entity Form 7.x-1.6

Also see the Inline Entity Form project page.

Reported by

• Matt Vance, provisional member of the Drupal Security Team

Fixed by

• Matt Vance, 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 https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity