vwdev Index.PHP SQL Injection Vulnerability
BID:16547
Info
vwdev Index.PHP SQL Injection Vulnerability
| Bugtraq ID: | 16547 |
| Class: | Input Validation Error |
| CVE: | |
| Remote: | Yes |
| Local: | No |
| Published: | Feb 08 2006 12:00AM |
| Updated: | Feb 08 2006 09:13PM |
| Credit: | Omid Aghababaei is credited with the discovery of this vulnerability. |
| Vulnerable: |
vwdev vwdev 0 |
| Not Vulnerable: | |
Discussion
vwdev Index.PHP SQL Injection Vulnerability
The vwdev application is prone to an SQL-injection vulnerability. This issue is due to a failure in the application to properly sanitize user-supplied input.
Successful exploitation can allow an attacker to bypass authentication, modify data, or exploit vulnerabilities in the underlying database implementation. Other attacks may also be possible.
The vwdev application is prone to an SQL-injection vulnerability. This issue is due to a failure in the application to properly sanitize user-supplied input.
Successful exploitation can allow an attacker to bypass authentication, modify data, or exploit vulnerabilities in the underlying database implementation. Other attacks may also be possible.
Exploit / POC
vwdev Index.PHP SQL Injection Vulnerability
An exploit is not required.
The following proof of concept examples are available:
http://www.example.com/index.php?Page=definition&UID=2;[SQLINJECTION]
http://www.example.com/index.php?Page=definition&UID=2;Drop Table Docs; --
An exploit is not required.
The following proof of concept examples are available:
http://www.example.com/index.php?Page=definition&UID=2;[SQLINJECTION]
http://www.example.com/index.php?Page=definition&UID=2;Drop Table Docs; --
Solution / Fix
vwdev Index.PHP SQL Injection Vulnerability
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]>.