Skip directly to content

Feed aggregator

How to manage your photos on Flickr.com

Drupal Core Security Announcements - Sat, 06/28/2014 - 14:50

To get the most out of the Drupal Flickr module, on your flickr.com account you should:

  1. complete the information associated with your account and your own photos
  2. put your own photos that you want to embed as a slideshow in photosets (aka 'albums' on Flickr)
  3. put the photos from others you want to embed as an album in galleries (not for your own photos, not available as slideshow)
  4. create an invite-only public group if you intend to display photos of a fixed group of flickr members without the need of giving them permissions on your website, e.g. for a sports club website
  5. know how to find appropriate keywords to fill a site quickly with public images related to the content based on taxonomy terms attached to a post.
1. Complete the information associated with your account and your own photos. 2. Put own photos you want to embed as a slideshow in photosets. 3. Put the photos from others you want to embed as an album in galleries. 4. Create an invite-only public group. 5. Find appropriate keywords to fill a site quickly with public images.
Categories: Security posts

No minimal password length?

Drupal Contrib Security Announcements - Sat, 06/28/2014 - 14:43
Project: Password Reset Landing Page (PRLP)Version: 7.x-1.0Status: ActivePriority: NormalCategory: Feature requestComponent: CodeAssigned: Unassigned

I installed this module, but I noticed I was able to create passwords with only 1 character?

On my normal password reset I had : https://www.drupal.org/project/password_policy installed, but it seems this module and password_policy don't go together?

Categories: Security posts

No minimal password length?

Drupal Core Security Announcements - Sat, 06/28/2014 - 14:43
Project: Password Reset Landing Page (PRLP)Version: 7.x-1.0Status: ActivePriority: NormalCategory: Feature requestComponent: CodeAssigned: Unassigned

I installed this module, but I noticed I was able to create passwords with only 1 character?

On my normal password reset I had : https://www.drupal.org/project/password_policy installed, but it seems this module and password_policy don't go together?

Categories: Security posts

Tests with dependencies do not show up if the dependencies are present

Drupal Contrib Security Announcements - Sat, 06/28/2014 - 14:34
Project: Drupal coreVersion: 8.x-devStatus: ActivePriority: NormalCategory: Bug reportComponent: simpletest.moduleAssigned: Unassigned

The relevant code checks $dependency_data, but that is not defined anywhere.

We have a test for this, but we only test that we can hide a test, not that a test with valid dependencies shows up

Categories: Security posts

Tests with dependencies do not show up if the dependencies are present

Drupal Core Security Announcements - Sat, 06/28/2014 - 14:34
Project: Drupal coreVersion: 8.x-devStatus: ActivePriority: NormalCategory: Bug reportComponent: simpletest.moduleAssigned: Unassigned

The relevant code checks $dependency_data, but that is not defined anywhere.

We have a test for this, but we only test that we can hide a test, not that a test with valid dependencies shows up

Categories: Security posts

Nube Question: Satellite Footprint Image Browser

Drupal Core Security Announcements - Sat, 06/28/2014 - 14:28

Design Goal: build a two-panel screen layout, with a list of satellite beams on the left, and a selected satellite footprint image on the right.

Can anyone please recommend a module and/or configuration to do this?

Use Case: A user scrolls through the list of satellite beams in the left window; when the user clicks on any item in the list, an associated image will appear in the right window.

I have already generated the content and view to display the list of satellite beams.

There are probably many ways to do this. I am new to Drupal, so not sure what is the simplest best-practice way of going about this.

Note, I am an moderately-experienced programmer, but have never coded anything in Drupal... and willing to learn if recommended.

Thanks,
--Chris Chaudoir

p.s., if interested, what I have done so far is at verticalvector dot com

Drupal version: Drupal 7.x
Categories: Security posts

Inconsistencies with entity hooks

Drupal Core Security Announcements - Sat, 06/28/2014 - 14:25
Project: Drupal coreVersion: 8.x-devStatus: ActivePriority: NormalCategory: Bug reportComponent: entity systemAssigned: Unassigned

While I was working on #2216535: Replace Node overview topic and Node API topic with Entity Hooks topic, I noticed several problems with the entity hooks:

