Category Archives: Drupal

Drupal Security Advisories

SA-CONTRIB-2015-040 – Webform prepopulate block – Cross Site Scripting (XSS)

Description

Webform prepopulate block module enables you to set a webform component to display in a separated block.

The module doesn’t sufficiently sanitize user supplied text when displaying the block, 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 or edit nodes.

CVE identifier(s) issued

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

Versions affected

  • Webform prepopulate block 7.x-3.0

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

Solution

Install the latest version:

Also see the Webform prepopulate 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: 

SA-CONTRIB-2015-039 – Views – Multiple vulnerabilities

Description

The Views module provides a flexible method for Drupal site designers to control how lists and tables of content, users, taxonomy terms and other data are presented.

Open redirect vulnerability

The module does not sanitize user provided URLs when processing the page to break the lock on Views being edited, thereby exposing an open redirect attack vector.

This vulnerability is mitigated by the fact that the Views UI submodule must be enabled.

Access bypass vulnerability

The module does not protect the default Views configurations that ship with the module sufficiently, thereby exposing possibly protected information to unprivileged users.

This vulnerability is mitigated by the fact that it only affects sites that have not granted the common “access content” or “access comments” permission to untrusted users. Furthermore, these default views configurations are disabled by default and must be enabled by an administrator.

CVE identifier(s) issued

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

Versions affected

  • Views 6.x-2.x versions prior to 6.x-2.18.
  • Views 6.x-3.x versions prior to 6.x-3.2.
  • Views 7.x-3.x versions prior to 7.x-3.10.

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

Solution

Install the latest version:

Also see the Views 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: 

SA-CONTRIB-2015-038 – Facebook Album Fetcher – Cross Site Scripting (XSS) – Unsupported

Description

Facebook Album Fetcher module allows you to fetch Facebook albums from a Facebook account.

The module incorrectly prints fields without proper sanitization thereby exposing a Cross Site Scripting vulnerability.

This vulnerability is mitigated by the fact that an attacker must have a role with 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

  • All versions of Facebook Album Fetcher.

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

Solution

If you use the Facebook Album Fetcher module you should uninstall it.

Also see the Facebook Album Fetcher project page.

Reported by

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: 

SA-CONTRIB-2015-037 – Path Breadcrumbs – Access Bypass

Description

This module enables you to configure breadcrumbs for any Drupal page.

The module doesn’t check node access on 403 Not Found pages. As a result, unpublished content data can be shown to unprivileged user.

This vulnerability is mitigated by the fact that it is possible to configure proper access control in Path Breadcrumbs items with “Selection Rules” from the UI.

CVE identifier(s) issued

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

Versions affected

  • Path Breadcrumbs 7.x-3.x versions prior to 7.x-3.2

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

Solution

Install the latest version:

Also see the Path Breadcrumbs 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: 

SA-CONTRIB-2015-036 – Public Download Count – Cross Site Scripting (XSS) – Unsupported

Description

Public Download Count module keeps track of file download counts.

The module doesn’t sufficiently sanitize user supplied text in the Download counts report page 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 or edit nodes.

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 Public Download Count module.

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

Solution

If you use the Public Download Count module you should uninstall it.

Also see the Public Download Count project page.

Reported by

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: 

SA-CONTRIB-2015-035 – Ajax Timeline – Cross Site Scripting (XSS)

Description

Ajax Timeline module enables you to display a vertical timeline of nodes based off a date field or created date of the configured nodes.

The module doesn’t sufficiently escape node titles when displaying the timeline, allowing a malicious user to inject code.

This vulnerability is mitigated by the fact that an attacker must have a role with permission to create or edit nodes of the type configured for the timeline.

CVE identifier(s) issued

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

Versions affected

  • Ajax Timeline 7.x-1.x versions prior to 7.x-1.1.

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

Solution

Install the latest version:

Also see the Ajax Timeline 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: 

SA-CONTRIB-2015-034 – Commerce WeDeal – Open Redirect

Description

Commerce WeDeal module enables you to do Commerce payments through the payment provider WeDeal.

The module doesn’t sufficiently check a query parameter used for page redirection, thereby leading to an Open Redirect vulnerability.

CVE identifier(s) issued

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

Versions affected

  • Commerce WeDeal 7.x-1.x versions prior to 7.x-1.3.

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

Solution

Install the latest version:

Also see the Commerce WeDeal 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: 

SA-CONTRIB-2015-033 – Certify – Access bypass and information disclosure

Description

Certify enables you to automatically issue PDF certificates to users upon completion of a set of conditions.

The module does not sufficiently check node access when showing (and creating) the PDF certificates. This can lead to users seeing certificates they should not have access to.

This vulnerability is mitigated by the fact that an attacker must have completed the conditions of the certificate.

CVE identifier(s) issued

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

Versions affected

  • Certify 6.x-2.x versions prior to 6.x-2.3.

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

Solution

Install the latest version:

Also see the Certify 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: 

SA-CONTRIB-2015-032 – Node Invite – Multiple vulnerabilities

Description

Node Invite module enables you to invite people to RSVP on node types that have been configured to represent events.

The module doesn’t sufficiently sanitize the titles of nodes in some listings, allowing a malicious user to inject code, thereby leading to a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that the attacker must have permission to create or edit nodes configured to be used for RSVP.

Additionally, some URLs are not protected against CSRF. A malicious user can cause a user with the “node_invite_can_manage_invite” permission to re-enable node invitations by getting his browser to make a request to a specially-crafted URL.

Lastly, the module is not checking that some destination parameters are internal URLs, thereby leading to an Open Redirect vulnerability.

CVE identifier(s) issued

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

Versions affected

  • Node Invite 6.x-2.x versions prior to 6.x-2.5.

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

Solution

Install the latest version:

Also see the Node Invite project page.

Reported by

  • Pere Orga provisional member of the Drupal Security Team

Fixed by

Coordinated by

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

Drupal version: 

SA-CONTRIB-2015-031 – GD Infinite Scroll – Multiple vulnerabilites

Description

GD Infinite Scroll module enables you to use the “infinite scroll jQuery plugin : auto-pager” on custom pages.

Some links were not protected against CSRF. A malicious user could cause another user with the “edit gd infinite scroll settings” permission to delete settings by getting his browser to make a request to a specially-crafted URL.

Also, the module fails to sanitize user input in its admin page, leading to a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission “edit gd infinite scroll settings”.

CVE identifier(s) issued

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

Versions affected

All GD Infinite Scroll versions prior to 7.x-1.4

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

Solution

Install the latest version, upgrade to GD Infinite Scroll 7.x-1.4

Also see the GD Infinite Scroll project page.

Reported by

  • Pere Orga provisional member of the Drupal Security Team

Fixed by

Coordinated by

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

Drupal version: