[IT-SecNots] [Security-news] Panels - Critical - Multiple Vulnerabilities - SA-CONTRIB-2016-047

[security-news AT drupal.org]

View online: https://www.drupal.org/node/2785631

  * Advisory ID: DRUPAL-SA-CONTRIB-2016-047
  * Project: Panels [1]     (third-party module)
  * Version: 7.x
  * Date: 2016-August-17
  * Security risk: 15/25 ( Critical)
    AC:None/A:None/CI:All/II:None/E:Theoretical/TD:All [2]
  * Vulnerability: Access bypass, Information Disclosure

-------- 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 [3] 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 [4]
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 [5]

Also see the Panels [6] project page.

-------- REPORTED BY
---------------------------------------------------------

  * Pere Orga [7] of the Drupal Security Team
  * John Coltrane [8]
  * Branden Hamilton [9]
  * Joep Hendrix [10]

-------- FIXED BY
------------------------------------------------------------

  * Jakob Perry [11] the module maintainer
  * Damien Mckenna [12]
  * Mike Potter [13] provisional member of the Drupal Security Team
  * David Snopek [14] of the Drupal Security Team

-------- COORDINATED BY
------------------------------------------------------

  * Mike Potter [15] 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 [16].

Learn more about the Drupal Security team and their policies [17], writing
secure code for Drupal [18], and  securing your site [19].

Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [20]


[1] https://www.drupal.org/project/panels
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/project/panels
[5] https://www.drupal.org/node/2785597/edit
[6] https://www.drupal.org/project/panels
[7] https://www.drupal.org/u/pere-orga
[8] https://www.drupal.org/u/jcoltrane
[9] https://www.drupal.org/u/brandenlhamilton
[10] https://www.drupal.org/user/125580
[11] https://www.drupal.org/u/japerry
[12] https://www.drupal.org/u/damienmckenna
[13] https://www.drupal.org/u/mpotter
[14] https://www.drupal.org/u/dsnopek
[15] https://www.drupal.org/u/mpotter
[16] https://www.drupal.org/contact
[17] https://www.drupal.org/security-team
[18] https://www.drupal.org/writing-secure-code
[19] https://www.drupal.org/security/secure-configuration
[20] https://twitter.com/drupalsecurity

_______________________________________________
Security-news mailing list
Security-news AT drupal.org
Unsubscribe at https://lists.drupal.org/mailman/listinfo/security-news