a) When the entity CRUD hooks are invoked, the generic ones like hook_entity_create() and hook_entity_load() all have the entity type ID passed in. This was not documented in most of the hook documentation in entity.api.php (I'm fixing that).

However, this is not being tested in entity_crud_hook_test.module where it tests all the entity CRUD hooks. I think that should be fixed?

b) Inconsistency: In all cases but one, the EntityStorageBase::invokeHook() method is used to invoke the entity hooks from the storage controller. This makes the type-specific hook run before the generic hook (hook_ENTITY_TYPE_create() before hook_entity_create() for instance).

However, during load it goes in the opposite order. It seems like this should be reversed? See EntityStorageBase::postLoad().

Categories: Security posts

.ht.sqlite database folder -- false permissions warning

Drupal Core Security Announcements - Sat, 06/28/2014 - 14:20
Project: Security ReviewVersion: 7.x-1.1Status: ActivePriority: NormalCategory: Bug reportComponent: CodeAssigned: Unassigned

I am receiving a warning about "Web server file system permissions" :

The following files and directories appear to be writeable by your web server. In most cases you can fix this by simply altering the file permissions or ownership. If you have command-line access to your host try running "chmod 644 [file path]" where [file path] is one of the following paths (relative to your webroot). For more information consult the Drupal.org handbooks on file permissions.
./sites/default/db

"db" directory contains .ht.sqlite database file. This directory, as well as database file, should be writeable by web server (permissions 755) ! otherwise (if permissions are 644) the website will be unable to work

So, there should be no warnings about folders that contain ".ht.sqlite" file

Categories: Security posts

SA-CONTRIB-2014-065 - Custom Meta - Cross Site Scripting (XSS)

Drupal Contrib Security Announcements - Wed, 06/18/2014 - 14:37
  • Advisory ID: DRUPAL-SA-CONTRIB-2014-065
  • Project: Custom Meta (third-party module)
  • Version: 6.x, 7.x
  • Date: 2014-June-18
  • Security risk: Moderately critical
  • Exploitable from: Remote
  • Vulnerability: Cross Site Scripting
Description

The module allows you to define and manage custom meta tags.

The module does not sufficiently sanitize user input before displaying the attribute and content values for meta tags on the administration page.

This vulnerability is mitigated by the fact that an attacker must have access to an account with the permission "administer custom meta settings".

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

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

Solution

Install the latest version:

Also see the Custom Meta 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 http://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
Categories: Security posts

SA-CONTRIB-2014-065 - Custom Meta - Cross Site Scripting (XSS)

Drupal Contrib Security Announcements - Wed, 06/18/2014 - 14:37
  • Advisory ID: DRUPAL-SA-CONTRIB-2014-065
  • Project: Custom Meta (third-party module)
  • Version: 6.x, 7.x
  • Date: 2014-June-18
  • Security risk: Moderately critical
  • Exploitable from: Remote
  • Vulnerability: Cross Site Scripting
Description

The module allows you to define and manage custom meta tags.

The module does not sufficiently sanitize user input before displaying the attribute and content values for meta tags on the administration page.

This vulnerability is mitigated by the fact that an attacker must have access to an account with the permission "administer custom meta settings".

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

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

Solution

Install the latest version:

Also see the Custom Meta 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 http://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
Categories: Security posts

SA-CONTRIB-2014-064 -Course - Access bypass

Drupal Contrib Security Announcements - Wed, 06/18/2014 - 14:04
  • Advisory ID: DRUPAL-SA-CONTRIB-2014-064
  • Project: Course (third-party module)
  • Version: 6.x, 7.x
  • Date: 2014-June-18
  • Security risk: Moderately critical
  • Exploitable from: Remote
  • Vulnerability: Access bypass
Description

This module enables you to create e-learning courses with any number of requirements for completion. A "Course object" is a relationship entity between a Course and a learning object, such as a Node.

The module doesn't sufficiently check access on Course object edit forms. The configuration options of any Course object are visible to any user including the anonymous user.

This vulnerability is mitigated by the fact that while the form and its configuration options can be viewed, no changes can be saved.

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

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

Solution

Install the latest version:

  • If you use the Course module for Drupal 6.x, upgrade to Course 6.x-1.1
  • If you use the Course module for Drupal 7.x, upgrade to Course 7.x-1.2

