Geeklog users.php and lib-sessions.php SQL injection
| geeklog-users-sessions-sql-injection (24775) |  Medium Risk |
Description:
Geeklog is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements to the users.php script using the $userid variable or to the lib-sessions.php script using the $sessid variable, which could allow the attacker to add, modify, or delete information in the back-end database.
Platforms Affected:
- Geeklog, Geeklog prior to 1.3.11sr3
- Geeklog, Geeklog prior to 1.4.0sr1
Remedy:
Upgrade to the latest version of Geeklog (1.4.0sr1 or later) or (1.3.11sr4 or later), available from the Geeklog Web site. See References.
Consequences:
Data Manipulation
References:
- Geeklog Web site, Security Update for Geeklog 1.4.0 at http://www.geeklog.net/filemgmt/singlefile.php?lid=671.
- Geeklog Web site, Security Update for Geeklog 1.3.11sr3 at http://www.geeklog.net/filemgmt/singlefile.php?lid=670.
- GulfTech Research And Development - February 19, 2006, Geeklog Remote Code Execution at http://www.gulftech.org/?node=research&article_id=00102-02192006.
- BID-16755: Geeklog Multiple Input Validation Vulnerabilities
- CVE-2006-0823: Multiple SQL injection vulnerabilities in Geeklog 1.4.0 before 1.4.0sr1 and 1.3.11 before 1.3.11sr4 allow remote attackers to inject arbitrary SQL commands via the (1) userid variable to users.php or (2) sessid variable to lib-sessions.php.
- OSVDB ID: 23348: Geeklog lib-sessions.php sessid Variable SQL Injection
- SA18920: Geeklog SQL Injection and File Inclusion Vulnerabilities
- VUPEN/ADV-2006-0661: Geeklog Multiple Remote SQL Injection and File Inclusion Vulnerabilities
Reported:
Feb 19, 2006
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