Virtual Communication Services Vpmi Enterprise 3.3 service_requests.asp UpdateID0 sql injection ⚔ [Disputed]

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.9$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Virtual Communication Services Vpmi Enterprise 3.3. Affected is an unknown function of the file service_requests.asp. The manipulation of the argument UpdateID0 leads to sql injection. This vulnerability is uniquely identified as CVE-2006-0897. The attack is possible to be carried out remotely. No exploit exists. There are still doubts about whether this vulnerability truly exists.

Detailsinfo

A vulnerability was found in Virtual Communication Services Vpmi Enterprise 3.3. It has been rated as critical. This issue affects an unknown code of the file service_requests.asp. The manipulation of the argument UpdateID0 with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

** DISPUTED ** SQL injection vulnerability in VCS Virtual Program Management Intranet (VPMi) Enterprise 3.3 allows remote attackers to execute arbitrary SQL commands via the UpdateID0 parameter to Service_Requests.asp. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information. NOTE: the vendor has disputed this issue, saying that "[we] have a behind the scenes complex state management system that uses a combination of keys placed in JavaScript and Session State (server side) that protects against the type of SQL injection you describe. We have tested for many of the cases and have not found it to be an issue." Further investigation suggests that the original researcher might have triggered errors using invalid field values, which is not proof of SQL injection; however, the vendor did not receive a response from the original researcher.

The weakness was disclosed 02/24/2006 by RedTeam Pentesting (Website). It is possible to read the advisory at attrition.org. The identification of this vulnerability is CVE-2006-0897 since 02/25/2006. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

It is declared as proof-of-concept. The real existence of this vulnerability is still doubted at the moment. By approaching the search of inurl:service_requests.asp 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 (24885), SecurityFocus (BID 16798†), OSVDB (23479†) and Secunia (SA18842†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.9

VulDB Base Score: 7.3
VulDB Temp Score: 6.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

02/24/2006 🔍
02/24/2006 +0 days 🔍
02/24/2006 +0 days 🔍
02/25/2006 +0 days 🔍
02/25/2006 +0 days 🔍
03/12/2015 +3302 days 🔍
08/07/2024 +3436 days 🔍

Sourcesinfo

Advisory: attrition.org
Researcher: RedTeam Pentesting
Status: Not defined
Disputed: 🔍

CVE: CVE-2006-0897 (🔍)
GCVE (CVE): GCVE-0-2006-0897
GCVE (VulDB): GCVE-100-28907
X-Force: 24885
SecurityFocus: 16798 - Virtual Communication Services VPMi Enterprise Service_Requests.ASP SQL Injection Vulnerability
Secunia: 18842
OSVDB: 23479 - VPMi Enterprise Service_Requests.asp UpdateID0 Parameter SQL Injection
Vupen: ADV-2006-0725

Entryinfo

Created: 03/12/2015 11:11
Updated: 08/07/2024 20:04
Changes: 03/12/2015 11:11 (58), 08/14/2018 08:24 (1), 08/07/2024 20:04 (16)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!