* Advisory ID: DRUPAL-SA-CONTRIB-2010-104
* Project: Relevant Content (third-party module)
* Version: 5.x, 6.x
* Date: 2010-November-17
* Security risk: Less critical
* Exploitable from: Remote
* Vulnerability: Information Disclosure
-------- DESCRIPTION
---------------------------------------------------------
The Relevant Content module provides a block and CCK field which contain
links to other nodes on the site which are considered "relevant" to the
current nodes based on number of shared taxonomy terms. The Relevant Content
module does not implement node access logic properly, resulting in the
disclosure of node titles and relationships between nodes that the user
cannot normally access.
-------- VERSIONS AFFECTED
---------------------------------------------------
* Relevant Content module for Drupal 5.x versions prior to 5.x-1.4
* Relevant Content module for Drupal 6.x versions prior to 6.x-1.5
Drupal core is not affected. If you do not use the contributed Relevant
Content [1] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Relevant Content module for Drupal 5.x upgrade to Relevant
Content 5.x-1.4 [2]
* If you use the Relevant Content module for Drupal 6.x upgrade to Relevant
Content 6.x-1.5 [3]
See also the Relevant Content project page [4].
-------- REPORTED BY
---------------------------------------------------------
* Szymon Nitka [5]
-------- FIXED BY
------------------------------------------------------------
* Nicholas Thompson [6], module maintainer
-------- CONTACT AND MORE INFORMATION
----------------------------------------
The Drupal security team can be reached at security at drupal.org or via the
form at http://drupal.org/contact. Learn more about the team and their
policies [7], writing secure code for Drupal [8], and secure configuration
[9] of your site.
[1] http://drupal.org/project/relevant_content
[2] http://drupal.org/node/974672
[3] http://drupal.org/node/974668
[4] http://drupal.org/project/relevant_content
[5] http://drupal.org/user/171725
[6] http://drupal.org/user/59351
[7] http://drupal.org/security-team
[8] http://drupal.org/writing-secure-code
[9] http://drupal.org/security/secure-configuration
* Advisory ID: DRUPAL-SA-CONTRIB-2010-103
* Project: Node Relativity (third-party module)
* Version: 5.x, 6.x
* Date: 2010-November-10
* Security risk: Critical
* Exploitable from: Remote
* Vulnerability: Cross-Site Scripting, Cross Site Request Forgery, Access
bypass
-------- DESCRIPTION
---------------------------------------------------------
The Node Relativity module allows parent-child relationships between nodes to
be established, managed and searched. The Node Relativity module does not
sanitize some of the user supplied data before displaying it, leading to a
Cross Site Scripting (XSS [1]) vulnerability which can be used by a malicious
user to gain full administrative access. The Node Relativity module does not
protect the links to establish relations between nodes against Cross-site
Request Forgeries (CSRF [2]) vulnerability which can be used by a malicious
user to directly perform operations on the database. The Node Relativity
module does not implement node access logic properly, resulting in the
display of node titles and the establishing of relations between nodes the
user has no access to.
-------- VERSIONS AFFECTED
---------------------------------------------------
* Node Relativity module for Drupal 5.x versions prior to 5.x-2.6
* Node Relativity module for Drupal 6.x versions prior to 6.x-1.4
Drupal core is not affected. If you do not use the contributed Node
Relativity [3] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Node Relativity module for Drupal 5.x upgrade to Node
Relativity 5.x-2.6 [4]
* If you use the Node Relativity module for Drupal 6.x upgrade to Node
Relativity 6.x-1.4 [5]
See also the Node Relativity project page [6].
-------- REPORTED BY
---------------------------------------------------------
* recrit [7]
* catch [8] of the Drupal security team
-------- FIXED BY
------------------------------------------------------------
* Jonathan Araña Cruz [9], module maintainer
-------- CONTACT AND MORE INFORMATION
----------------------------------------
The Drupal security team can be reached at security at drupal.org or via the
form at http://drupal.org/contact. Learn more about the team and their
policies [10], writing secure code for Drupal [11], and Secure Configuration
[12] of your site.
[1] http://en.wikipedia.org/wiki/Cross-site_scripting
[2] http://en.wikipedia.org/wiki/Csrf
[3] http://drupal.org/project/relativity
[4] http://drupal.org/node/968516
[5] http://drupal.org/node/968514
[6] http://drupal.org/project/relativity
[7] http://drupal.org/user/452914
[8] http://drupal.org/user/35733
[9] http://drupal.org/user/49817
[10] http://drupal.org/security-team
[11] http://drupal.org/writing-secure-code
[12] http://drupal.org/security/secure-configuration
* Advisory ID: DRUPAL-SA-CONTRIB-2010-102
* Project: Category tokens (third-party module)
* Version: 6.x
* Date: 2010-November-10
* Security risk: Less critical
* Exploitable from: Remote
* Vulnerability: Cross-Site Scripting
-------- DESCRIPTION
---------------------------------------------------------
The Category tokens module exposes additional tokens for the first and last
terms related to a node for each vocabulary. The module does not sanitize the
vocabulary names when displayed in token help, leading to a Cross-Site
Scripting (XSS [1]) vulnerability that may lead to a malicious user gaining
full administrative access. This vulnerability is mitigated by the fact that
user must have the "administer taxonomy" permission in order to create and
edit vocabularies and enter the XSS.
-------- VERSIONS AFFECTED
---------------------------------------------------
* Category tokens module for Drupal 6.x versions prior to 6.x-1.1.
Drupal core is not affected. If you do not use the contributed Category
tokens [2] module, there is nothing you need to do.
-------- SOLUTION
------------------------------------------------------------
Install the latest version:
* If you use the Category tokens module for Drupal 6.x upgrade to Category
tokens 6.x-1.1 [3]
See also the Category tokens project page [4].
-------- REPORTED BY
---------------------------------------------------------
* Dave Reid [5], Drupal Security Team
-------- FIXED BY
------------------------------------------------------------
* Dave Reid [6], Drupal Security Team
* scheepers de bruin [7], module maintainer
-------- CONTACT
-------------------------------------------------------------
The Drupal security team [8] can be reached at security at drupal.org or via
the form at http://drupal.org/contact.
[1] http://en.wikipedia.org/wiki/Cross-site_scripting
[2] http://drupal.org/project/category_tokens
[3] http://drupal.org/node/939848
[4] http://drupal.org/project/category_tokens
[5] http://drupal.org/user/53892
[6] http://drupal.org/user/53892
[7] http://drupal.org/user/162354
[8] http://drupal.org/security-team