Some security issues have been reported in the Drupal Project and Project issue tracking modules, which can be exploited by malicious users to disclose sensitive information and bypass certain access restrictions.

The security issues are caused due to the improper enforcing of the "access projects", "access own projects", "access project issues" and "access own project issues" permissions. This can be exploited to disclose project names and other unspecified sensitive information about project or issues, via the Tracker Module and the "Recent posts" page, if a project or issue is promoted to the front page, and also to disclose a project's CVS activity if the node identifier is known.

The security issues are reported in the following products:
* Project module versions prior to 5.x-1.0, 4.7.x-2.3, and 4.7.x-1.3
* Project issue tracking module versions prior to 5.x-1.0, 4.7.x-2.4, and 4.7.x-1.4

Solution
Drupal 4.7.x:
Further details available to Secunia VIM customers

Provided and/or discovered by
Derek Wright, Drupal security team.

Changelog
Further details available to Secunia VIM customers

Original Advisory
http://drupal.org/node/168760

Deep Links
Links available to Secunia VIM customers