Insanely Simple Blog current_subsection SQL injection
| isb-currentsubsection-sql-injection (35450) |  Medium Risk |
Description:
Insanely Simple Blog is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements to the index.php script using the current_subsection or id parameters, which could allow the attacker to view, add, modify or delete information in the back-end database.
Platforms Affected:
- Insanely Simple Blog, Insanely Simple Blog 0.5 and prior
Remedy:
No remedy available as of July 4, 2009.
Consequences:
Data Manipulation
References:
- BugTraq Mailing List, Tue Jul 17 2007 - 05:08:41 CDT, Insanely simple blog - Multiple vulnerabilities (sql) at http://archives.neohapsis.com/archives/bugtraq/2007-07/0160.html.
- SourceForge.net, Insanely Simple Blog at http://sourceforge.net/projects/insanelysimple2.
- BID-24934: Insanely Simple Blog Multiple Input Validation Vulnerabilities
- BID-29630: Insanely Simple Blog 'index.php' Multiple SQL Injection Vulnerabilities
- CVE-2007-3889: Multiple SQL injection vulnerabilities in Insanely Simple Blog 0.5 and earlier allow remote attackers to execute arbitrary SQL commands via the current_subsection parameter to index.php and other unspecified vectors.
- CVE-2008-2670: Multiple SQL injection vulnerabilities in index.php in Insanely Simple Blog 0.5 allow remote attackers to execute arbitrary SQL commands via (1) the id parameter, or (2) the term parameter in a search action. NOTE: the current_subsection parameter is already covered by CVE-2007-3889.
- SA26105: Insanely Simple Blog Multiple Vulnerabilities
Reported:
Jul 17, 2007
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net