Project Security Advisories

Subscribe to Project Security Advisories feed
Updated: 24 min 2 sec ago

Token Insert Entity - Moderately Critical - Access bypass and information disclosure - SA-CONTRIB-2015-171

Wed, 12/02/2015 - 3:57pm
Description

This module offers a WYSIWYG button to embed rendered entities in fields using a WYSIWYG (normally the body of a node).

There is a vulnerability because a user that can create or edit content and has the "insert entity token" permission can insert tokens relating to e.g. an unpublished node and allow any (including anonymous) users to see this rendered node embedded into the main node.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Token Insert Entity 7.x-1.x versions prior to 7.x-1.1.

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

Solution

Install the latest version:

Also see the Token Insert Entity project page.

Reported by
  • killes of the Drupal Security Team
Fixed by Coordinated by 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

Drupal version: Drupal 7.x

Apache Solr Search - Moderately Critical - Access Bypass - SA-CONTRIB-2015-170

Wed, 12/02/2015 - 2:27pm
Description

This module enables you to connect to an Apache Solr search server to provide a replacement for Drupal core content search and provide both extra features and better search performance and relevance.

The module doesn't correctly check access when attempting to delete non-default search environments.

This vulnerability is mitigated by the fact that the site must have a non-default environment configured and an attacker must discover the ID of the environment.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Apache Solr Search 6.x-3.x versions prior to 6.x-3.1.
  • Apache Solr Search 7.x-1.x versions prior to 7.x-1.8.

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

Solution

Install the latest version:

Also see the Apache Solr Search project page.

Reported by Fixed by Coordinated by
  • Peter Wolanin of the Drupal Security Team, and a module maintainer
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

Drupal version: Drupal 6.xDrupal 7.x

Chat Room - Moderately Critical - Access Bypass - SA-CONTRIB-2015-169

Wed, 12/02/2015 - 12:01pm
Description

Chat Room enables site owners to integrate chats into nodes by adding the chat room field to them. The module relies on a websocket connection to send chat messages to the client.

The module doesn't sufficiently validate access before setting up the websocket. As a result, users may receive messages from chat rooms they don't have access to via the websocket.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Chat Room 7.x-2.x versions prior to 7.x-2.2.

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

Solution

Install the latest version:

Also see the Chat Room project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 7.x

Mollom - Critical - Access bypass - SA-CONTRIB-2015-168

Wed, 12/02/2015 - 11:17am
Description

The Mollom module allows users to protect their website from spam. As part of the spam protection, Mollom enables the website administrator to create a blacklist. When content is submitted that matches terms on the black list it will be automatically marked as spam and rejected per the site configuration.

The module doesn't sufficiently check for access when accessing or modifying the blacklist for the site. This enables a potential attacker to add, update, or remove their own terms to a site-wide blacklist. The potential exists for an attacker to remove existing blacklist terms which could allow their content to be accepted onto the site.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Mollom 6.x-2.x versions between 6.x-2.7 through 6.x-2.14.

This does not affect the modules for Drupal 7 or Drupal 8.

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

Solution

Install the latest version:

Also see the Mollom project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 6.x

RESTful - Less Critical - Access bypass - SA-CONTRIB-2015-167

Wed, 12/02/2015 - 11:15am
Description

RESTful module allows Drupal to be operated via RESTful HTTP requests, using best practices for security, performance, and usability.

The module doesn't sufficiently validate some user input. Specific code could be run arbitrarily by an attacker in certain circumstances.

This vulnerability is mitigated by the fact that only sites with a custom implementation of methods from a specific class are affected. Also, that custom code would need to affect data or impact the site in some way.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • RESTful 7.x-1.x versions prior to 7.x-1.6.

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

Solution

Install the latest version:

  • If you use the RESTful 7.x-1.x module for Drupal 7.x, upgrade to RESTful 7.x-1.6

Also see the RESTful project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 7.x

Encrypt - Moderately Critical - Weak Encryption - SA-CONTRIB-2015-166

Wed, 11/18/2015 - 3:10pm
Description

This module enables you to encrypt data within Drupal using a user-configurable encryption method and key provider.

The module did not sufficiently validate good configurations and api usage resulting in multiple potential weaknesses depending on module usage. The default encryption method could theoretically leak the key for known plaintexts. This vulnerability is mitigated by the fact that an attacker would need to have access to the encrypted data which is generally not possible without a breach of the database.

The default key provider uses the Drupal private key, which means that it could potentially be leaked which puts other elements of the site at risk. This vulnerability is mitigated by requiring the default combination of encryption method and key provider for the Drupal private key to be potentially leaked. Users of the module are likely to employ a key of their own creation, rather than use the Drupal private key.

