Hírolvasó

Drupal 8.3.7 is a maintenance releases which contain fixes for security vulnerabilities.

Download Drupal 8.3.7

Updating your existing Drupal 8 sites is strongly recommended (see instructions for Drupal 8). This release fixes security issues only; there are no new features nor non-security-related bug fixes in this release. See the 8.3.7 release notes for details on important changes and known issues affecting this release. Read on for details of the security vulnerabilities that were fixed in this release.

• Advisory ID: DRUPAL-SA-CORE-2017-004
• Project: Drupal core
• Version: 8.x
• Date: 2017-Aug-16
• Security risk: 15/25 ( Critical) AC:None/A:User/CI:Some/II:Some/E:Theoretical/TD:Default
• Multiple vulnerabilities

Description Views - Access Bypass - Moderately Critical - Drupal 8 - CVE-2017-6923

When creating a view, you can optionally use Ajax to update the displayed data via filter parameters. The views subsystem/module did not restrict access to the Ajax endpoint to only views configured to use Ajax. This is mitigated if you have access restrictions on the view.

It is best practice to always include some form of access restrictions on all views, even if you are using another module to display them.

REST API can bypass comment approval - Access Bypass - Moderately Critical - Drupal 8 - CVE-2017-6924

When using the REST API, users without the correct permission can post comments via REST that are approved even if the user does not have permission to post approved comments.

This issue only affects sites that have the RESTful Web Services (rest) module enabled, the comment entity REST resource enabled, and where an attacker can access a user account on the site with permissions to post comments, or where anonymous users can post comments.

Entity access bypass for entities that do not have UUIDs or have protected revisions - Access Bypass - Critical - Drupal 8 - CVE-2017-6925

There is a vulnerability in the entity access system that could allow unwanted access to view, create, update, or delete entities. This only affects entities that do not use or do not have UUIDs, and entities that have different access restrictions on different revisions of the same entity.

Versions affected

• Drupal core 8.x versions prior to 8.3.7

Solution

Install the latest version:

• If you use Drupal 8.x, upgrade to Drupal core 8.3.7

Drupal 7 core is not affected, however, Drupal 7 Views is: see Views - Moderately Critical - Access Bypass - DRUPAL-SA-CONTRIB-2017-068

Also see the Drupal core project page.

Reported by Views - Access Bypass

• Maxim Podorov

REST API can bypass comment approval - Access Bypass

• Arshad

Entity access bypass for entities that do not have UUIDs or protected revisions - Access Bypass

• Miles Worthington

Fixed by Views - Access Bypass

• Klaus Purer
• Daniel Wehner
• Michael Hess of the Drupal Security Team
• Len Swaneveld
• Wim Leers

REST API can bypass comment approval - Access Bypass

• Daniel Wehner
• Arshad
• Lee Rowlands of the Drupal Security Team
• Wim Leers
• Sascha Grossenbacher

Entity access bypass for entities that do not have UUIDs or protected revisions - Access Bypass

• Andrei Mateescu
• Peter Wolanin of the Drupal Security Team
• Matthew Donadio
• xjm of the Drupal Security Team
• Sascha Grossenbacher

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-2017-069
• Project: Views Refresh (third-party module)
• Version: 7.x, 8.x
• Date: 2017-August-16
• Security risk: 14/25 ( Moderately Critical) AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Default
• Vulnerability: Access bypass

Description

When creating a view, you can optionally use Ajax to update the displayed data via filter parameters. The views refresh module did not restrict access to the Ajax endpoint to only views configured to use Ajax. This is mitigated if you have access restrictions on the view.

It is best practice to always include some form of access restrictions on all views, even if you are using another module to display them.

CVE identifier(s) issued

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

Versions affected

• views fresh versions prior to 7.x-1.2.

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

Solution

Install the latest version:

• If you use the views refresh module for Drupal 7.x, upgrade to views refresh 7.x-1.2

Also see the Views refresh project page.

Reported by

• Maxim Podorov

Fixed by

• Maxim Podorov the module maintainer
• Klaus Purer
• Daniel Wehner
• Michael Hess of the Drupal Security Team
• Len Swaneveld
• Wim Leers
• Peter Wolanin of the Drupal Security Team

Coordinated by

• Michael Hess 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-2014-0XX
• Project: Views (third-party module)
• Version: 7.x, 8.x
• Date: 2017-August-16
• Security risk: 14/25 ( Moderately Critical) AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Default
• Vulnerability: Access bypass

Description

When creating a view, you can optionally use Ajax to update the displayed data via filter parameters. The views subsystem/module did not restrict access to the Ajax endpoint to only views configured to use Ajax. This is mitigated if you have access restrictions on the view.

