Document Title:
===============
Mutualaid CMS v4.3.1 - SQL Injection Web Vulnerability


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


Release Date:
=============
2016-06-21


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


Common Vulnerability Scoring System:
====================================
7.6


Product & Service Introduction:
===============================
http://www.mutualaid.org/


Abstract Advisory Information:
==============================
An independent vulnerability laboratory researcher discovered a remote 
sql-injection web vulnerability in the official Mutualaid CMS v4.3.1 content 
management system.


Vulnerability Disclosure Timeline:
==================================
2016-06-21:     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 
Mutualaid CMS v4.3.1 content management system.
The vulnerability allows remote attackers to execute own sql commands to 
compromise the web-applicaation or connected dbms.

The vulnerability is located in the `id - nid` parameter of the `article.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 request method to inject/execute is GET. The security 
vulnerability is a classic order by sql injection 
in the `id` or `nid` value. 

The security risk of the sql injection vulnerability is estimated as high with 
a cvss (common vulnerability scoring system) count of 7.6.
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):
                                [+] article.php

Vulnerable Parameter(s):
                                [+] id - nid


Proof of Concept (PoC):
=======================
The remote sql-injection web 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):
text:"Hosting provided by mutualaid.org"


PoC: Exploitation
http://localhost:8080/article.php?nid=-[ID]&;'[SQL-INJECTION VULNERABILITY!]--


Reference(s):
http://localhost:8080/article.php


Solution - Fix & Patch:
=======================
The vulnerability can be patched by usage of a secure prepared statement in the 
vulnerable file GET method request.
Restrict the parameter and disallow special chars or escapte the entries 
permanently.


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


Credits & Authors:
==================
mr_mask_black
Greetz: peyman - hossein - kian error - king dawn - white wolf - ahmad danger


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:    ad...@vulnerability-lab.com         - 
resea...@vulnerability-lab.com                                - 
ad...@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 
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 resea...@vulnerability-lab.com) to get a ask permission.

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




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


Reply via email to