BlogMe Archshow.ASP SQL Injection Vulnerability
BID:23956
Info
BlogMe Archshow.ASP SQL Injection Vulnerability
| Bugtraq ID: | 23956 |
| Class: | Input Validation Error |
| CVE: |
CVE-2007-2661 |
| Remote: | Yes |
| Local: | No |
| Published: | May 13 2007 12:00AM |
| Updated: | May 07 2015 05:39PM |
| Credit: | gsy and kerem125 are credited with the discovery of this vulnerability. |
| Vulnerable: |
Gamma Scripts BlogMe 3.0 |
| Not Vulnerable: | |
Discussion
BlogMe Archshow.ASP SQL Injection Vulnerability
BlogMe is prone to an SQL-injection vulnerability because it fails to sufficiently sanitize user-supplied data before using it in an SQL query.
Exploiting this issue could allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database.
BlogMe 3.0 is vulnerable; other versions may also be affected.
BlogMe is prone to an SQL-injection vulnerability because it fails to sufficiently sanitize user-supplied data before using it in an SQL query.
Exploiting this issue could allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database.
BlogMe 3.0 is vulnerable; other versions may also be affected.
Exploit / POC
BlogMe Archshow.ASP SQL Injection Vulnerability
Attackers can use a browser to exploit this issue.
An example URI has been provided:
http://www.example.com/blogme/archshow.asp?var=-99%20Union+all+select+0,1,2,3,4,username,password,7,8,9,10,0+from+admin
Attackers can use a browser to exploit this issue.
An example URI has been provided:
http://www.example.com/blogme/archshow.asp?var=-99%20Union+all+select+0,1,2,3,4,username,password,7,8,9,10,0+from+admin
Solution / Fix
BlogMe Archshow.ASP 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 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 for this issue. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].