Another encryption method included with the module uses a cipher that can leak structural information about the plaintext. This vulnerability is mitigated by the fact that it would only affect encryptions of large quantities of data, such as files and data of shorter lengths would not be affected.

The default key created by the module is generated by a MD5 hash, which is not as strong as using truly random bytes of data.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Encrypt 7.x-2.x versions prior to 7.x-2.2.

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

Solution

Install the latest version:

Once installed, review your settings and alter it to use a key provider and encryption method that is not deprecated. If data was encrypted with a deprecated key provider or encryption method then you should also re-encrypt all that data.

Also see the Encrypt project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 7.x

UC Profile - Moderately Critical - Information Disclosure - SA-CONTRIB-2015-165

Wed, 11/11/2015 - 11:45am
Description

UC Profile module enables you to collect profile fields for users during the checkout process of Ubercart as a checkout pane.

The module doesn't sufficiently check access to profiles under certain circumstances. Depending on the information being collected, sensitive data may be exposed.

This vulnerability is mitigated by the fact that only sites that store data to the anonymous user's profile 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
  • UC Profile 6.x-1.x versions prior to 6.x-1.3

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

Solution

Install the latest version:

Also see the UC Profile project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 6.x

MAYO theme - Moderately Critical - Cross Site Scripting (XSS) - SA-CONTRIB-2015-164

Wed, 11/11/2015 - 11:27am
Description

MAYO theme enables you to change certain theme settings via the administration interface.

Some theme settings aren't sufficiently sanitized.

This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Administer themes".

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • All MAYO 7.x-2.x versions prior to 7.x-2.6
  • All MAYO 7.x-1.x versions prior to 7.x-1.4

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

Solution

Install the latest version:

  • If you use the MAYO theme for Drupal 7.x-2.x, upgrade to MAYO 7.x-2.6
  • If you use the MAYO theme for Drupal 7.x-1.x, upgrade to MAYO 7.x-1.4

Also see the MAYO project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 7.x

Monster Menus - Access Bypass - Moderately Critical - SA-CONTRIB-2015-163

Wed, 11/04/2015 - 12:21pm
Description

Monster Menus is a hierarchical menu tree, which provides highly scalable, granular permissions for all pages within a site.

The module includes an option to remove nodes from view (add them to a "recycle bin") rather than deleting them outright. When a node has been put into a bin using an affected version of the module, it remains visible via a seldom-used URL pattern to the users to whom it had been visible previously, when it was outside of the recycle bin.

This vulnerability is mitigated by the facts that:

  1. Sites which do not use the recycle bin feature are not vulnerable.
  2. The exposed node is no more accessible than it had been before being placed into the recycle bin. If the node could not be read by a particular user while it was on the regular page, it would still be unreadable by that user when in the recycle bin.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Monster Menus versions 7.x-1.21 through 7.x-1.23.

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

Solution

Install the latest version:

Also see the Monster Menus project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 7.x

Login Disable - Access Bypass - Moderately Critical - SA-CONTRIB-2015-162

Wed, 11/04/2015 - 11:13am
Description

This module enables you to prevent existing users from logging in to your Drupal site unless they know the secret key to add to the end of the ?q=user login form page.

The Login Disable module doesn't support other contributed user authentication modules like CAS or URL Login. When combined with those modules, the protection preventing a user from logging in does not work.

This vulnerability is mitigated by the fact that an attacker must already have a user account to log in. This bug therefore allows users to log in even if they do not have permission to login.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Login Disable 6.x-1.x versions prior to 6.x-1.1.
  • Login Disable 7.x-1.x versions prior to 7.x-1.2.

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

Solution

Install the latest version:

Also see the Login Disable project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 6.xDrupal 7.x

Field as Block - Less Critical - Information Disclosure - SA-CONTRIB-2015-161

Wed, 10/28/2015 - 11:58am
Description

This module enables you to take a field from the current entity and place it elsewhere as a block.

The module caches the block output in a manner that could allow sensitive content to be seen by visitors who should not see it.

The problem will only occur when other modules alter field output based on user permissions.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Field as Block 7.x-1.x versions prior to 7.x-1.4.

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

Solution

Install the latest version:

Also see the Field as Block project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 7.x

Webform CiviCRM Integration - Moderately Critical - Cross Site Scripting (XSS) - SA-CONTRIB-2015-160

Wed, 10/21/2015 - 3:14pm
Description

Webform CiviCRM Integration allows you to add CiviCRM fields to a Drupal Webform.

The module doesn't sufficiently escape user input.

Some of the vulnerabilities are mitigated by the fact that an attacker must have a role with the permission to edit the webform node plus "access CiviCRM" to define the input prompts, or permission to create events in CiviCRM.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Webform CiviCRM 7.x versions prior to 7.x-4.13.

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

