First published: Fri Mar 09 2007(Updated: )
The Project issue tracking module before 4.7.x-1.3, 4.7.x-2.* before 4.7.x-2.3, and 5 before 5.x-0.2-beta for Drupal allows remote authenticated users, with "access project issues" permission, to read the contents of a private node via a URL with a modified node identifier.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Drupal Drupal Project Issue Tracking | =4.7_2.1 | |
Drupal Drupal Project Issue Tracking | =5.0_0.1 | |
Drupal Drupal Project Issue Tracking | =5.7_1.1 | |
Drupal Drupal Project Issue Tracking | =4.7_1.2 | |
Drupal Drupal Project Issue Tracking | =4.7_2.0 | |
Drupal Drupal Project Issue Tracking | =4.7_1.0 | |
Drupal Drupal Project Issue Tracking | =4.7_2.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2007-1368 is considered to have a medium severity level due to the potential for unauthorized access to private information.
To fix CVE-2007-1368, update the Drupal project issue tracking module to version 4.7.x-1.3 or later, or 5.x-0.2-beta or later.
Users of the affected versions of the Drupal project issue tracking module who have authenticated access and the 'access project issues' permission are at risk.
The affected versions of Drupal for CVE-2007-1368 include versions before 4.7.x-1.3, 4.7.x-2.x before 4.7.x-2.3, and versions before 5.x-0.2-beta.
CVE-2007-1368 allows remote authenticated users to read the contents of a private node by manipulating the node identifier.