[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Morfy CMS v1.05 - Command Execution Vulnerability



Document Title:
===============
Morfy CMS v1.05 - Command Execution Vulnerability


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

https://github.com/Awilum/monstra-cms/issues/351

http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-9185

CVE-ID:
=======
CVE-2014-9185


Release Date:
=============
2014-12-10


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


Common Vulnerability Scoring System:
====================================
6.2


Product & Service Introduction:
===============================
Morfy is a flat file CMS, this means there is no administration backend and database to deal with. You simply create .md files 
in the `content` folder and that becomes a page. To run Morfy you simple need PHP 5.3.0 or higher with PHP`s Multibyte String module.
Operation system: Unix, Linux, Windows, Mac OS. Webserver: Apache with Mod Rewrite or Ngnix with Rewrite Module.

(Copy of the Vendor Homepage: http://morfy.monstra.org/documentation )


Abstract Advisory Information:
==============================
An independent Vulnerability Laboratory Researcher discovered a remote command execution vulnerability in the official Morfy v1.05 Content Management System.


Vulnerability Disclosure Timeline:
==================================
2014-11-02: Researcher Notification & Coordination (Paulos Yibelo)
2014-12-10: Public Disclosure (Vulnerability Laboratory)


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


Affected Product(s):
====================
GNU GPL License
Product: Morfy - Content Management System 1.05


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


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


Technical Details & Description:
================================
A command execution web vulnerability has been discovered in the official Morfy v1.05 Content Management System.
The vulnerability allows an attacker to unauthorized execution system specific commands that compromises the online 
web-application or connected dbms.

The vulnerability is located in the site_url parameter of the default content management system install.php file.
Remote attackers are able to execute system specific commands to compromise the application by usage of malicious 
requests that run through the vulnerable site_url value. The request method to inject the code is POST via Add.

The security risk of the vulnerability is estimated as high with a cvss (common vulnerability scoring system) 
count of 6.2. Exploitation of the web vulnerability requires no privileged application user account or user interaction. 
Successful exploitation of the command execution vulnerability results in content management system compromise.

Request Method(s):
				[+] POST

Vulnerable Module(s):
				[+] Install

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

Vulnerable Parameter(s):
				[+] site_url


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

Manual steps to reproduce the security vulnerability ...

1. Download the morfy content management system
2. Use the default and access the installation file (install.php)
3. Inject the following payload `website.com}','yibelo'=> eval("system('dir');"),` (as website url) by usage of the Add function
4. Then navigate to site.com/config.php which shall get executed because that will result site_url'='website.com}','yibelo'=>eval("system('dir');"),//',
5. Successful reproduce of the security vulnerability!


Vulnerable Source: install.php < config.php

./install.php Line 57
$post_site_url = isset($_POST['site_url']) ? $_POST['site_url'] : '';

./install.php Line 64-77
    file_put_contents('config.php', "<?php
    return array(
        'site_url' => '{$post_site_url}',
        'site_charset' => 'UTF-8',
        'site_timezone' => '{$post_site_timezone}',
        'site_theme' => 'default',
        'site_title' => '{$post_site_title}',
        'site_description' => '{$post_site_description}',
        'site_keywords' => '{$post_site_keywords}',
        'email' => '{$post_email}',
        'plugins' => array(
            'markdown',
            'sitemap',
        ),    );");


Reference(s):
http://morfy.127.0.0.1:8080/install.php
http://morfy.127.0.0.1:8080/config.php


Solution - Fix & Patch:
=======================
The vulnerability can be patched by a secure restriction in the config.php file that requests the vulnerable site_url value.
Encode and parse the vulnerable site_url in the add input field of the installation module (install.php). 
Restrict the input fields and disallow special chars to prevent system specific command executions.


Security Risk:
==============
The security risk of the remote command execution vulnerability in the php engine of the web-application is estimated as high. (CVSS 6.2)


Credits & Authors:
==================
Paulos Yibelo [Independent Vulnerability Researcher]


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@xxxxxxxxxxxxxxxxxxxxx 	- research@xxxxxxxxxxxxxxxxxxxxx 	       		- admin@xxxxxxxxxxxxxxxxx
Section:    magazine.vulnerability-db.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/

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@xxxxxxxxxxxxxxxxxxxxx or research@xxxxxxxxxxxxxxxxxxxxx) to get a permission.

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



-- 
VULNERABILITY LABORATORY - RESEARCH TEAM
SERVICE: www.vulnerability-lab.com
CONTACT: research@xxxxxxxxxxxxxxxxxxxxx
PGP KEY: http://www.vulnerability-lab.com/keys/admin@xxxxxxxxxxxxxxxxxxxxx%280x198E9928%29.txt