full-disclosure - GENU CMS 2012.3 - Multiple SQL Injection Vulnerabilities

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date: Tue, 01 May 2012 05:02:53 +0200
From: Research <research@...nerability-lab.com>
To: full-disclosure@...ts.grok.org.uk
Subject: GENU CMS 2012.3 - Multiple SQL Injection
	Vulnerabilities

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

Date:
=====
2012-04-30

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

VL-ID:
=====
538

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:
=========
A Vulnerability Laboratory Research Team discovered multiple SQL Injection vulnerabilities in GENU CMS 2012.3 content management system.

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

Status:
========
Published

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

Severity:
=========
Critical

Details:
========
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:
=================
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:
=========
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`;
}

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

Credits:
========
Vulnerability Laboratory [Research Team]  -    snup (snup@...nerability-lab.com)

Disclaimer:
===========
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. Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability-
Lab. 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 or its suppliers.

    						Copyright © 2012 Vulnerability-Lab

-- 
VULNERABILITY RESEARCH LABORATORY TEAM
Website: www.vulnerability-lab.com
Mail: research@...nerability-lab.com

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/