Also see the Course 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 http://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

Categories: Security posts

SA-CONTRIB-2014-064 -Course - Access bypass

Drupal Contrib Security Announcements - Wed, 06/18/2014 - 14:04
  • Advisory ID: DRUPAL-SA-CONTRIB-2014-064
  • Project: Course (third-party module)
  • Version: 6.x, 7.x
  • Date: 2014-June-18
  • Security risk: Moderately critical
  • Exploitable from: Remote
  • Vulnerability: Access bypass
Description

This module enables you to create e-learning courses with any number of requirements for completion. A "Course object" is a relationship entity between a Course and a learning object, such as a Node.

The module doesn't sufficiently check access on Course object edit forms. The configuration options of any Course object are visible to any user including the anonymous user.

This vulnerability is mitigated by the fact that while the form and its configuration options can be viewed, no changes can be saved.

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

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

Solution

Install the latest version:

  • If you use the Course module for Drupal 6.x, upgrade to Course 6.x-1.1
  • If you use the Course module for Drupal 7.x, upgrade to Course 7.x-1.2

Also see the Course 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 http://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

Categories: Security posts

SA-CONTRIB-2014-063 - Easy Breadcrumb - Cross Site Scripting (XSS)

Drupal Contrib Security Announcements - Wed, 06/18/2014 - 13:07
  • Advisory ID: DRUPAL-SA-CONTRIB-2014-063
  • Project: Easy Breadcrumb (third-party module)
  • Version: 7.x
  • Date: 2014-June-18
  • Security risk: Moderately critical
  • Exploitable from: Remote
  • Vulnerability: Cross Site Scripting
Description

The Easy Breadcrumb module generates breadcrumbs from path aliases.

This module does not properly sanitize user-supplied values creating a Cross Site Scripting (XSS) vulnerability.

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

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

Solution

If you use the Easy Breadcrumb module for Drupal 7 upgrade to 7.x-2.10.

Also see the Easy Breadcrumb 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 http://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

Categories: Security posts

SA-CONTRIB-2014-063 - Easy Breadcrumb - Cross Site Scripting (XSS)

Drupal Contrib Security Announcements - Wed, 06/18/2014 - 13:07
  • Advisory ID: DRUPAL-SA-CONTRIB-2014-063
  • Project: Easy Breadcrumb (third-party module)
  • Version: 7.x
  • Date: 2014-June-18
  • Security risk: Moderately critical
  • Exploitable from: Remote
  • Vulnerability: Cross Site Scripting
Description

The Easy Breadcrumb module generates breadcrumbs from path aliases.

This module does not properly sanitize user-supplied values creating a Cross Site Scripting (XSS) vulnerability.

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

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

Solution

If you use the Easy Breadcrumb module for Drupal 7 upgrade to 7.x-2.10.

Also see the Easy Breadcrumb 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 http://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

Categories: Security posts

SA-CONTRIB-2014-062 -Passsword Policy - Multiple vulnerabilities

Drupal Contrib Security Announcements - Wed, 06/18/2014 - 12:58
  • Advisory ID: DRUPAL-SA-CONTRIB-2014-062
  • Project: Password policy (third-party module)
  • Version: 6.x, 7.x
  • Date: 2014-June-18
  • Security risk: Moderately critical
  • Exploitable from: Remote
  • Vulnerability: Multiple vulnerabilities
Description

The Password Policy module enables you to define and enforce password policies with various constraints on allowable user passwords.

Access bypass and information disclosure (7.x only)

The module has a history constraint, which when enabled, disallows a user's password from being changed to match a specified number of their previous passwords. For this to work, the module stores a history of all previous user password hashes from the time the module is enabled (regardless of whether the history constraint is enabled).

Upon upgrading from 6.x to 7.x, the module does not convert these hashes from the Drupal 6 format to the Drupal 7 format. This has two consequences:
1. Users can change their passwords to old passwords used in Drupal 6 in violation of the history constraint.
2. Previous user passwords from Drupal 6 are kept indefinitely in Drupal 7 as weak MD5 hashes. If a site is compromised, past user passwords are at high risk of exposure.

This vulnerability is mitigated by the fact that only sites using 7.x that have previously used 6.x are affected.

