| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in OcoMon up to 1.21. This affects an unknown function. Performing a manipulation results in sql injection. This vulnerability is identified as CVE-2005-4662. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as critical has been found in OcoMon up to 1.21. 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 integrity. The summary by CVE is:
Multiple SQL injection vulnerabilities in OcoMon 1.20, and possibly earlier versions, allow remote attackers to execute arbitrary SQL commands via unknown attack vectors in an unspecified input form, a different vulnerability than CVE-2005-4664.
The weakness was released 11/07/2005 by OCOMON (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2005-4662 since 01/16/2006. 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.
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 (23085), SecurityFocus (BID 15386†), OSVDB (20751†) and Secunia (SA17470†). Entries connected to this vulnerability are available at VDB-27983 and VDB-27982. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: Not defined
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
11/07/2005 🔍11/11/2005 🔍
11/11/2005 🔍
11/11/2005 🔍
12/31/2005 🔍
01/16/2006 🔍
03/12/2015 🔍
07/16/2018 🔍
Sources
Advisory: securityfocus.com⛔Researcher: OCOMON
Status: Not defined
Confirmation: 🔍
CVE: CVE-2005-4662 (🔍)
GCVE (CVE): GCVE-0-2005-4662
GCVE (VulDB): GCVE-100-27981
X-Force: 23085 - OcoMon is vulnerable to SQL injection
SecurityFocus: 15386 - OcoMon Multiple Unspecified SQL Injection Vulnerabilities
Secunia: 17470 - OcoMon Unspecified SQL Injection Vulnerabilities, Moderately Critical
OSVDB: 20751 - OcoMon Unspecified SQL Injection
See also: 🔍
Entry
Created: 03/12/2015 11:11Updated: 07/16/2018 09:17
Changes: 03/12/2015 11:11 (53), 07/16/2018 09:17 (8)
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.