Drupal Protected Node 6.x Access Bypass

2012-06-14 / 2012-08-15
Risk: High
Local: No
Remote: Yes
CWE: CWE-264


Ogólna skala CVSS: 7.5/10
Znaczenie: 6.4/10
Łatwość wykorzystania: 10/10
Wymagany dostęp: Zdalny
Złożoność ataku: Niska
Autoryzacja: Nie wymagana
Wpływ na poufność: Częściowy
Wpływ na integralność: Częściowy
Wpływ na dostępność: Częściowy

View online: http://drupal.org/node/1632918 * Advisory ID: DRUPAL-SA-CONTRIB-2012-101 * Project: Protected node [1] (third-party module) * Version: 6.x * Date: 2012-June-13 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- The Protected Node module enables users to use a password to restrict access to an individual node or all nodes of a node type. The module doesn't sufficiently protect node access when nodes are accessed outside of the standard node view (i.e. node/1 is protected but other lists are not). CVE: Requested -------- VERSIONS AFFECTED --------------------------------------------------- * Protected node 6.x-1.x versions prior to 6.x-1.6. Drupal core is not affected. If you do not use the contributed Protected node [3] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Protected node module for Drupal 6.x, upgrade to Protected node 6.x-1.6 [4] Also see the Protected node [5] project page. -------- REPORTED BY --------------------------------------------------------- * Martin Barbella [6] -------- FIXED BY ------------------------------------------------------------ * Alexis Wilke [7] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Greg Knaddison [8] of the Drupal Security Team * Michael Hess [9] 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 http://drupal.org/contact [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. [1] http://drupal.org/project/protected_node [2] http://drupal.org/security-team/risk-levels [3] http://drupal.org/project/protected_node [4] http://drupal.org/node/1258034 [5] http://drupal.org/project/protected_node [6] http://drupal.org/user/633600 [7] http://drupal.org/user/356197 [8] http://drupal.org/user/36762 [9] http://drupal.org/user/102818 [10] http://drupal.org/contact [11] http://drupal.org/security-team [12] http://drupal.org/writing-secure-code [13] http://drupal.org/security/secure-configuration _______________________________________________ Security-news mailing list Security-news@drupal.org Unsubscribe at http://lists.drupal.org/mailman/listinfo/security-news _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/

Referencje:

http://drupal.org/node/1632918


Vote for this issue:
50%
50%


 

Thanks for you vote!


 

Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.


(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}

Copyright 2024, cxsecurity.com

 

Back to Top