[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20130731183159.4A7E79003F@www1.drupal.org>
Date: Wed, 31 Jul 2013 18:31:59 +0000 (UTC)
From: security-news@...pal.org
To: security-news@...pal.org
Subject: [Security-news] SA-CONTRIB-2013-061 - Flippy -
Access Bypass
View online: https://drupal.org/node/2054701
* Advisory ID: DRUPAL-SA-CONTRIB-2013-061
* Project: Flippy [1] (third-party module)
* Version: 7.x
* Date: 2013-July-31
* Security risk: Less critical [2]
* Exploitable from: Remote
* Vulnerability: Access bypass
-------- DESCRIPTION
---------------------------------------------------------
This module enables you to generate previous/next links for content types.
The module doesn't sufficiently enforce node access when generating
previous/next links. A user may be presented with a link (including alias if
one is set) but will not be able to view the node content.
This vulnerability is mitigated by the fact that an attacker must have a role
with the permission to access content.
-------- CVE IDENTIFIER(S) ISSUED
--------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in
accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED
---------------------------------------------------
* Flippy 7.x-1.x versions prior to 7.x-1.1
Drupal core is not affected. If you do not use the contributed Flippy [4]
module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Flippy module for Drupal 7.x, upgrade to Flippy 7.x-1.2 [5]
Also see the Flippy [6] project page.
-------- REPORTED BY
---------------------------------------------------------
* daviddr [7]
-------- FIXED BY
------------------------------------------------------------
* Joshua Li [8] the module maintainer
-------- COORDINATED BY
------------------------------------------------------
* Greg Knaddison [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/flippy
[2] http://drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] http://drupal.org/project/flippy
[5] http://drupal.org/node/2050827
[6] http://drupal.org/project/flippy
[7] http://drupal.org/user/2471996
[8] http://drupal.org/user/633216
[9] http://drupal.org/user/36762
[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@...pal.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/
Powered by blists - more mailing lists