===============
CRUCMS Crucial Networking - SQL Injection Vulnerability
References (Source):
====================
http://www.vulnerability-lab.
Release Date:
=============
2015-05-18
Vulnerability Laboratory ID (VL-ID):
==============================
1497
Common Vulnerability Scoring System:
==============================
8.2
Product & Service Introduction:
==============================
We work with businesses to develop web sites that help grow their bottom line. What if we told you that you could turn one of the most neglected and
frustrating aspects of your business into your most valuable, lead- and revenue-generating asset? That’s what happens when you hire the
right web strategy partner. We get that you may not understand or really want to deal with the web. Or maybe you do want to deal with it,
but don’t know where to begin. That’s where we come in with CRUCMS.
(Copy of the Vendor Homepage: http://www.contactcrucial.com/
Abstract Advisory Information:
==============================
An indepndent vulnerability laboratory researcher discovered a remote sql injection web vulnerability in the official Crucial Networking - CRUCMS web-application.
Vulnerability Disclosure Timeline:
==============================
2015-05-18: Public Disclosure (Vulnerability Laboratory)
Discovery Status:
=================
Published
Affected Product(s):
====================
Crucial Networking LLC
Product: CRUCMS - Content Management System 2015 Q2
Exploitation Technique:
=======================
Remote
Severity Level:
===============
High
Technical Details & Description:
==============================
Multiple remote sql injection vulnerabilities has been discovered in the official Crucial Networking - CRUCMS web-application (2015 Q2).
The vulnerability allows remote attackers to execute own sql commands to compromise the web-applicaation or database management system.
The vulnerabilities are located in the id value of the `projects-cat.php`,`kitchen-
Remote attackers are able to execute own sql commands by manipulation of the GET method request with the vulnerable id value.
The request method to inject the command is GET and the issue is located on the application-side.
The security risk of the sql injection vulnerability is estimated as high with a cvss (common vulnerability scoring system) count of 8.2.
Exploitation of the remote sql injection web vulnerability requires no user interaction or privilege web-application user account.
Successful exploitation of the remote sql injection results in dbms, web-server and web-application compromise.
Request Method(s):
[+] GET
Vulnerable File(s):
[+] projects-cat.php
[+] kitchen-chefs-detail.php
[+] gallery-view.php
Vulnerable Parameter(s):
[+] id
Proof of Concept (PoC):
=======================
The sql Injection web vulnerability can be exploited by remote attackers without privilege web-application user account or user interaction.
For security demonstration or to reproduce the security vulnerability follow the provided information and steps below to continue.
PoC:
http://www.[WEBSITE].com/
http://www.[WEBSITE].com/
http://www.[WEBSITE].com/
Note: use for example SQLMAP to find the (DB NAME) then use this command to get admin username and password
Command: sqlmap -u http://www.site.com/
Reference(s):
http://www.[WEBSITE].com/
http://www.[WEBSITE].com/
http://www.[WEBSITE].com/
Solution - Fix & Patch:
=======================
The sql vulnerability can be patched by a secure parse and encode of the vulnerable id value.
Use a prepared statement to protect the request and restrict the input by disallowing special chars like script code tags and co.
Security Risk:
==============
The security risk of the remote sql injection web vulnerability in the content management system is estimated as high. (CVSS 8.2)
Credits & Authors:
==================
kjfido - To mrdanger_3 and to all my old friends +ALL Muslims
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.evolution-sec.com
Contact: admin@vulnerability-lab.com - research@vulnerability-lab.com - admin@evolution-sec.com
Section: magazine.vulnerability-db.com - vulnerability-lab.com/contact.
Social: twitter.com/#!/vuln_lab - facebook.com/VulnerabilityLab -youtube.com/user/
Feeds: vulnerability-lab.com/rss/rss.
Programs: vulnerability-lab.com/submit.
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 (feed), modify, use or edit our material contact
(admin@vulnerability-lab.com or research@vulnerability-lab.com
Copyright © 2015 | Vulnerability Laboratory - [Evolution Security GmbH]™
Komentarų nėra:
Rašyti komentarą