| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Drupal Aggregation module. This affects an unknown part. This manipulation causes cross site scripting. This vulnerability is registered as CVE-2008-2998. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.
Details
A vulnerability was found in Drupal Aggregation module (Content Management System). It has been declared as problematic. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity. The summary by CVE is:
Multiple cross-site scripting (XSS) vulnerabilities in the Aggregation module 5.x before 5.x-4.4 for Drupal allow remote attackers to inject arbitrary web script or HTML via unspecified vectors.
The weakness was published 07/03/2008 by Heine Deelstra (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2008-2998 since 07/03/2008. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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 3.0 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (43008), SecurityFocus (BID 29677†) and Secunia (SA30618†). Similar entries are available at VDB-43048, VDB-43047 and VDB-43046. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
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: Aggregation module 3.0
Timeline
06/11/2008 🔍06/12/2008 🔍
07/03/2008 🔍
07/03/2008 🔍
07/03/2008 🔍
03/17/2015 🔍
11/24/2017 🔍
Sources
Vendor: drupal.orgAdvisory: securityfocus.com⛔
Researcher: Heine Deelstra
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2008-2998 (🔍)
GCVE (CVE): GCVE-0-2008-2998
GCVE (VulDB): GCVE-100-43045
X-Force: 43008 - Aggregation module for Drupal unspecified cross-site scripting
SecurityFocus: 29677 - Drupal Aggregation Module Multiple Vulnerabilities
Secunia: 30618 - Drupal Aggregation Module Multiple Vulnerabilities, Moderately Critical
See also: 🔍
Entry
Created: 03/17/2015 12:19Updated: 11/24/2017 08:31
Changes: 03/17/2015 12:19 (54), 11/24/2017 08:31 (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.