| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Drupal Taxonomy Image module up to 4. This vulnerability affects unknown code. Performing a manipulation results in cross site scripting. This vulnerability is reported as CVE-2008-2773. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Drupal Taxonomy Image module up to 4 (Content Management System). It has been classified as problematic. This affects an unknown code. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:
Cross-site scripting (XSS) vulnerability in the Taxonomy Image module 5.x before 5.x-1.3 and 6.x before 6.x-1.3, a module for Drupal, allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
The weakness was disclosed 06/18/2008 (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2008-2773 since 06/18/2008. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
It is declared as highly functional.
Upgrading to version 5 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (43013), SecurityFocus (BID 29683†) and Secunia (SA30631†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.drupal.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Highly functional
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Taxonomy Image module 5
Timeline
06/11/2008 🔍06/12/2008 🔍
06/18/2008 🔍
06/18/2008 🔍
06/18/2008 🔍
03/16/2015 🔍
11/12/2017 🔍
Sources
Vendor: drupal.orgAdvisory: securityfocus.com⛔
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2008-2773 (🔍)
GCVE (CVE): GCVE-0-2008-2773
GCVE (VulDB): GCVE-100-42837
X-Force: 43013 - Taxonomy Image module for Drupal unspecified cross-site scripting
SecurityFocus: 29683 - Drupal Taxonomy Image Module Multiple Unspecified Cross Site Scripting Vulnerabilities
Secunia: 30631 - Drupal Taxonomy Image Module Cross-Site Scripting Vulnerabilities, Less Critical
Entry
Created: 03/16/2015 17:00Updated: 11/12/2017 21:02
Changes: 03/16/2015 17:00 (53), 11/12/2017 21:02 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.