It is best practice to always include some form of access restrictions on all views, even if you are using another module to display them.

CVE identifier(s) issued

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

Versions affected

• Views versions prior to 7.x-3.17.

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:

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

Also see the Views project page.

Reported by

• Maxim Podorov

Fixed by

• Klaus Purer
• Daniel Wehner
• Michael Hess of the Drupal Security Team
• Len Swaneveld
• Wim Leers
• Peter Wolanin of the Drupal Security Team

Coordinated by

• Michael Hess 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-2017-067
• Project: Entity reference (third-party module)
• Version: 7.x
• Date: 2017-August-16
• Security risk: 12/25 ( Moderately Critical) AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:Default
• Vulnerability: Access bypass

Description

The entity reference module provides a field type that can reference arbitrary entities.

In a vulnerable configuration, an attacker could determine the titles of nodes they do not have access to.

This is mitigated as only entity reference fields using the "simple" entity selector are vulnerable, and the attack is not possible if any access control (i.e. node access) is in place (the attacker's role is missing only the "access content" permission to be able to view the content.)

CVE identifier(s) issued

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

Versions affected

• entityreference 7.x-1.x versions prior to 7.x-1.5.

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

Solution

Install the latest version:

• If you use the entityreference module for Drupal 7.x, upgrade to entityreference 7.x-1.5

Also see the Entity reference project page.

Reported by

• Greg Knaddison of the Drupal Security Team
• Aaron Ott

Fixed by

• David Pascoe-Deslauriers the module maintainer

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-2014-0XX
• Project: Facebook Like Button (third-party module)
• Version: 7.x
• Date: 2017-August-09
• Security risk: 13/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All
• Vulnerability: Cross Site Scripting

Description

This module provides a Facebook Like button on node pages and blocks.
The module does not sufficiently sanitize output when configured to use custom css rules.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer fblikebutton".

CVE identifier(s) issued

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

Versions affected

• Facebook Like Button 7.x-2.x versions prior to 7.x-2.6.

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

Solution

Install the latest version:

• If you use the fblikebutton module for Drupal 7.x, upgrade to Facebook like button 7.x-2.6

Also see the Facebook Like Button project page.

Reported by

• Tatar Balazs Janos

Fixed by

• Tatar Balazs Janos
• Getulio Sánchez 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-2017-065
• Project: Session Cache API (third-party module)
• Version: 7.x, 8.x
• Date: 2017-August-09
• Security risk: 18/25 ( Critical) AC:Basic/A:User/CI:All/II:All/E:Proof/TD:Default
• Vulnerability: Multiple vulnerabilities

Description

This module does not safely deal with serialization.

CVE identifier(s) issued

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

Versions affected

• Session Cache API 7.x-1.4

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

Solution

Install the latest version:

• Upgrade to session_cache 7.x-1.5

Also see the Session Cache API project page.

Reported by

• Tomas Bortoli
• Pere Orga of the Drupal Security Team

Fixed by

• Rik de Boer the module maintainer

Coordinated by

• Michael Hess 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-2017-064
• Project: Better field descriptions (third-party module)
• Version: 7.x
• Date: 2017-Aug-09
• Security risk: 16/25 ( Critical) AC:None/A:User/CI:Some/II:Some/E:Theoretical/TD:All
• Vulnerability: Cross Site Scripting

Description

This module enables you to add themeable descriptions to fields in forms.

The module doesn't sufficiently sanitize descriptions.

This vulnerability is mitigated by the fact that an attacker must have a role with the permission "add better descriptions to fields".

CVE identifier(s) issued

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

Versions affected

• Better field descriptions 7.x-1.x versions prior to 7.x-1.1.

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

Solution

Install the latest version:

• If you use the Better Field Descriptions module for Drupal 7.x, upgrade to Better field descriptions 7.x-1.2

Also see the Better field descriptions project page.

Reported by

• mchampsee

Fixed by

• mchampsee
• odegard the module maintainer

Coordinated by

• Michael Hess 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-2017-063
• Project: Relation (third-party module)
• Version: 7.x
• Date: 2017-August-09
• Security risk: 14/25 ( Moderately Critical) AC:None/A:User/CI:Some/II:None/E:Exploit/TD:Uncommon
• Vulnerability: Access bypass

Description

This module enables you to store relationships between entities as fieldable entities.

The module doesn't sufficiently check permissions when displaying related entities labels with the Relation Dummy Field module widget.

This vulnerability is mitigated by the fact that the optional Relation Dummy Field module must be enabled and any entity must be configured to display related entities with the widget provided by the module.

CVE identifier(s) issued

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

Versions affected

• Relation 7.x-1.x versions prior to 7.x-1.1.

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

Solution

Install the latest version:

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

Also see the Relation project page.

Reported by

• Lars Schröter

Fixed by

• Mikko Rantanen the module maintainer
• Lars Schröter

Coordinated by

• Michael Hess 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-2017-062
• Project: services_views (third-party module)
• Date: 2-Aug-2017

Description

This module provides views support for the Services module.

The security team is marking this module unsupported. There is a known security issue with the module that has not been fixed by the maintainer. If you would like to maintain this module, please read: https://www.drupal.org/node/251466

Versions affected

• All versions

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

Solution

If you use the services_views module for Drupal you should uninstall it.

Also see the services_views project page.

Reported by

• Klaus Purer

Fixed by

Not applicable

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-2017-061
• Project: ajax_facets (third-party module)
• Date: 2-Aug-2017

Description

This module allows you to create facet filters which working by AJAX. Filters and search results will be updated by AJAX.

The security team is marking this module unsupported. There is a known security issue with the module that has not been fixed by the maintainer. If you would like to maintain this module, please read: https://www.drupal.org/node/251466

Versions affected

• All versions

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

Solution

If you use the ajax_facets module for Drupal you should uninstall it.

Also see the ajax_facets project page.

Reported by

• Frédéric G. Marand

Fixed by

Not applicable

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-2017-060
• Project: baidu_analytics (third-party module)
• Date: 2-Aug-2017

Description

This module adds the Baidu Analytics web statistics tracking system to your website.

The security team is marking this module unsupported. There is a known security issue with the module that has not been fixed by the maintainer. If you would like to maintain this module, please read: https://www.drupal.org/node/251466

Versions affected

• All versions

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

Solution

If you use the baidu_analytics module for Drupal you should uninstall it.

Also see the baidu_analytics project page.

Reported by

• Huang jie

Fixed by

Not applicable

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-2017-059
• Project: html_title (third-party module)
• Date: 2-Aug-2017

Description

The HTML Title module allows a limited set of HTML markup (em, sub, sup, b, i, strong, cite, code, bdi, wbr) to be used in node titles.

The security team is marking this module unsupported. There is a known security issue with the module that has not been fixed by the maintainer. If you would like to maintain this module, please read: https://www.drupal.org/node/251466

Versions affected

• All versions

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

Solution

If you use the html_title module for Drupal you should uninstall it.

Also see the html_title project page.

Reported by

• Nathaniel Catchpole of the Drupal Security Team

Fixed by

Not applicable

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-2017-058
• Project: Alinks (third-party module)
• Version: 8.x
• Date: 2017-August-02
• Security risk: 13/25 ( Moderately Critical) AC:Basic/A:None/CI:None/II:Some/E:Theoretical/TD:All
• Vulnerability: Access bypass

Description

This module enables you to automatically link keywords to specific URLs.

This module has an insufficient access check on the delete route.

Alinks uses the wrong permission for an access check.

CVE identifier(s) issued

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

Versions affected

• Alinks 8.x-1.x versions prior to 8.x-1.1.

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

Solution

Install the latest version:

• If you use the Alinks module for Drupal 8.x, upgrade to Alinks 8.x-1.1

Also see the Alinks project page.

Reported by

• Inasse

Fixed by

• Inasse
• Webflo
• Greg Boggs the module maintainer

Coordinated by

• Michael Hess 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-2017-057
• Project: DrupalChat (third-party module)
• Version: 7.x
• Date: 2017-July-05
• Security risk: 16/25 ( Critical) AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:All
• Vulnerability: Cross Site Scripting, Cross Site Request Forgery

Description

DrupalChat allows visitors of your Drupal site to chat with each other privately or together in a public chatroom.

The module did not confirm the validity of a chat request, resulting in a Cross Site Request Forgery (CSRF) vulnerability which enables an attacker to trick a user to send arbitrary chat messages to any user. The

The module did not filter administrator provided text, leading to 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

• DrupalChat 7.x-2.x versions prior to 7.x-2.2.

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

Solution

Install the latest version:

• If you use the DrupalChat module for Drupal 7.x, upgrade to DrupalChat 7.x-2.6

Also see the DrupalChat project page.

Also see the DrupalChat project page.

Reported by

• Elin Yordanov

Fixed by

• Shashwat Srivastava the module maintainer

Coordinated by

• Michael Hess 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

Drupal version: Drupal 7.x

• Advisory ID: DRUPAL-SA-CONTRIB-2017-056
• Project: OAuth (third-party module)
• Version: 8.x
• Date: 2017-July-05
• Security risk: 15/25 ( Critical) AC:Complex/A:None/CI:Some/II:Some/E:Theoretical/TD:All
• Vulnerability: Access bypass

Description

This module enables you to protect requests via the OAuth authentication protocol.

The module doesn't sufficiently notify the Cache API to avoid caching responses under the scenario in which an authenticated user requests a resource such as unpublished node.

This vulnerability is mitigated by the fact that an attacker must know the available resources in a Drupal site.

CVE identifier(s) issued

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

Versions affected

• OAuth 8.x-2.x versions prior to 8.x-2.1.

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

Solution

In addition to updating the code, you must Clear all caches.

• If you use the OAuth module for Drupal 8.x, upgrade to OAuth 8.x-2.1

Also see the OAuth project page.

Reported by

• Kevin Dutra.

Fixed by

• Kevin Dutra
• Juampy NR the module maintainer

Coordinated by

• Michael Hess 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

Drupal version: Drupal 7.x

• Advisory ID: DRUPAL-SA-CONTRIB-2017-055
• Project: SMTP Authentication Support (third-party module)
• Version: 7.x, 8.x
• Date: 2017-June-28
• Security risk: 10/25 ( Moderately Critical) AC:Complex/A:None/CI:Some/II:None/E:Theoretical/TD:Uncommon
• Vulnerability: Information Disclosure

Description

This SMTP module enables you to send mail using a third party (non-system) mail service instead of the local system mailer included with Drupal. When this module is in debugging mode, it will log privileged information.

CVE identifier(s) issued

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

Versions affected

• smtp 8.x-1.x versions prior to 8.x-1.0-beta3.
• smtp 7.x-1.x versions prior to 7.x-1.7.

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

Solution

Install the latest version:

• If you use the smtp module for Drupal 8.x, upgrade to smtp 8.x-1.0-beta3
• If you use the smtp module for Drupal 7.x, upgrade to smtp 7.x-1.7

Also see the SMTP Authentication Support project page.

Reported by

• Baysaa of the Drupal Security Team

Fixed by

• Fabiano Sant'Ana the module maintainer
• José San Martin the module maintainer
• David Snopek of the Drupal Security Team
• Cash Williams of the Drupal Security Team
• Michael Hess of the Drupal Security Team

Coordinated by

• Michael Hess 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-2017-054
• Project: Services (third-party module)
• Version: 7.x
• Date: 2017-June-28
• Security risk: 19/25 ( Critical) AC:None/A:User/CI:All/II:All/E:Theoretical/TD:Default
• Vulnerability: SQL Injection

Description

This module provides a standardized solution for building API's so that external clients can communicate with Drupal.

The module doesn't sufficiently sanitize column names provided by the client when they are querying for data and trying to sort it.

This vulnerability is mitigated by the fact that a site must have an "Index" resource enabled and the attacker must know the endpoint's URL.

CVE identifier(s) issued

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

Versions affected

• Services 7.x-3.x versions prior to 7.x-3.20

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

Solution

Install services version 7.x-3.20 of the module or disable any Index resources within your endpoint(s).

Also see the Services project page.

Reported by

• John Morahan

Fixed by

• Tyler Frankenstein, a module maintainer
• John Morahan

Coordinated by

• Michael Hess 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 8.3.4 and Drupal 7.56 are maintenance releases which contain fixes for security vulnerabilities.

Download Drupal 8.3.4 Download Drupal 7.56

Updating your existing Drupal 8 and 7 sites is strongly recommended (see instructions for Drupal 8 and for Drupal 7). This release fixes security issues only; there are no new features nor non-security-related bug fixes in this release. See the 8.3.4 release notes and the 7.56 release notes for details on important changes and known issues affecting this release. Read on for details of the security vulnerabilities that were fixed in this release.

• Advisory ID: DRUPAL-SA-CORE-2017-003
• Project: Drupal core
• Version: 7.x, 8.x
• Date: 2017-June-21
• Multiple vulnerabilities

Description PECL YAML parser unsafe object handling - Critical - Drupal 8 - CVE-2017-6920

PECL YAML parser does not handle PHP objects safely during certain operations within Drupal core. This could lead to remote code execution.

File REST resource does not properly validate - Less Critical - Drupal 8 - CVE-2017-6921

The file REST resource does not properly validate some fields when manipulating files. A site is only affected by this if the site has the RESTful Web Services (rest) module enabled, the file REST resource is enabled and allows PATCH requests, and an attacker can get or register a user account on the site with permissions to upload files and to modify the file resource.

Files uploaded by anonymous users into a private file system can be accessed by other anonymous users - Moderately Critical - Drupal 7 and Drupal 8 - CVE-2017-6922

Private files that have been uploaded by an anonymous user but not permanently attached to content on the site should only be visible to the anonymous user that uploaded them, rather than all anonymous users. Drupal core did not previously provide this protection, allowing an access bypass vulnerability to occur. This issue is mitigated by the fact that in order to be affected, the site must allow anonymous users to upload files into a private file system.

The security team has also received reports that this vulnerability is being exploited for spam purposes, similar to the scenario discussed in PSA-2016-003 for the public file system.

Versions affected

• Drupal core 7.x versions prior to 7.56
• Drupal core 8.x versions prior to 8.3.4

Solution

Install the latest version:

• If you use Drupal 7.x, upgrade to Drupal core 7.56
• If you use Drupal 8.x, upgrade to Drupal core 8.3.4

Also see the Drupal core project page.

Reported by PECL YAML parser unsafe object handling

• Heine Deelstra

File REST resource does not properly validate

• Samuel Mortenson

Files uploaded by anonymous users into a private file system can be accessed by other anonymous users

• Greg Knaddison of the Drupal Security team
• Mori Sugimoto of the Drupal Security team
• iancawthorne

Fixed by PECL YAML parser unsafe object handling

• XJM of the Drupal Security team
• Alex Pott of the Drupal Security team
• Peter Wolanin of the Drupal Security team

File REST resource does not properly validate

• Samuel Mortenson
• Wim Leers
• Alex Pott of the Drupal Security team
• XJM of the Drupal Security team
• Sascha Grossenbacher

Files uploaded by anonymous users into a private file system can be accessed by other anonymous users

• David Rothstein of the Drupal Security team
• Peter Wolanin of the Drupal Security team
• Michael Hess of the Drupal Security team
• XJM of the Drupal Security team
• Chris McCafferty of the Drupal Security team
• Lee Rowlands of the Drupal Security team
• Alex Pott of the Drupal Security team
• Nathaniel Catchpole of the Drupal Security team
• Stefan Ruijsenaars of the Drupal Security team
• Nate Haug
• Gareth Goodwin

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

• Advisory ID: DRUPAL-SA-CONTRIB-2017-053
• Project: Search 404 (third-party module)
• Version: 7.x
• Date: 2017-June-21
• Security risk: 13/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All
• Vulnerability: Cross Site Scripting

Description

The Search 404 module enables you to redirect 404 pages to a search page on the site for the keywords in the url that was not found.

The module did not filter administrator-provided text before displaying it to the user on the 404 page creating a Cross Site Scripting (XSS) vulnerability.

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

CVE identifier(s) issued

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

Versions affected

• Search 404 7.x-2.x versions prior to 7.x-1.5.

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

Solution

Install the latest version:

• If you use the Search 404 module for Drupal 7.x, upgrade to Search 404 7.x-1.5

Also see the Search 404 project page.

Reported by

• Sean Hamlin

Fixed by

• Anoop John the module maintainer
• Sean Hamlin the reporter

Coordinated by

• Greg Knaddison of the Drupal Security Team
• Michael Hess 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: Drupal 7.x

• Advisory ID: DRUPAL-SA-CONTRIB-2017-052
• Project: Lightweight Directory Access Protocol (LDAP) (third-party module)
• Version: 7.x
• Date: 2017-May-31
• Security risk: 15/25 ( Critical) AC:Basic/A:User/CI:Some/II:Some/E:Proof/TD:All
• Vulnerability: Multiple vulnerabilities

Description

The LDAP module does not sanitize user input correctly in several cases, allowing a user to modify parameters without restriction and inject data.

If the site administrator chooses to hide the email or password from the user form (instead of showing or disabling it under "Authorization"), these values can be overwritten.

CVE identifier(s) issued

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

Versions affected

• LDAP 7.x-2.x versions prior to 7.x-2.2.

Drupal core is not affected. If you do not use the contributed Lightweight Directory Access Protocol (LDAP) module, there is nothing you need to do.

Solution

Install the latest version:

• If you use the LDAP module for Drupal 7.x-2.x, upgrade to LDAP-7.x-2.2

Also see the Lightweight Directory Access Protocol (LDAP) project page.

Reported by

• ABDERRAZAK ZENNED

Fixed by

• Lee Rowlands
• queenvictoria
• Hendrik Grahl
• Michael Hess of the Drupal Security Team

Coordinated by

• Michael Hess 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