Joomla com_blog v1.6 - (Pid) SQL Injection Vulnerability

Document Title:
===============
Joomla com_blog v1.6 - (Pid) SQL Injection Vulnerability


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


Release Date:
=============
2017-02-28


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


Common Vulnerability Scoring System:
====================================
7


Abstract Advisory Information:
==============================
An independent vulnerability laboratory partner team researcher discovered a remote sql-injection web vulnerability in 
the official Joomla CMS com_blog v1.6 component.


Vulnerability Disclosure Timeline:
==================================
2017-02-28: Public Disclosure (Vulnerability Laboratory)


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


Affected Product(s):
====================
Joomlart
Product: com_blog - Joomla Component (Web-Application) 1.6


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


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


Technical Details & Description:
================================
A remote sql-injection web vulnerability has been discovered in the official Joomla CMS com_blog v1.6 component.
The issue allows remote attackers to execute own malicious sql commands to compromise the web-application or dbms.

The sql-injection vulnerability is located in the `pid` parameter of the `com_blog` module. The request method to 
execute is GET and the attack vector is client-side. Remote attackers are able to inject own malicious sql commands 
via vulnerable `pid` parameter to compromise the web-application or dbms. The web vulnerability is a classic remote 
sql-injection in the `joomla `com_blog` component.

The security risk of the vulnerability is estimated as high with a common vulnerability scoring system count of 7.0. 
Exploitation of the sql-injection vulnerability requires no privilege web-application user account or user interaction. 
Successful exploitation of the web vulnerability results in web-application or database management system compromise.

Request Method(s):
[+] GET

Vulnerable Component(s):
[+] com_blog

Vulnerable File(s):
[+] index.php

Vulnerable Parameter(s):
[+] pid


Proof of Concept (PoC):
=======================
The sql-injection vulnerability can be exploited by remote attackers without privilege web-application user account or user interaction.
For security demonstration or to reproduce the vulnerability follow the provided information and steps below to continue.


Dork(s):
inurl:index.php?option=com_blog
site:index.php?option=com_blog


PoC: Exploitation
http://localhost/[JOOMLA_PATH]/index.php?option=com_blog&view=comments&pid=[SQL-INJECTION VULNERABILITY!]&Itemid=0


Reference(s):
http://localhost/joomla/
http://localhost/joomla/index.php
http://localhost/joomla/index.php?option=com_blog


Solution - Fix & Patch:
=======================
The sql-injection web vulnerability can be resolved by a parse and restriction of the vulnerable `pid` parameter.
Disallow the usage of special chars and use the escape function. 
Implement a secure prepared statement to resolve the vulnerability.


Security Risk:
==============
The security risk of the remote sql injection web vulnerability in the web-application coponent plugin is estimated as high. (CVSS 7.0)


Credits & Authors:
==================
Amir - Iranian Exploit Database (www.iedb.ir) [http://www.vulnerability-lab.com/show.php?user=IEDB%20Team]

Thanks: C0dex,B3hz4d,Beni_vanda,Mr_time,Bl4ck M4n,black_security,Yasser,Ramin Assadian,Black_Nofuzi,SecureHost, 
1TED,Mr_Kelever,Mr_keeper,Mahmod,Iedb,Khashayar,B3hz4d4,Shabgard,Cl09er,Be_lucky,MoslemHaghighian,Dr_Iman,8Bit,
Javid,Esmiley_Amir,Mahdi_feizezade,Amin_Zohrabi,Shellshock3 ... all my friends and the Iedb Team.


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 mainly for 
consequential or incidental damages so the foregoing limitation may not apply. We do not approve or encourage anybody to break any licenses, policies, 
deface websites, hack into databases or trade with stolen data.

Domains:    www.vulnerability-lab.com 		- www.vuln-lab.com 						- www.evolution-sec.com
Section:    magazine.vulnerability-lab.com 	- vulnerability-lab.com/contact.php 				- evolution-sec.com/contact
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
Programs:   vulnerability-lab.com/submit.php 	- vulnerability-lab.com/list-of-bug-bounty-programs.php 	- vulnerability-lab.com/register.php

Any modified copy or reproduction, including partially usages, of this file, resources or information 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, source code, videos and other information on this website is trademark 
of vulnerability-lab team & the specific authors or managers. To record, list, modify, use or edit our material contact (admin@) to get a ask permission.

				    Copyright © 2017 | Vulnerability Laboratory - [Evolution Security GmbH]™