Access bypass (6.x)

The module has a feature that lets an administrator force a password change for one or more users at their next login. These users are unable to access the website beyond their account page until changing their password.

A bug exists in 6.x where a password change will not be enforced when a user_save() is performed between the time when the administrator forces the password change and the time the affected user logs in. This can lead to users retaining insecure passwords.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Password Policy 6.x-1.x versions prior to 6.x-1.7.
  • Password Policy 7.x-1.x versions prior to 7.x-1.7.
  • Password Policy 7.x-2.x versions prior to 7.x-2.0-alpha2.

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

Solution

Warning: If you are using 7.x, and have used 6.x in the past on the same site, you are advised to back up your database prior to upgrading to the latest version to reduce the risk of an unforeseen upgrade problem causing permanent loss of password history.

Install the latest version:

  • If you use the Password Policy module for Drupal 6.x, upgrade to 6.x-1.7
  • If you use the Password Policy 1.x module for Drupal 7.x, upgrade to 7.x-1.7
  • If you use the Password Policy 2.x module for Drupal 7.x, upgrade to 7.x-2.0-alpha2

Also see the Password policy 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 http://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
Categories: Security posts

SA-CONTRIB-2014-062 -Passsword Policy - Multiple vulnerabilities

Drupal Contrib Security Announcements - Wed, 06/18/2014 - 12:58
  • Advisory ID: DRUPAL-SA-CONTRIB-2014-062
  • Project: Password policy (third-party module)
  • Version: 6.x, 7.x
  • Date: 2014-June-18
  • Security risk: Moderately critical
  • Exploitable from: Remote
  • Vulnerability: Multiple vulnerabilities
Description

The Password Policy module enables you to define and enforce password policies with various constraints on allowable user passwords.

Access bypass and information disclosure (7.x only)

The module has a history constraint, which when enabled, disallows a user's password from being changed to match a specified number of their previous passwords. For this to work, the module stores a history of all previous user password hashes from the time the module is enabled (regardless of whether the history constraint is enabled).

Upon upgrading from 6.x to 7.x, the module does not convert these hashes from the Drupal 6 format to the Drupal 7 format. This has two consequences:
1. Users can change their passwords to old passwords used in Drupal 6 in violation of the history constraint.
2. Previous user passwords from Drupal 6 are kept indefinitely in Drupal 7 as weak MD5 hashes. If a site is compromised, past user passwords are at high risk of exposure.

This vulnerability is mitigated by the fact that only sites using 7.x that have previously used 6.x are affected.

Access bypass (6.x)

The module has a feature that lets an administrator force a password change for one or more users at their next login. These users are unable to access the website beyond their account page until changing their password.

A bug exists in 6.x where a password change will not be enforced when a user_save() is performed between the time when the administrator forces the password change and the time the affected user logs in. This can lead to users retaining insecure passwords.

CVE identifier(s) issued
  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.
Versions affected
  • Password Policy 6.x-1.x versions prior to 6.x-1.7.
  • Password Policy 7.x-1.x versions prior to 7.x-1.7.
  • Password Policy 7.x-2.x versions prior to 7.x-2.0-alpha2.

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

Solution

Warning: If you are using 7.x, and have used 6.x in the past on the same site, you are advised to back up your database prior to upgrading to the latest version to reduce the risk of an unforeseen upgrade problem causing permanent loss of password history.

Install the latest version:

  • If you use the Password Policy module for Drupal 6.x, upgrade to 6.x-1.7
  • If you use the Password Policy 1.x module for Drupal 7.x, upgrade to 7.x-1.7
  • If you use the Password Policy 2.x module for Drupal 7.x, upgrade to 7.x-2.0-alpha2

Also see the Password policy 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 http://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
Categories: Security posts

SA-CONTRIB-2014-061 - VideoWhisper Webcam Plugins - Cross Site Scripting (XSS) - Unsupported

Drupal Contrib Security Announcements - Wed, 06/18/2014 - 12:54
  • Advisory ID: DRUPAL-SA-CONTRIB-2014-061
  • Project: VideoWhisper Webcam Plugins (third-party module)
  • Version: 7.x
  • Date: 2014-June-18
  • Security risk: Critical
  • Exploitable from: Remote
  • Vulnerability: Cross Site Scripting