Solution

Install the latest version:

Also see the Webform CiviCRM Integration project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 7.x

LABjs - Less Critical - Open Redirect - SA-CONTRIB-2015-159

Wed, 10/21/2015 - 12:36pm
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-004).

Only sites with the Overlay module enabled are vulnerable.

An incomplete fix for this issue was released in SA-CONTRIB-2015-124.

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

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

Also see the LABjs project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 7.x

jQuery Update - Less Critical - Open Redirect - SA-CONTRIB-2015-158

Wed, 10/21/2015 - 12:34pm
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-004).

Only sites with the Overlay module enabled are vulnerable.

An incomplete fix for this issue was released in SA-CONTRIB-2015-123.

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

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:

Also see the jQuery Update project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 7.x

Twilio - Moderately Critical - Access bypass - SA-CONTRIB-2015-157

Wed, 10/14/2015 - 4:56pm
Description

This module provides hooks and rules integration to leverage the Twilio API to send/receive phone calls and text messages.

The module relies on existing permissions for providing administration which can lead to untrusted users having access to perform actions that may not be intended.

This vulnerability is mitigated by the fact that an attacker must have access to a session with the role that has the permission "access administration pages".

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Twilio 7.x-1.x versions prior to 7.x-1.11

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

Solution

Install the latest version:

Grant the permission "administer twilio" to any roles that should be able to administer the Twilio module.

Also see the Twilio project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 7.x

Colorbox - Access bypass - Less Critical - SA-CONTRIB-2015-156

Wed, 10/07/2015 - 12:16pm
Description

This module allows for integration of Colorbox, a jQuery lightbox plugin, into Drupal.

The module allows unprivileged users to add unexpected content to a Colorbox, including content from external sites. This allows an unprivileged user to deface a site.

This vulnerability is mitigated by the fact that an attacker must have permission to post comments with a text format that allows links.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Colorbox 7.x-2.x versions prior to 7.x-2.10.

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

Solution

Install the latest version:

Also see the Colorbox project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 7.x

Entity Registration - Moderately Critical - Information Disclosure - SA-CONTRIB-2015-155

Wed, 10/07/2015 - 11:47am
Description

This module enables you to manage registrations for events.

The module doesn't sufficiently protect information about who is registered to attend specific events when anonymous users are granted a permission that is commonly recommended when allowing anonymous registrations.

This vulnerability is mitigated by the fact that anonymous users must have the permission "Register other accounts."

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Entity Registration 7.x-1.x versions prior to 7.x-1.5.

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

Solution

Install the latest version:

Note on releases: the security bug was fixed in the 7.x-1.5 release, however that release included many other bug fixes and features. The 7.x-1.6 release is intended to fix a critical, non-security bug in the 7.x-1.5 release.

Update permissions configuration:

  • Remove the "Register other accounts" permission for anonymous users or other unprivileged roles
  • If needed, add the "Register Self" permission for anonymous users and other unprivileged roles

Also see the Entity Registration project page.

Reported by Fixed by Coordinated by 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

Stickynote - Cross Site Scripting (XSS) - Moderately Critical - SA-CONTRIB-2015-154

Wed, 10/07/2015 - 11:40am
Description

This module enables you to create notes on a page inside a block.

The module doesn't sufficiently sanitize the note text on the admin listing page.

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

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Stickynote 7.x-1.x versions prior to 7.x-1.3.

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

Solution

Install the latest version.

Also see the stickynote project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 7.x

Taxonomy Find - Unsupported - SA-CONTRIB-2015-153

Wed, 09/30/2015 - 4:16pm
Description

This module enables you to add a simple search interface to lookup taxonomy terms by name.

The module doesn't sufficiently sanitize output of taxonomy vocabulary names and term names.

This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Administer vocabularies and terms" or the ability to add or edit nodes or entities with taxonomy fields attached.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • MODULE 6.x-2.x versions up to 6.x-1.2.
  • MODULE 7.x-2.x versions up to 7.x-1.0.

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

Solution

If you use the Taxonomy Find module you should uninstall it.

Also see the Taxonomy Find project page.

Reported by
  • Matt Vance provisional member of the Drupal Security Team
Fixed by

Not applicable.

Coordinated by 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

Drupal version: Drupal 6.xDrupal 7.x

User Dashboard - SQL Injection - Critical - SA-CONTRIB-2015-152

Wed, 09/30/2015 - 4:13pm
Description

Module contains SQL Injection vulnerabilities.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • user_dashboard 7.x versions prior to 7.x-1.4

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

Solution

Install the latest version.

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

Also see the UserDashboard project page.

Reported by Fixed by Coordinated by 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

Drupal version: Drupal 7.x

Pages