146 lines
6 KiB
Text
Executable file
146 lines
6 KiB
Text
Executable file
Document Title:
|
||
===============
|
||
Mangallam CMS - SQL Injection Web Vulnerability
|
||
|
||
|
||
References (Source):
|
||
====================
|
||
http://www.vulnerability-lab.com/get_content.php?id=1421
|
||
|
||
|
||
Release Date:
|
||
=============
|
||
2015-01-26
|
||
|
||
|
||
Vulnerability Laboratory ID (VL-ID):
|
||
====================================
|
||
1421
|
||
|
||
|
||
Common Vulnerability Scoring System:
|
||
====================================
|
||
8.9
|
||
|
||
|
||
Abstract Advisory Information:
|
||
==============================
|
||
An independent vulnerability laboratory researcher discovered a remote SQL-Injection web vulnerability in the official Mangallam Content Management System 2015-Q1.
|
||
|
||
|
||
Vulnerability Disclosure Timeline:
|
||
==================================
|
||
2015-01-26: Public Disclosure (Vulnerability Laboratory)
|
||
|
||
|
||
Discovery Status:
|
||
=================
|
||
Published
|
||
|
||
|
||
Exploitation Technique:
|
||
=======================
|
||
Remote
|
||
|
||
|
||
Severity Level:
|
||
===============
|
||
Critical
|
||
|
||
|
||
Technical Details & Description:
|
||
================================
|
||
A remote sql injection web vulnerability has been discovered in the official Mangallam Content Management System 2015-Q1.
|
||
The sql vulnerability allows an attacker to inject sql commands to compromise the application & database management system.
|
||
|
||
The sql injection vulnerability is located in the `newsid` value of the vulnerable `news_view.php` application file. Remote attackers
|
||
are able to inject own sql commands by manipulation of the vulnerable newsid value in the `news_view.php` file. A successful attack
|
||
requires to manipulate a GET method request with vulnerable `newsid` value to inject own sql commands. The injection is a classic
|
||
order by sql injection that allows to compromise the web-application and connected database management system. The request method to
|
||
inject own sql commands is GET and the vulnerability is located on the application-side of the service.
|
||
|
||
The security risk of the sql injection vulnerability is estimated as high with a cvss (common vulnerability scoring system) count of 8.9.
|
||
Exploitation of the application-side web vulnerability requires no privileged web-application user account and no user interaction.
|
||
Successful exploitation of the security vulnerability result in web-application and database management system compromise.
|
||
|
||
Request Method(s):
|
||
[+] GET
|
||
|
||
Vulnerable Module(s):
|
||
[+] News
|
||
|
||
Vulnerable File(s):
|
||
[+] news_view.php
|
||
|
||
Vulnerable Parameter(s):
|
||
[+] newsid
|
||
|
||
|
||
Proof of Concept (PoC):
|
||
=======================
|
||
The remote sql injection web vulnerability can be exploited by remote attackers without privileged application user account or user interaction.
|
||
For security demonstration or to reproduce the security vulnerability follow the provided information and steps below to continue.
|
||
|
||
Dork(s):
|
||
allinurl:news_view.php?newsid=
|
||
title:Powered By Powered by Mangallam
|
||
|
||
|
||
PoC:
|
||
http://localhost:8080/news_view.php?newsid=-1'[REMOTE SQL-INJECTION VULNERABILITY!]--
|
||
|
||
|
||
Reference(s):
|
||
http://localhost:8080/news_view.php
|
||
|
||
|
||
Solution - Fix & Patch:
|
||
=======================
|
||
The remote vulnerability can be patched by usage of a prepared statement next to the newsid GET method request.
|
||
Restrict and filter the newsid value and disallow input of special chars. Prevent disaplaying of php errors by usage of the (0)error (php) function.
|
||
|
||
|
||
|
||
Security Risk:
|
||
==============
|
||
The security risk of the remote sql injection web vulnerability in the content management system is estimated as critical.
|
||
|
||
|
||
Credits & Authors:
|
||
==================
|
||
IranGuard Security Team - P0!s0nC0d3
|
||
|
||
|
||
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.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@vulnerability-lab.com or research@vulnerability-lab.com) to get a permission.
|
||
|
||
Copyright <20> 2015 | Vulnerability Laboratory - [Evolution Security GmbH]<5D>
|
||
|
||
|
||
|
||
--
|
||
VULNERABILITY LABORATORY - RESEARCH TEAM
|
||
SERVICE: www.vulnerability-lab.com
|
||
CONTACT: research@vulnerability-lab.com
|
||
PGP KEY: http://www.vulnerability-lab.com/keys/admin@vulnerability-lab.com%280x198E9928%29.txt
|
||
|
||
|