GENU CMS 2012.3 - Multiple SQL Injection Vulnerabilities

Document Title:
===============
GENU CMS 2012.3 - Multiple SQL Injection Vulnerabilities


References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=538


Release Date:
=============
2012-04-29


Vulnerability Laboratory ID (VL-ID):
====================================
538


Common Vulnerability Scoring System:
====================================
7.5


Product & Service Introduction:
===============================
GENU is a Content Management System written with PHP language and using a database server (MySQL, PostgreSQL or SQLite) for 
storage. It is fully customisable since it uses a templates system and supports multiple languages.

(Copy of the Vendor Homepage: http://www.gnew.fr)


Abstract Advisory Information:
==============================
A Vulnerability Laboratory Research Team discovered multiple SQL Injection vulnerabilities in GENU CMS 2012.3 content management system.


Vulnerability Disclosure Timeline:
==================================
2012-04-28:	Vendor Fix/Patch by Check
2012-04-30:	Public or Non-Public Disclosure


Discovery Status:
=================
Published


Exploitation Technique:
=======================
Remote


Severity Level:
===============
High


Technical Details & Description:
================================
A SQL Injection vulnerability  is detected in GENU CMS 2012.3.
The vulnerability allows an attacker (remote) or local low privileged user account to inject/execute own sql commands 
on the affected application dbms. Successful exploitation of the vulnerability results in dbms & application compromise.

Vulnerable Module(s): 
                                                        [+] posts/search.php
                                                        [+] news/search.php
                                                        [+] comments/search.php


Proof of Concept (PoC):
=======================
The sql injection vulnerabilities can be exploited by remote attackers without user inter action. For demonstration or reproduce ...

Word in 'search' must consist of at least two characters

PoC:
http://127.0.0.1:8080/GENU/news/search.php?search=xd&match=`news_subject[SQL-Injection]
http://127.0.0.1:8080/GENU/comments/search.php?search=xd&match=`news_subject[SQL-Injection]
http://127.0.0.1:8080/GENU/posts/search.php?search=xd&match=`news_subject[SQL-Injection]


Solution - Fix & Patch:
=======================
In file: /news/search.php
In line 82:
                     AND LOWER(` . TABLE_NEWS . `.` . $_GET[`match`] . `) LIKE  \\\\`%` . strtolower($search) . `% `

In file: /comments/search.php
In line 77:
                     AND LOWER(` . TABLE_COMMENTS . `.` . $_GET[`match`] . `) LIKE  `%` . strtolower($search) . `% `

In file: /posts/search.php
In line 78:
                     AND LOWER(` . TABLE_POSTS . `.` . $_GET[`match`] . `) LIKE  `%` . strtolower($search) . `% `
                   
Variable $_GET[`match`] is not filtered.
We must in this line`s edit $_GET[`match`] on $match and add code:

In file: /news/search.php
In line 71

In file: /comments/search.php
In line 69

In file: /posts/search.php
In line 69

e.g code:

if(isset($_GET[`match`]))
{
   if ($_GET[`match`] == `news_subject`) $match = `news_subject`;
   if ($_GET[`match`] == `news_text`) $match = `news_text`;
   else $match = `news_subject`;
}


Security Risk:
==============
The security risk of the sql injection vulnerabilities are estimated as high(+).


Credits & Authors:
==================
Vulnerability Laboratory [Research Team]  -    snup ([email protected])



Disclaimer & Information:
=========================
The information provided in this advisory is provided as it is without any warranty. Vulnerability-Lab disclaims all warranties, 
either expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-
Lab or its suppliers are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business 
profits or special damages, even if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some 
states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation 
may not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases 
or trade with fraud/stolen material.

Domains:    www.vulnerability-lab.com   	- www.vuln-lab.com			       - www.vulnerability-lab.com/register
Contact:    [email protected] 	- [email protected] 	       - [email protected]
Section:    video.vulnerability-lab.com 	- forum.vulnerability-lab.com 		       - news.vulnerability-lab.com
Social:	    twitter.com/#!/vuln_lab 		- facebook.com/VulnerabilityLab 	       - youtube.com/user/vulnerability0lab
Feeds:	    vulnerability-lab.com/rss/rss.php	- vulnerability-lab.com/rss/rss_upcoming.php   - vulnerability-lab.com/rss/rss_news.php

Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. 
Permission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other 
media, are reserved by Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, sourcecode, videos and 
other information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), 
modify, use or edit our material contact ([email protected] or [email protected]) to get a permission.

    				   	Copyright © 2012 | Vulnerability Laboratory