OcoMon Multiple Unspecified SQL Injection Vulnerabilities
BID:15386
Info
OcoMon Multiple Unspecified SQL Injection Vulnerabilities
| Bugtraq ID: | 15386 |
| Class: | Input Validation Error |
| CVE: | |
| Remote: | Yes |
| Local: | No |
| Published: | Nov 11 2005 12:00AM |
| Updated: | Nov 11 2005 12:00AM |
| Credit: | The vendor disclosed these vulnerabilities. |
| Vulnerable: |
OcoMon OcoMon 1.21 OcoMon OcoMon 1.20 0 OcoMon OcoMon 1.14 OcoMon OcoMon 1.13 OcoMon OcoMon 1.12 OcoMon OcoMon 1.11 |
| Not Vulnerable: | |
Discussion
OcoMon Multiple Unspecified SQL Injection Vulnerabilities
OcoMon is prone to multiple unspecified SQL injection vulnerabilities. These issues are due to a failure in the application to properly sanitize user-supplied input before using it in an SQL query.
Successful exploitation could result in a compromise of the application, disclosure or modification of data, or may permit an attacker to exploit vulnerabilities in the underlying database implementation.
Ocomon versions 1.x are reported to be affected; other versions may also be affected.
OcoMon is prone to multiple unspecified SQL injection vulnerabilities. These issues are due to a failure in the application to properly sanitize user-supplied input before using it in an SQL query.
Successful exploitation could result in a compromise of the application, disclosure or modification of data, or may permit an attacker to exploit vulnerabilities in the underlying database implementation.
Ocomon versions 1.x are reported to be affected; other versions may also be affected.
Exploit / POC
OcoMon Multiple Unspecified SQL Injection Vulnerabilities
No exploit is required.
No exploit is required.
Solution / Fix
OcoMon Multiple Unspecified SQL Injection Vulnerabilities
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.