| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Source Workshop vCounter 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file vcounter.php. Executing a manipulation of the argument url can lead to sql injection. The identification of this vulnerability is CVE-2006-1499. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability classified as critical was found in Source Workshop vCounter 1.0. This vulnerability affects an unknown code of the file vcounter.php. The manipulation of the argument url with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
SQL injection vulnerability in vCounter.php in vCounter 1.0 allows remote attackers to execute arbitrary SQL commands via the URI (_SERVER[REQUEST_URI] variable).
The weakness was shared 03/28/2006 by Aliaksandr Hartsuyeu (Website). The advisory is shared for download at vupen.com. This vulnerability was named CVE-2006-1499 since 03/29/2006. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.
It is declared as proof-of-concept. By approaching the search of inurl:vcounter.php it is possible to find vulnerable targets with Google Hacking.
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 (25500), SecurityFocus (BID 17302†), OSVDB (24234†) and Secunia (SA19422†). Once again VulDB remains the best source for vulnerability data.
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: 6.9
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
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: Proof-of-Concept
Google Hack: 🔍
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
03/28/2006 🔍03/29/2006 🔍
03/29/2006 🔍
03/29/2006 🔍
03/29/2006 🔍
03/29/2006 🔍
03/12/2015 🔍
08/27/2017 🔍
Sources
Advisory: vupen.com⛔Researcher: Aliaksandr Hartsuyeu
Status: Not defined
CVE: CVE-2006-1499 (🔍)
GCVE (CVE): GCVE-0-2006-1499
GCVE (VulDB): GCVE-100-29404
X-Force: 25500
SecurityFocus: 17302 - vCounter vCounter.PHP SQL Injection Vulnerability
Secunia: 19422 - vCounter "url" SQL Injection Vulnerability, Moderately Critical
OSVDB: 24234 - vCounter vCounter.php url Parameter SQL Injection
Vupen: ADV-2006-1147
Entry
Created: 03/12/2015 12:19Updated: 08/27/2017 07:26
Changes: 03/12/2015 12:19 (47), 08/27/2017 07:26 (14)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.