• Advisory ID: DRUPAL-SA-CONTRIB-2015-155
• Project: Entity Registration (third-party module)
• Version: 7.x
• Date: 2015-October-07
• Security risk: 14/25 ( Moderately Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:Uncommon
• Vulnerability: Information Disclosure

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:

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

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

• Caroline Boyden

Fixed by

• Gabe Carleton-Barnes, the module maintainer

Coordinated by

• Michael Hess of the Drupal Security Team
• David Snopek 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-154
• Project: stickynote (third-party module)
• Version: 7.x
• Date: 2015-October-07
• Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All
• Vulnerability: Cross Site Scripting

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.

• If you use the Stickynote module for Drupal 6.x, upgrade to Stickynote 7.x-1.3

Also see the stickynote project page.

Reported by

• Jon Peck

Fixed by

• Luke Herrington the module maintainer

Coordinated by

• 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