Panels – Critical – Multiple Vulnerabilities – SA-CONTRIB-2016-047

Description

Panels does not check access on some routes (Critical)

Panels allows users with certain permissions to modify the layout and panel panes on pages or entities utilizing panels.

Much of the functionality to modify these panels rely on backend routes that call administrative forms. These forms did not provide any access checks, or site specific encoded urls. This can allow an attacker to guess the backend url as an anonymous user and see data loaded for the form.

There is no mitigation for this exploit. Any site with panels enabled is vulnerable.

Panels In-place Editor does not properly check for access (Moderately Critical)

The Panels In-Place Editor (IPE) allows users with certain permissions to modify the layout and panel content of pages.

The default behavior for Panels IPE is to allow any user with the permissions “Use the Panels In-Place Editor” and “Change layouts with the Panels In-Place Editor ” access to the IPE regardless of whether or not a user has proper access to the page. While users cannot edit the page content itself, they can change the layout and the different panel panes shown.

This vulnerability is mitigated by the fact that an attacker must have a role with the permission “Use the Panels In-Place Editor” and the IPE must be enabled for the specific content type.

CVE identifier(s) issued

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

Versions affected

  • Panels 7.x-3.x versions prior to 7.x-3.6.

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

Solution

Install the latest version:

  • If you use the panels module for Drupal 7x, upgrade to Panels 7.x-3.6

Also see the Panels project page.

Reported by

Fixed by

Coordinated by

  • Mike Potter 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: 

Leave a Reply