| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Drupal EveryBlog 5.0/6.0. This issue affects some unknown processing. Performing a manipulation results in sql injection. This vulnerability is known as CVE-2008-6134. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Drupal EveryBlog 5.0/6.0 (Content Management System). It has been classified as critical. This affects some unknown functionality. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in EveryBlog 5.x and 6.x, a module for Drupal, allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
The weakness was published 02/13/2009 by Security Team with Drupal Security Team (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2008-6134 since 02/13/2009. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
It is declared as highly functional.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (45756), SecurityFocus (BID 31656†) and Secunia (SA32194†). Similar entries are available at VDB-46548, VDB-46547 and VDB-46546. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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: 7.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/08/2008 🔍10/09/2008 🔍
02/13/2009 🔍
02/13/2009 🔍
02/13/2009 🔍
03/17/2015 🔍
10/28/2018 🔍
Sources
Vendor: drupal.orgAdvisory: securityfocus.com⛔
Researcher: Security Team
Organization: Drupal Security Team
Status: Not defined
Confirmation: 🔍
CVE: CVE-2008-6134 (🔍)
GCVE (CVE): GCVE-0-2008-6134
GCVE (VulDB): GCVE-100-46545
X-Force: 45756 - EveryBlog module for Drupal unspecified SQL injection
SecurityFocus: 31656 - Drupal EveryBlog Module Multiple Unspecified Vulnerabilities
Secunia: 32194 - Drupal EveryBlog Module Multiple Vulnerabilities, Moderately Critical
See also: 🔍
Entry
Created: 03/17/2015 16:11Updated: 10/28/2018 07:59
Changes: 03/17/2015 16:11 (53), 10/28/2018 07:59 (8)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.