Message-ID: <b45fb38d-37e5-955a-19b4-273314d5859a@vulnerability-lab.com>
Date: Wed, 6 Jul 2016 11:12:28 +0200
From: Vulnerability Lab <research@...nerability-lab.com>
To: fulldisclosure@...lists.org
Subject: [FD] Micron CMS v5.3 - (cat_id) SQL Injection Vulnerability

Document Title:
===============
Micron CMS v5.3 - (cat_id) SQL Injection Vulnerability


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


Release Date:
=============
2016-07-06


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


Common Vulnerability Scoring System:
====================================
6.8


Product & Service Introduction:
===============================
Micron is dedicated to providing the very best in service, expertise and technology to our clients. Our certified developers 
use only the latest and most applicable technologies to create robust, reliable and comprehensive web solutions. Whether it's 
leveraging the capabilities of a customized application or creating a dynamic on-line presence, Micron has the experience 
necessary to deliver a precision tailored solution.

(Copy of the Homepage: http://websolutions.micronsolutions.in/ )


Abstract Advisory Information:
==============================
An independent vulnerability laboratory researcher discovered a remote sql-injection vulnerability in the official Micron content management system 2016 Q2.


Vulnerability Disclosure Timeline:
==================================
2016-07-06:	Public Disclosure (Vulnerability Laboratory)


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


Affected Product(s):
====================

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


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


Technical Details & Description:
================================
A remote sql injection web vulnerability has been discovered in the official Micron content management system 2016 Q2.
The vulnerability allows remote attackers to execute own sql commands to compromise the web-applicaation or connected dbms.

The web vulnerability is located in the `cat_id` parameter of the `mainbooks.php` file GET method request. Remote attackers 
are able to execute sql commands by injection of malicious statements via GET method request. The vulnerability is located on 
the application-side and the attack vector is non-persistent. The security vulnerability is a classic order by sql injection 
in the `cat_id` parameter.

The security risk of the sql injection vulnerability is estimated as high with a cvss (common vulnerability scoring system) count of 6.9.
Exploitation of the remote sql injection web vulnerability requires no user interaction or privileged web-application user account.
Successful exploitation of the remote sql injection results in database management system, web-server and web-application compromise.

Request Method(s):
				[+] GET

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

Vulnerable Parameter(s):
				[+] cat_id


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

Dork(s):
intext:"Powered By : Micron Solutions"

PoC:
http://localhost:8080/mainbooks.php?cat_id=-1'[SQL-INJECTION VULNERABILITY!]--


Security Risk:
==============
The security risk of the remote sql-injection web vulnerability in the cate_id parameter of the mainbooks.php file is estimated as high. (CVSS 6.8)


Credits & Authors:
==================
mr_mask_black - [http://www.vulnerability-lab.com/show.php?user=mr_mask_black]


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 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
Contact:    admin@...nerability-lab.com 	- research@...nerability-lab.com 				- admin@...lution-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 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@ or research@...nerability-lab.com) to get a ask permission.

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




-- 
VULNERABILITY LABORATORY - RESEARCH TEAM
SERVICE: www.vulnerability-lab.com
CONTACT: research@...nerability-lab.com



_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: http://seclists.org/fulldisclosure/

Powered by blists - more mailing lists