| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in DUware DUdirectory 3.1. The affected element is an unknown function. Performing a manipulation of the argument Password results in sql injection. This vulnerability is known as CVE-2006-6455. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in DUware DUdirectory 3.1. It has been classified as critical. This affects an unknown code. The manipulation of the argument Password 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:
Multiple SQL injection vulnerabilities in admin/default.asp in DUware DUdirectory 3.1, and possibly DUdirectory Pro and Pro SQL 3.x, allow remote attackers to execute arbitrary SQL commands via the (1) Username or (2) Password parameter. NOTE: some of these details are obtained from third party information.
The weakness was published 12/10/2006 (Website). The advisory is shared at secunia.com. This vulnerability is uniquely identified as CVE-2006-6455 since 12/10/2006. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is 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 (30783), SecurityFocus (BID 21485†) and Secunia (SA23275†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
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
12/07/2006 🔍12/07/2006 🔍
12/10/2006 🔍
12/10/2006 🔍
12/10/2006 🔍
03/12/2015 🔍
08/10/2018 🔍
Sources
Advisory: secunia.com⛔Status: Not defined
CVE: CVE-2006-6455 (🔍)
GCVE (CVE): GCVE-0-2006-6455
GCVE (VulDB): GCVE-100-33765
X-Force: 30783 - DUware DUdirectory admin/default.asp SQL injection
SecurityFocus: 21485 - DUDirectory Multiple SQL Injection Vulnerabilities
Secunia: 23275 - DUware DUdirectory SQL Injection Vulnerabilities, Moderately Critical
Vupen: ADV-2006-4908
Entry
Created: 03/12/2015 22:21Updated: 08/10/2018 06:36
Changes: 03/12/2015 22:21 (51), 08/10/2018 06:36 (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.