Description

Includes multiple modules for video communications including room listing, pay per view access control.

The module doesn't sufficiently filter user supplied text from the url (reflected cross site scripting). No special permissions are required to exploit this issue.

There are no mitigating factors for this vulnerability.

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 VideoWhisper Webcam Plugins.

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

Solution

If you use the VideoWhisper Webcam Plugins module you should uninstall it.

Also see the VideoWhisper Webcam Plugins project page.

Reported by

This issue was publicly disclosed as CVE-2014-2715 outside of the process to report security issues in Drupal. Issues reported via the Drupal Security Team process normally include the original reporter.

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 http://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
Categories: Security posts

SA-CONTRIB-2014-061 - VideoWhisper Webcam Plugins - Cross Site Scripting (XSS) - Unsupported

Drupal Contrib Security Announcements - Wed, 06/18/2014 - 12:54
  • Advisory ID: DRUPAL-SA-CONTRIB-2014-061
  • Project: VideoWhisper Webcam Plugins (third-party module)
  • Version: 7.x
  • Date: 2014-June-18
  • Security risk: Critical
  • Exploitable from: Remote
  • Vulnerability: Cross Site Scripting
Description

Includes multiple modules for video communications including room listing, pay per view access control.

The module doesn't sufficiently filter user supplied text from the url (reflected cross site scripting). No special permissions are required to exploit this issue.

There are no mitigating factors for this vulnerability.

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 VideoWhisper Webcam Plugins.

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

Solution

If you use the VideoWhisper Webcam Plugins module you should uninstall it.

Also see the VideoWhisper Webcam Plugins project page.

Reported by

This issue was publicly disclosed as CVE-2014-2715 outside of the process to report security issues in Drupal. Issues reported via the Drupal Security Team process normally include the original reporter.

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 http://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
Categories: Security posts

SA-CONTRIB-2014-060- Petitions - Cross Site Request Forgery (CSRF)

Drupal Contrib Security Announcements - Wed, 06/11/2014 - 18:41
  • Advisory ID: DRUPAL-SA-CONTRIB-2014-060
  • Project: - Petitions - (third-party distribution)
  • Version: 7.x
  • Date: 2014-June-11
  • Security risk: Less critical
  • Exploitable from: Remote
  • Vulnerability: Cross Site Request Forgery
Description

This distribution enables you to build an application that lets users create and sign petitions.
The contained wh_petitions module doesn't sufficiently verify the intent of the user when signing a petition. A malicious user could trick another user into signing a petition they did not intend to sign by getting them to visit a specially-crafted URL while logged in.

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

Drupal core is not affected. If you do not use the contributed - Petitions - distribution, there is nothing you need to do.

Solution

Install the latest version:

Note that petitions 7.x-1.2 is the last release for the first version of petitions. petitions 7.x-1.x is no longer maintained, and you are strongly encouraged to upgrade to the latest version petitions 7.x-2.0-beta19. Also see the - Petitions - 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 http://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
Categories: Security posts

SA-CONTRIB-2014-060- Petitions - Cross Site Request Forgery (CSRF)

Drupal Contrib Security Announcements - Wed, 06/11/2014 - 18:41
  • Advisory ID: DRUPAL-SA-CONTRIB-2014-060
  • Project: - Petitions - (third-party distribution)
  • Version: 7.x
  • Date: 2014-June-11
  • Security risk: Less critical
  • Exploitable from: Remote
  • Vulnerability: Cross Site Request Forgery
Description

This distribution enables you to build an application that lets users create and sign petitions.
The contained wh_petitions module doesn't sufficiently verify the intent of the user when signing a petition. A malicious user could trick another user into signing a petition they did not intend to sign by getting them to visit a specially-crafted URL while logged in.

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

Drupal core is not affected. If you do not use the contributed - Petitions - distribution, there is nothing you need to do.

Solution

Install the latest version:

Note that petitions 7.x-1.2 is the last release for the first version of petitions. petitions 7.x-1.x is no longer maintained, and you are strongly encouraged to upgrade to the latest version petitions 7.x-2.0-beta19. Also see the - Petitions - 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 http://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
Categories: Security posts

Pages