Joomla Photo SQL Injection

2012-08-06T00:00:00
ID PACKETSTORM:115310
Type packetstorm
Reporter Chokri Ben Achor
Modified 2012-08-06T00:00:00

Description

                                        
                                            `Title:  
======  
Joomla com_photo - SQL Injection Vulnerability  
  
  
Date:  
=====  
2012-07-10  
  
  
References:  
===========  
http://www.vulnerability-lab.com/get_content.php?id=654  
  
  
VL-ID:  
=====  
641  
  
  
Common Vulnerability Scoring System:  
====================================  
8  
  
  
Introduction:  
=============  
Joomla is a free and open source content management system (CMS) for publishing content on the World  
Wide Web and intranets and a model–view–controller (MVC) Web application framework that can also be  
used independently.  
  
Joomla is written in PHP, uses object-oriented programming (OOP) techniques and software design  
patterns, stores data in a MySQL database, and includes features such as page caching,  
RSS feeds, printable versions of pages, news flashes, blogs, polls, search, and support for language  
internationalization.  
  
Joomla had been downloaded 23 million times. Between March 2007 and February 2011 there had been  
more than 21 million downloads. As of November 2011, there are over 8,600 free and commercial  
extensions available from the official Joomla! Extension Directory and more available from other sources.  
  
(Copy of the Vendor Homepage: http://en.wikipedia.org/wiki/Joomla)  
  
  
Abstract:  
=========  
A Vulnerability-Lab researcher discovered a SQL injection vulnerability in the com_photo module of the joomla CMS.  
  
  
Report-Timeline:  
================  
2012-07-10: Public or Non-Public Disclosure  
  
  
Status:  
========  
Published  
  
  
Exploitation-Technique:  
=======================  
Remote  
  
  
Severity:  
=========  
Critical  
  
  
Details:  
========  
A SQL Injection vulnerability is detected in the com_photo module of the joomla Content Management System.  
Remote attackers & low privileged user accounts can execute/inject own sql commands to compromise the application dbms.  
The vulnerability is located in the com_photo module with the bound vulnerable AlbumId & key parameters.   
Successful exploitation of the vulnerability result in dbms (Server) or application (Web) compromise.  
  
Vulnerable Module(s):  
[+] index.php?option=com_photo  
  
Vulnerable Parameter(s):   
[+] AlbumId  
[+] key  
  
  
Proof of Concept:  
=================  
The SQL Injection vulnerabilities can be exploited by remote attackers without privileged user account or   
required user inter action. For demonstration or reproduce ...  
  
Path: /  
File: index.php  
Parameter1: ?AlbumId=[SQL Injection]  
Parameter2: ?key=[SQL Injection]  
  
  
Reference(s):  
http://www.xxx.com.np/index.php?option=com_photo&task=gallery&AlbumId=8[SQL Injection]  
http://www.xxx.com/index.php?option=com_photo&action=slideview&key=16[SQL Injection]  
  
  
Risk:  
=====  
The security risk of the SQL injection vulnerability is estimated as critical.  
  
  
Credits:  
========  
Vulnerability Research Laboratory - Chokri Ben Achor (meister@vulnerability-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. 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: admin@vulnerability-lab.com - support@vulnerability-lab.com - research@vulnerability-lab.com  
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 (admin@vulnerability-lab.com or support@vulnerability-lab.com) to get a permission.  
  
Copyright © 2012 | Vulnerability Laboratory  
  
  
  
--   
VULNERABILITY RESEARCH LABORATORY  
LABORATORY RESEARCH TEAM  
CONTACT: research@vulnerability-lab.com  
  
`