CVE-2009-2075: High severity drupal vulnerability
Published Jun 16, 2009
·Updated
Nodequeue 5.x before 5.x-2.7 and 6.x before 6.x-2.2, a module for Drupal, does not properly restrict access when displaying node titles, which has unknown impact and attack vectors.
Affected Software
18 affected components
Drupal Drupal
Angrydonuts Nodequeue=5.x-2.0
Angrydonuts Nodequeue=5.x-2.0-beta
Angrydonuts Nodequeue=5.x-2.0-rc
Angrydonuts Nodequeue=5.x-2.0-rc2
Angrydonuts Nodequeue=5.x-2.0-rc3
Angrydonuts Nodequeue=5.x-2.1
Angrydonuts Nodequeue=5.x-2.2
Angrydonuts Nodequeue=5.x-2.4
Angrydonuts Nodequeue=5.x-2.5
Angrydonuts Nodequeue=5.x-2.6
Angrydonuts Nodequeue=5.x-2.x-dev
Angrydonuts Nodequeue=6.x-2.0
Angrydonuts Nodequeue=6.x-2.1
Angrydonuts Nodequeue=6.x-2.1-rc1
Angrydonuts Nodequeue=6.x-2.1-rc2
Angrydonuts Nodequeue=6.x-2.1-rc3
Angrydonuts Nodequeue=6.x-2.x-dev
Remediation
Patch Available
Patch Available
Patch Available
Patch Available
Event History
Jun 16, 2009
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description
Data Sourced
07:30 PM
DescriptionWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2009-2075?
The severity of CVE-2009-2075 is currently unknown as it involves improper access restriction when displaying node titles.
2
How do I fix CVE-2009-2075?
To fix CVE-2009-2075, upgrade Nodequeue to version 5.x-2.7 or 6.x-2.2 or later.
3
What versions are affected by CVE-2009-2075?
CVE-2009-2075 affects Nodequeue versions 5.x before 5.x-2.7 and 6.x before 6.x-2.2.
4
What kind of impact does CVE-2009-2075 have?
The impact of CVE-2009-2075 is unknown but could potentially allow unauthorized access to node titles.
5
Is there a known exploit for CVE-2009-2075?
There are no publicly known exploits for CVE-2009-2075 currently available.